One POST per call. The 402 challenge carries the exact amount and a line-item breakdown before you sign, so an agent always knows the cost first.
Dynamic pricing — the exact quote is returned in each 402 before any spend. Volume tools bill per returned item and require resultsLimit, so you never pay for more than you asked for.
Watch an account and get the post as it lands, have every event signed and pushed to your endpoint, and post as your own handle without handing over your keys.
Monitor an account or keyword and get the post the moment it lands. 21 event types, prepaid by the hour at about $0.025/hr, stops on its own at expiry.
Every event arrives as an HMAC-signed POST with a durable retry ladder over ~36 minutes, auto-pause on repeated failure, and a terminal monitor.expired event.
Connect an X account once, then pay per action across 12 write types. Credentials are relayed sealed — never stored here, never in a URL, never seen by the calling agent.
Five installable skills — reads and search, bulk exports, real-time monitors, and posting through an account you connect once, plus the unattended loop that drafts in your voice and queues replies for approval. One command in Claude Code, Cursor, OpenClaw or Hermes, and no X developer account anywhere in the setup.
/skill.mdthe agent playbook/llms.txtservice index for LLMs/openapi.jsonschemas + payment discoveryPOST /api/mcptools/list free · tools/call paidThe short version of the docs — what this is, what it costs, and how paying per call works.
twitr.sh is a pay-per-call X/Twitter API built for AI agents. It covers reads (tweets, profiles, timelines), search with full operator filters, bulk extractions, real-time account and keyword monitors with signed webhooks, and posting through a connected X account. Every request is paid at call time in USDC over the HTTP 402 flow — no signup and no API keys.
Prices start at $0.001 per call. Single reads cost about $0.0012; volume tools (search, timelines, lists) bill per returned item, and real-time monitors are prepaid at roughly $0.025 per hour. The exact quote is returned in the 402 challenge before you pay, so an agent always knows the cost first.
The wallet is the account. Your first POST to any tool returns HTTP 402 Payment Required with the exact price; your client signs a USDC payment (x402 on Base or Solana, MPP on Tempo) and retries the identical request to get the data. x402-aware clients do both steps automatically.
USDC on three networks: Base and Solana via the x402 protocol, and Tempo via MPP. Both rails settle on-chain per request — there is no subscription and no prepaid balance.
Yes. POST /api/mcp is a streamable-HTTP MCP endpoint: tools/list is free, tools/call is payment-gated with a JSON-RPC 402. There is also an installable agent skill at /skill.md, an LLM service index at /llms.txt, and a full OpenAPI 3.1 spec at /openapi.json.
Yes. A monitor watches one account or one keyword query and emits 21 event types — new posts, replies, quotes, mentions, profile changes, and more. Events are delivered by polling or as HMAC-signed webhooks with a durable retry ladder. Monitors are prepaid by the hour at about $0.025/hr.
Yes. Connect an X account once, then pay per action across 12 write types — post, reply, like, retweet, follow, DM, and more. Credentials are relayed sealed during login: never stored, never placed in a URL, never visible to the calling agent.
No. 4xx and 5xx responses are never charged. Resource-creating calls (extractions, monitors, writes) require an Idempotency-Key header, so a retry replays the original result instead of charging twice.
14 tools, one spec. Your agent pays, we run it, you get clean JSON.
Listings in progress — the agent directories and payment indexes we publish to, not endorsements.