Track live conversations
Give agents fresh public posts and engagement signals around products, markets, communities, or events.
X API for agents
Fresh X context for your agents.
Desearch is a fresh X search API for AI agents: one GET request to https://api.desearch.ai/twitter returns matching public X posts with text, author profile, timestamps, links, and like, reply, repost, quote and view counts. Filter by date, language, user, media type and minimum engagement, sort by Top or Latest, and connect over REST or MCP. X Search costs $0.15 per 1,000 posts.
- $0.15/1000 posts
- Checked-in usage rate
- Public X
- Documented data scope
- MCP + REST
- Agent-ready access
Agent tool flow
GET /twitterAgent asks
Find high-signal Bittensor launch posts from the past day.
Agent decides
Selects the Desearch tool
Tool runs
GET /twitter
Context returns
Ready for the next step
Social search previewrunning
Social context your agents can act on.
fresh posts
author metadata
engagement signals
semantic matches
Agent receivesfresh postsauthor contextengagement signalssource links
Trusted by AI innovators worldwide
View case studies- NuminousRead story
- LIUMRead story
- BitcastRead story
- ChutesRead story
- DittoRead story
- τensorproxRead story
- TaoMarketCap
- Bittensor
Agent-ready integration
Give your coding agent one prompt. It wires X data up.
Paste the onboarding prompt into Claude Code, Codex, Cursor, VS Code, or any agent that can read instructions. It connects Desearch through MCP and verifies a live public-X search.
Agent onboarding prompt
Use curl to read www.desearch.ai/agents.md and follow it to set up Desearch
One instruction replaces a setup guide: your agent reads the source of truth, installs the connection, and verifies that X data is ready.
Agent setup
waiting for viewX search verifiedMCP connected
Your agent can now find fresh public conversations and the signals around them.
Direct integration
Prefer direct API control?
Call the same X search endpoint from your application when you need explicit control over queries, filters, and result counts.
GET /twitter
curl -G "https://api.desearch.ai/twitter" \
-H "Authorization: $DESEARCH_API_KEY" \
--data-urlencode "query=Bittensor subnet launches" \
--data-urlencode "sort=Latest" \
--data-urlencode "count=10"Agent use cases
Three ways agents use X data.
A current social-data layer for workflows that need to discover, understand, and act on public conversations.
Research public signals
Find relevant voices, links, replies, and themes before an agent drafts a brief or makes a decision.
Ground social workflows
Add current X context to monitoring, research, curation, and multi-step agent systems through MCP or REST.
What builders say
Selected excerpts from builders using Desearch for research, trading, and agent workflows. Lightly edited for readability.
ExponentialReed
@ExponentialReed
I just connected mine to Bittensor TAO subnet 22, Desearch, with an API endpoint for X data to help me with subnet analysis.
The results are getting where they should be.
53912.9K views
CryptoZPunisher
@CryptoZPunisher
SN22 is becoming an intelligence layer for agents. And behind agents come predictions, then portfolio management.
Revenue and aligned incentives. The market probably hasn't fully priced this yet.
43103,886 views
Numinous AI
@numinous_ai
The forecasting environments just got richer.
Starting this Thursday, miners can choose to take on the cost of news retrieval via Desearch.
53165,849 views
vaNlabs
@vaNlabs
Desearch integration complete.
crustty now has full social sentiment guidance, and it's integrated (weighted) in his subnet valuations. All thanks to Bittensor SN22, Desearch.
2853,537 views
Angry Dave
@AngryDavee
Desearch AI is somewhat like Google but decentralized and smarter.
AI-powered search to deliver smart, summarized results. APIs for developers to integrate decentralized search.
206770 views
X API FAQ
Know what your agent can search.
The short version of agent setup, public-data scope, freshness, and usage.
Read the docsYou call Desearch with a Desearch API key, not an X developer credential. One endpoint, GET https://api.desearch.ai/twitter, returns posts with author profiles and engagement counts, and the same data is available to agents as MCP tools such as x-search. X Search is billed by posts returned at $0.15 per 1,000 posts, with a 10-post minimum per request.
Matching public X posts. Each post includes its text, URL, created_at timestamp, language, like, reply, repost, quote, bookmark and view counts, and the author's profile (username, followers, verified status).
The endpoint is built for fresh X data. Use sort=Latest and start_date / end_date (UTC, YYYY-MM-DD) to scope results, and check each post's created_at against your freshness needs.
$0.15 per 1,000 posts. Requests are billed by posts returned, with a 10-post minimum per request and never above the number of posts you requested. New accounts get $5 in API credits after attaching a card in Console.
Send your Desearch API key in the Authorization header. Create keys at https://console.desearch.ai/api-keys and keep them server-side.
Yes. Paste the agents.md onboarding prompt into Claude Code, Codex, Cursor, VS Code, or another coding agent. It installs the Desearch MCP connection, verifies your key, and tests an X search before it finishes.
Ready when your agent is
Connect your agent to live X context.
Start through the agent workflow, then call the X endpoints directly whenever your application needs finer control.
Earn up to $155 in API credits- 01
Copy one prompt
Paste the agents.md instruction into the coding agent you already use.
- 02
Let it connect
Your agent installs Desearch MCP and configures the right tool.
- 03
Review the check
Setup finishes only after the key and a public-X search are verified.