X Data Hub
Twitter/X API Data
AI Agent Data Engine · Twitter/X API · Managed rate limits
Twitter/X data engine for AI agents
Feed trading bots, research agents, market monitors, and alert workflows with live posts, user profiles, search results, trends, quotes, reposts, and timelines through one stable API layer.
Tradingsentiment and event signals
Researchtopic and account intelligence
Alertsnear real-time agent triggers
Use Cases
Agent workflows powered by Twitter/X data
Twitter/X is where traders, founders, researchers, projects, influencers, and communities publish signals first. X Data Hub turns that feed into structured context your agents can act on.
Compare
Why agents use a managed Twitter/X data layer
One API key gives agents structured Twitter/X data, managed request limits, and an account-pool path for search results that can fit your market niche.
| Need | X Data Hub | Official X API | Self-hosted account pool |
|---|---|---|---|
| Setup and access | Same-day API key | Approval, plans, contracts | Accounts, proxies, parser, ops |
| Cost model | Recharge credits | High monthly commitment | Accounts + proxies + engineering time |
| API limits | 20 req/s per key + edge 429 | Plan and endpoint quotas | You own cooling, retries, and bans |
| Advanced search | Account-pool preference layer | Generic query behavior | Can be niche-biased, but fragile |
| Private account pool | Managed health and routing | No private account context | Private, but you maintain everything |
| Agent-ready data | Search, profiles, threads, timelines | Strong, but plan-gated | Custom parsing and normalization |
Core idea:
keep the self-hosting advantage of private account context and advanced-search preference, while removing the daily work of account bans, rate limits, retries, and parser maintenance.
Pricing
Recharge credits as your data usage grows
New accounts receive 2,000 trial credits for API testing. Successful calls consume credits; larger recharge packs include bonus credits while keeping the same API limits.
For first integration tests and small agent jobs.
- 10,000 credits
- No bonus credits
- 20 requests/s per API key
For running trading, research, and alert agents daily.
- 31,900 credits total
- Includes 2,900 bonus credits
- Usage visibility for daily jobs
For production workflows with steady Twitter/X demand.
- 118,800 credits total
- Includes 19,800 bonus credits
- Usage logs and key controls
For data-heavy agents and multi-project teams.
- 388,700 credits total
- Includes 89,700 bonus credits
- Usage logs and key controls
QPS Limits
One shared rate-limit model
Credits control how much you can consume. Rate limits control how fast your program can call the service. They are separate by design.
Edge protection
Default key protection is 20 requests/s. Over-limit traffic gets a fast 429 before it reaches provider calls.
API key20 requests / second
Outer edgeOver-limit traffic returns 429 before business logic runs
Abuse guardAbnormal error patterns can automatically freeze a key
Endpoint Pricing
Estimate credits by endpoint cost
Draft model for launch: simple lookups are cheap, paginated social graph and advanced search cost more. Failed provider calls are not charged as successful usage.
Tweet lookup, user profile, user about.
Threads, conversations, quotes, reposts, user tweets, media, articles.
Market and topic trend feeds.
Paginated social graph pages.
Search pages with query, feed, cursor, and account-pool preference routing.
2,000 search pages x 5 + 8,000 tweet/profile calls x 1.