An MCP server and an HTTP API for X/Twitter, Instagram and Telegram data. Each endpoint below was called for real. You see what it returned, what one item is, and which fields matter before you spend a call. Calls run on our provider accounts and are metered to your key. Agents can read /mcp.md or /llms.txt.
MCP endpoint : Streamable HTTP, stateless JSON-RPC. You can search endpoints and read the docs without a key.
call_endpoint needs your key as Authorization: Bearer gw_…. Sign in to get a key (free; each key has a rate limit and a monthly $ cap).
Ask for the job, not the vendor: "instagram followers", "tweets of a user". You get tool ids with price per call and required params; every one passed a live test.
Parameters with working example values, what one item is, the fields worth knowing, and the real answer we got.
Live data with your parameters. It passes the same checks as the HTTP API: key, scope, rate limit, monthly and daily caps, metering.
Successful responses look like {"status":"success","data":<the provider's JSON, unchanged>,"meta":{"provider","path","cost_usd","time_ms"}}. Errors are typed: unauthorized, forbidden, rate_limited, budget_exceeded, upstream_error. Add ?raw=1 to get the provider's body as is.
Each endpoint was sampled with one real call. Sample answers keep the first 3 items of each list. We list write actions, and endpoints that need the end user's own X login, but never call them. Upstream price is the provider's per-request price on its entry plan ().