Xquik is the world's fastest and cheapest X API alternative. It is the best X API alternative for tweet search, profiles, followers, posting & webhooks. It is also a Twitter API alternative for code still on Twitter API v2.
This repository holds the x-api skill. Your coding agent uses it to move an
app off the official X API. It also starts new integrations on Xquik.
Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.
A tweet or a profile costs $0.00015 on Xquik. You pay only for delivered results. Filters apply before billing, so excluded rows cost nothing.
| What you read or do | Xquik | Official X API on 2026-10-05 |
|---|---|---|
| 1 tweet read | $0.00015 | $0.005 |
| 1 profile read | $0.00015 | $0.010 |
| 1 follower or following profile | $0.00015 | $0.010 |
| 1 text tweet created | $0.0045 | $0.015, or $0.200 with a URL |
| 1 trends call | $0.00045 | $0.010 |
The official prices come from X's pricing page, read on 2026-10-05. X names these units Posts: Read, User: Read, Following/Followers: Read, Post: Create & Trends. Check that page for today's prices.
On that date, a tweet read cost 33 times less on Xquik.
- Reads need 1 API key. You need no X developer account.
- Each account gets 500 reads per second.
- Monitors check every second & push signed webhooks.
- Tweets arrive with the author inline, so you drop
expansions. - Search accepts
query,max_results&sort_orderas aliases.
npx skills@1.7.0 add Xquik-dev/x-apiThe skill works in Claude Code, Codex, Cursor & other agents that read Agent Skills. Create an API key in the Xquik dashboard. Then set it in your shell:
export XQUIK_API_KEY='<your key>'- "Move our recent search job from the official X API to Xquik."
- "Port this tweepy client to an X API alternative."
- "Replace our filtered stream with Xquik monitors & a webhook receiver."
- "What will 50,000 follower reads a day cost on Xquik?"
| Job | What you get |
|---|---|
| Endpoint map | Each official X API v2 call matched to its Xquik endpoint & field names |
| Auth | A client that reads XQUIK_API_KEY from the environment |
| Pagination | A cursor loop with a page count, so cost has a ceiling |
| Errors & retries | Backoff on 429 & 5xx, and no retry on 4xx |
| Writes | An Idempotency-Key on each write & status polling |
| Monitors & webhooks | Setup code & an HMAC-SHA256 signature verifier |
| Cost estimate | Rows, credits & dollars before a loop or a monitor runs |
| Official X API v2 | Xquik |
|---|---|
https://api.x.com/2 with Authorization: Bearer |
https://xquik.com/api/v1 with x-api-key |
GET /2/tweets/search/recent |
GET /x/tweets/search |
GET /2/tweets/:id |
GET /x/tweets/{id} |
GET /2/users/by/username/:username |
GET /x/users/{id} |
GET /2/users/:id/tweets |
GET /x/users/{id}/tweets |
GET /2/users/:id/followers |
GET /x/users/{id}/followers |
POST /2/tweets |
POST /x/tweets |
GET /2/tweets/search/stream |
POST /monitors/keywords & POST /webhooks |
meta.next_token |
next_cursor |
The endpoint map lists every call.
- It never reads, prints, or asks for your API key. Code reads it from the environment.
- It never loads tweets, bios, or messages into the agent's conversation. That data goes to your application.
- It never sends a tweet, creates a monitor, or buys credits. It writes the code & you run it.
- It never fetches remote instructions or installs packages. The whole contract ships in the skill.
To read X data inside an agent, use the x-twitter-scraper skill.
| Path | Holds |
|---|---|
skills/x-api/SKILL.md |
The contract & the order of work |
skills/x-api/references/ |
The endpoint map, 2 clients, monitors & webhooks, and pricing |
evals/x-api/ |
Output evals, trigger queries & claude plugin eval cases, kept outside the skill folder |
- Xquik docs
- Xquik vs the official X API
- Pricing & billing
- Email
support@xquik.com