Fetch thread context around one tweet so agents can understand multi-post announcements and arguments.
Turn long announcement threads into one complete agent-readable context.
curl --request GET 'https://xai.xxxstrategy.com/v1/tweets/20/thread' \
--header 'Authorization: Bearer tw_live_your_api_key'Create an API key from the console to run this endpoint against live Twitter/X data.
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.
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.
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 |
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.
New accounts receive 2,000 trial credits for API testing. Successful calls consume credits; larger recharge packs include bonus credits.
For first integration tests and small agent jobs.
For running trading, research, and alert agents daily.
For production workflows with steady Twitter/X demand.
For data-heavy agents and multi-project teams.
Credits control how much you can consume. Rate limits control how fast your program can call the service. They are separate by design.
Current endpoint costs are loaded from live admin configuration. List and search calls consume credits per returned item; single lookups are charged per request.
Fetching live credits configuration from the API.
Start with focused workflow pages for AI agents, social data APIs, scraping replacement, crypto alerts, competitor monitoring, social listening, and API comparisons.
These answers help builders decide whether Social Data Hub fits their AI agent, trading, alerting, social listening, or market research workflow.
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.
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.
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.
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.