TwitterAPIs is a pay-as-you-go Twitter and X API for developers and AI agents. Get Twitter data and actions without an X developer account or a subscription, at $0.0008 per call (about $0.04 per 1,000 tweets). It ships a native MCP server, so Claude, Cursor and any MCP client can read tweets, run advanced search and pull the follower graph directly. 112 REST endpoints, clean JSON, and $0.50 in free credits at signup, no card.
Native MCP server for Claude, Cursor and Claude Code
112 REST endpoints: tweet search, user graph, timelines, threads and posting
$0.0008 per call, about $0.04 per 1,000 tweets, no subscription
No X developer account, one Bearer API key
Advanced tweet search by keyword, hashtag, mention and date
Account monitoring via signed webhook, Slack or Discord
Feed live Twitter and X data to AI agents and LLM apps over MCP
Run a managed tweet scraper or social-listening pipeline
Influencer and follower-graph discovery
Brand monitoring and research without the official X API cost
Build RAG and training datasets from tweets and threads

Hi Fazier! TwitterAPIs is a pay-as-you-go Twitter and X API: $0.0008 per call, about $0.04 per 1,000 tweets, with no X developer account and no subscription. 112 REST endpoints cover tweet search, the follower graph, timelines, threads and posting, and it ships a native MCP server for Claude and Cursor. New accounts get $0.50 in free credits, no card. Would love your feedback.
The native MCP server and per-call pricing make this attractive for agent workflows that only need occasional X lookups, and 112 endpoints cover both search and actions. Could the docs expose per-endpoint rate limits and retry guidance, so teams can estimate spend and handle throttling before scaling a job?
Pay-as-you-go at $0.0008 per call is a genuinely useful model for occasional research — I like that there is no X developer account or monthly subscription to maintain. The native MCP server for Claude and Cursor stands out for agent workflows. One question: how do the signed webhooks handle rate limits or retries when monitoring a busy account?
Convertlyft reads how visitors use a website (funnels, session replays, rage and dead clicks, form friction, JavaScript errors and page speed) and audits the site's SEO. Instead of leaving you with dashboards to interpret, it tells you what to fix first and shows the evidence for each recommendation. Every figure comes with its time window and whether it was measured, read from a stored crawl, or estimated, so you know how far to trust it. Convertlyft also works inside AI tools. Its remote MCP server and open-source agent skills let Claude Code, Codex, Cursor, Gemini CLI, Copilot and other agents pull your site's analytics, diagnose conversion drops and run SEO research directly. A REST API mirrors every tool. You can try it without an account: run a free SEO scan of any public site, an AI agent-readiness check, or search the docs. Convertlyft is free during early access.
The pay-per-call model without needing an X developer account is the real draw here - most alternatives still lock you into a pricey subscription before a single tweet. One question: how do rate limits work on the follower graph endpoint, is $0.0008 charged per page or per full pull? The native MCP server is a smart move too; asking Claude for the latest tweets on a topic with zero glue code is exactly how I would use this.
Putting the MCP server next to write endpoints raises a question for me: when an agent in Claude or Cursor has the key, can I scope that key to read-only, so a stray tool call can't post or follow from my account? And for the follower-graph pulls, is a large account billed per page of results or per follower returned? At $0.0008 a call that changes the maths quite a bit.

Hi Fazier! TwitterAPIs is a pay-as-you-go Twitter and X API: $0.0008 per call, about $0.04 per 1,000 tweets, with no X developer account and no subscription. 112 REST endpoints cover tweet search, the follower graph, timelines, threads and posting, and it ships a native MCP server for Claude and Cursor. New accounts get $0.50 in free credits, no card. Would love your feedback.
The native MCP server and per-call pricing make this attractive for agent workflows that only need occasional X lookups, and 112 endpoints cover both search and actions. Could the docs expose per-endpoint rate limits and retry guidance, so teams can estimate spend and handle throttling before scaling a job?
Pay-as-you-go at $0.0008 per call is a genuinely useful model for occasional research — I like that there is no X developer account or monthly subscription to maintain. The native MCP server for Claude and Cursor stands out for agent workflows. One question: how do the signed webhooks handle rate limits or retries when monitoring a busy account?
Convertlyft reads how visitors use a website (funnels, session replays, rage and dead clicks, form friction, JavaScript errors and page speed) and audits the site's SEO. Instead of leaving you with dashboards to interpret, it tells you what to fix first and shows the evidence for each recommendation. Every figure comes with its time window and whether it was measured, read from a stored crawl, or estimated, so you know how far to trust it. Convertlyft also works inside AI tools. Its remote MCP server and open-source agent skills let Claude Code, Codex, Cursor, Gemini CLI, Copilot and other agents pull your site's analytics, diagnose conversion drops and run SEO research directly. A REST API mirrors every tool. You can try it without an account: run a free SEO scan of any public site, an AI agent-readiness check, or search the docs. Convertlyft is free during early access.
The pay-per-call model without needing an X developer account is the real draw here - most alternatives still lock you into a pricey subscription before a single tweet. One question: how do rate limits work on the follower graph endpoint, is $0.0008 charged per page or per full pull? The native MCP server is a smart move too; asking Claude for the latest tweets on a topic with zero glue code is exactly how I would use this.
Putting the MCP server next to write endpoints raises a question for me: when an agent in Claude or Cursor has the key, can I scope that key to read-only, so a stray tool call can't post or follow from my account? And for the follower-graph pulls, is a large account billed per page of results or per follower returned? At $0.0008 a call that changes the maths quite a bit.
Find your next favorite product or submit your own. Made by @FalakDigital.
Copyright ©2026. All Rights Reserved