Xquik API
Independent, third-party X (Twitter) data and automation platform offering 40+ tools for search, extraction, write actions, monitoring, webhooks, and trends. Provides a REST API with OpenAPI 3.1 contract, hosted MCP servers, llms.txt, and published agent skills. Not affiliated with X Corp.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Xquik API the way a machine reads it — 2 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Xquik API scores 17.4/100 (emerging), with a separate agent-readiness read of 17/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Xquik API
Each block below is one kind of artifact we hold for Xquik API. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 2
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Xquik REST API
REST API for X (Twitter) data and automation with OpenAPI 3.1 contract covering 93 paths across API Keys, Account, Articles, Communities, Composition, Draws, Events, Extractions...
Xquik Docs MCP Server
Read-only documentation search MCP server for the Xquik platform.
← All providers · Data indexed from github.com/api-evangelist/xquik-api · machine-readable index on apis.io