Social Data Hub
Social Data Hub
Public Social Data API
Independent developer service. Not affiliated with, endorsed by, or operated by X Corp. or Twitter.
Guide

Twitter/X API for AI Agents

How AI agents use Twitter/X public social data, search, profiles, timelines, threads, and alerts as live market context.

Why agents need public social data

Twitter/X is often the first place where founders, traders, journalists, projects, and communities publish market-moving context. Agents need structured access to public social data instead of brittle browser automation.

What to connect first

Start with advanced search for narratives, user timelines for watchlists, tweet detail for enrichment, and conversation or quote endpoints for reaction analysis.

Operational model

Use API keys, predictable rate limits, and credit accounting so agent workflows can be monitored and scaled without maintaining account pools, retries, and parsing logic in each project.

Related API endpoints

search.tweetsAdvanced Twitter/X Search API

Search Twitter/X public social data with query text, feed selection, count limits, and cursor pagination for agents and market monitors.

tweet.lookupTweet Detail API

Fetch one Twitter/X post by tweet id for enrichment, alert verification, and agent context windows.

tweet.threadTweet Thread API

Fetch thread context around one tweet so agents can understand multi-post announcements and arguments.

tweet.conversationTweet Conversation API

Fetch replies and conversation context for a Twitter/X post with cursor pagination.

Read API DocsView Pricing
Public Social Data API · Twitter/X API · Managed rate limits

Public social data API for AI agents

Feed trading bots, research agents, market monitors, and alert workflows with live Twitter/X public social data: posts, profiles, search results, trends, quotes, reposts, and timelines through one stable API layer.

View Pricing
Tradingsentiment and event signals
Researchtopic and account intelligence
Alertsnear real-time agent triggers
Social Data Hub AI agent data engine preview
Use Cases

Agent workflows powered by public social data

Twitter/X is where traders, founders, researchers, projects, influencers, and communities publish signals first. Social Data Hub turns public social data into structured context your agents can act on.

Trading strategy agents Track token tickers, founder posts, whale narratives, breaking news, and sentiment spikes before they reach slower data feeds.
Market research agents Build account maps, topic summaries, competitor monitors, launch trackers, and daily intelligence reports from live social data.
News and alert agents Watch keywords, cashtags, projects, KOLs, and events, then trigger webhooks, Slack alerts, dashboards, or downstream agent tasks.
Growth and lead agents Find active builders, communities, KOLs, buyers, and partner signals from high-intent conversations around your market.
Compare

Why agents use a managed social data layer

One API key gives agents structured Twitter/X social data, managed request limits, and an account-pool path for search results that can fit your market niche.

Need Social 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.
API Coverage

Public social data endpoints for production agent systems

Social Data Hub packages high-demand Twitter/X social data into API responses that are easier for AI agents, dashboards, trading systems, and research workflows to consume.

Advanced Twitter/X social search API Run keyword, cashtag, account, and narrative searches across public social data for market monitoring, launch tracking, trend discovery, and social listening.
Tweet detail, thread, and conversation APIs Fetch post context, replies, thread structure, quote activity, and repost activity so agents can reason over full event timelines.
User profile and timeline APIs Build account intelligence, KOL monitors, competitor trackers, founder watchlists, and creator research pipelines.
Agent-ready rate limits and credits Use API keys with predictable request protection, credit accounting, and managed provider routing instead of maintaining fragile scraping infrastructure.
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.

Starter Recharge 10U

For first integration tests and small agent jobs.

  • 10,000 credits
  • No bonus credits
  • USDT-TRC20 payment
Builder Recharge 29U

For running trading, research, and alert agents daily.

  • 31,900 credits total
  • Includes 2,900 bonus credits
  • USDT-TRC20 payment
Scale Recharge 99U

For production workflows with steady Twitter/X demand.

  • 118,800 credits total
  • Includes 19,800 bonus credits
  • USDT-TRC20 payment
Volume Recharge 299U

For data-heavy agents and multi-project teams.

  • 388,700 credits total
  • Includes 89,700 bonus credits
  • USDT-TRC20 payment
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 Credits

Estimate endpoint credits

Current endpoint costs are loaded from live admin configuration. List and search calls consume credits per returned item; single lookups are charged per request.

Loading endpoint credits ...

Fetching live credits configuration from the API.

FAQ

Public social data API questions teams ask before integration

These answers help builders decide whether Social Data Hub fits their AI agent, trading, alerting, social listening, or market research workflow.

What is Social Data Hub used for?

Social Data Hub is used to feed AI agents and automation workflows with Twitter/X public social data: search results, tweet details, account profiles, timelines, quotes, reposts, and conversation context.

Is this a replacement for the official X API?

It is a managed data layer for teams that need fast integration, credit-based usage, and account-pool routing. Teams with direct enterprise X API contracts may still use the official API for contract-specific workloads.

Which workflows benefit most from Twitter/X data?

Trading bots, market intelligence agents, research dashboards, launch monitors, news alerts, lead discovery systems, and community analytics tools usually benefit most from near real-time social data.

How do credits and rate limits work?

Credits measure successful data consumption, while rate limits control request speed. API keys are protected by a default 20 requests per second limit and over-limit requests return 429 quickly.