The X API for public data, priced per result.

Retrieve public X/Twitter data through a plain REST API — or straight from your AI assistant. Nothing to apply for, and no subscription.

No credit card required. $0.20 per 1000 results, and the balance never expires.

Developers

One request in, structured JSON out.

No SDK, no pagination library, no parsing layer. Every endpoint answers a plain HTTP request with the same shape you see here.

https://api.socialdata.tools/twitter/user/elonmusk
{
"id": 44196397,
"id_str": "44196397",
"name": "Elon Musk",
"screen_name": "elonmusk",
"location": "\ud835\udd4f\u00d0",
"url": null,
"description": "",
"protected": false,
"verified": true,
"followers_count": 166213974,
"friends_count": 506,
"listed_count": 149577,
"favourites_count": 37987,
"statuses_count": 34934,
"created_at": "2009-06-02T20:12:29.000000Z",
"profile_banner_url": "https://pbs.twimg.com/profile_banners/44196397/1690621312",
"profile_image_url_https": "https://pbs.twimg.com/profile_images/1683325380441128960/yRsRRjGO_normal.jpg",
"can_dm": false
}

Thirty more endpoints — lists, spaces, communities, threads, quotes, retweeters — are in the API reference.

  • Real-time results

    Requests are served against live data, not a cached snapshot from hours ago.

  • One key, every endpoint

    A single bearer token authenticates every request. No OAuth flow, no SDK, no connected account.

  • Pay-as-you-go pricing

    $0.20 per 1000 results, no subscription, and the balance never expires.

How it works

From signup to first response in five minutes.

No approval queue, no SDK to install, no contract. Three steps, and the third one is just topping up a balance.

  1. 1

    Create an API key

    Sign up and generate a key in your dashboard. There is no application to submit, no platform approval to wait on, and no X account to connect.

  2. 2

    Send your first request

    Every endpoint is a plain REST call with a bearer token, so it works from curl, Postman, or the HTTP client you already use. Responses come back as JSON.

  3. 3

    Pay for what comes back

    Most endpoints cost $0.20 per 1000 results. You deposit what you need rather than subscribing, and the balance stays in your account until you spend it.

A first request looks like this:

curl "https://api.socialdata.tools/twitter/search?query=from%3AOpenAI&type=Latest" \
  -H "Authorization: Bearer $SOCIALDATA_API_KEY" \
  -H "Accept: application/json"

Full endpoint reference, parameters, and response shapes live in the API documentation.

Features

An X (Twitter) API that stays out of your way.

Public posts, profiles, search, and followers — priced per result, with nothing to install and nothing to keep running.

  • No approval queue

    No X developer account, no application, no waiting to be let in. Sign up, create a key, and the first request works.

  • Pay for results, not seats

    Most endpoints cost $0.20 per 1000 results. Top up what you need instead of subscribing, and the balance stays until you spend it.

  • Real-time responses

    Requests are served against live data, so what comes back reflects what is publicly visible right now — not a snapshot from last night.

  • Read-only by design

    Nothing is ever posted on your behalf and no account is connected, so there is nothing of yours to get rate-limited or suspended.

  • No proxies to babysit

    No scraping stack, no rotating proxies, no browser fleet to keep alive when the markup changes. One HTTP call returns JSON.

  • Ready for AI agents

    An MCP server ships alongside the REST API, so Claude Code, Codex, Cursor, or Windsurf can pull the same data with no wrapper code.

X (Twitter) MCP Server

Your AI assistant, connected to X data

The Model Context Protocol lets Claude, Codex, Cursor or Windsurf call SocialData directly. Ask a question in plain English and your assistant looks the answer up — no wrapper code to write. Same per-tweet pricing as the API, still no subscription.

claude mcp add --transport http socialdata https://api.socialdata.tools/mcp \
    --header "Authorization: Bearer YOUR_API_KEY"
  • Read-only. 14 tools covering users, tweets, search and followers.
  • Billed exactly like the equivalent REST call — same rate, same limits.
  • Works in your terminal, your editor, or Claude Desktop.
Use cases

What teams build with it.

The same endpoints, pointed at different problems.

  • Monitoring and alerts

    Track brand mentions, competitors, or a watchlist of accounts, and route what matters into Slack, a CRM, or an internal workflow.

  • Audience intelligence

    Map the followers, following, and engagement around an account or community to power segmentation and market research.

  • Creator and lead discovery

    Find the accounts active in a market or conversation, enrich their public profiles, and rank them on audience and engagement signals.

  • Analytics dashboards

    Keep a reporting product current with posts, profiles, engagement metrics, and list activity arriving as consistent JSON.

  • Research datasets

    Collect reproducible datasets with cursor pagination, date ranges, and search operators, keeping the source IDs and timestamps intact.

  • Context for AI applications

    Give agents and analysis pipelines current public posts, conversations, and engagement signals through a documented HTTP API.

Usage-based pricing

Pay for the data you retrieve.

No plans, no seats, no monthly reset. Add funds to your balance and spend them at your own pace — the balance does not expire.

$0.0002

per tweet or user profile

That's $0.20 per 1,000 tweets

Applies to most post, profile, follower, search, list, community, and Space data. Some specialised endpoints are priced differently — each one is listed in the pricing reference.

Included with every account

  • Every standard Data API endpoint
  • API key management and a usage dashboard
  • Low-balance notifications and optional auto top-ups
  • Cursor pagination on every collection endpoint
  • Failed requests do not consume your balance

Running a high volume? Contact support and we will quote a custom rate.

Frequently Asked Questions

Answers to common questions about SocialData.

SocialData provides API endpoints to easily extract public data from social media websites.

Anyone focused on growing their social media account or business and looking for a convenient way to export data that can be used to find leads. Or anyone building their own product that relies on social media data.

No. You don't need an X developer account, an approved app, or your own X credentials, and there is no application to fill in or wait on. Sign up for SocialData, create an API key, and start requesting data — that is the whole process. This is the main reason developers move here from the official X API, where access depends on platform approval and a monthly plan.

About five minutes. Create an account, generate an API key in your dashboard, and make your first request. Every endpoint is a plain REST call with a bearer token, so it works from curl, Postman, or any HTTP client in the language you already use — our API documentation has ready-to-paste examples.

We do not currently offer a free plan, but you can contact our support team and discuss your use case. We might be able to setup a free demo account for you.

We are using various sources to get the data, but all of it is public data

Real-time. Requests are served against live data, so a post, profile, or search result reflects what is publicly visible on X at the moment you call the API — not a cached snapshot from hours or days ago. That matters if you are tracking mentions, monitoring accounts, or reacting to something as it happens.

No. SocialData is read-only: it extracts public data and never acts on your behalf. You never connect an X account or hand over credentials, so there is no account of yours to get rate-limited, restricted, or suspended. If you need to publish content, you will need X's official API for that part — SocialData covers the reading side.

Yes. SocialData runs an MCP (Model Context Protocol) server, so AI coding assistants can query X data directly — Claude Code, Codex, Cursor, Windsurf, and Claude Desktop are all supported. Point your client at https://api.socialdata.tools/mcp using your API key, then ask for what you need in plain English instead of writing wrapper code. Note that the connector interfaces in claude.ai and ChatGPT are not supported, because they require OAuth rather than an API key.

Exactly like the REST API. Every tool call costs what the equivalent request costs and is drawn from the same balance — there is no separate MCP subscription, seat fee, or minimum. One thing worth knowing: an assistant given a broad instruction such as "get all followers of this account" will keep paging until it has everything, so it is worth watching your balance the first few times you let an agent work unattended.

For most of the endpoints the price is $0.2 per 1000 results returned (e.g. 1000 posts). Explore API documentation for information on specific price per endpoint. We provide lower custom rates for projects that generate large volume.

You can deposit any amount that you think you might need. If you expect to use the service regularly, you may set up a recurring deposit, but only if you think this is needed.

Your balance will not expire. Unlike other services, we don't provide monthly usage limits that reset every month. Any deposit you make will remain in your account until you've used it completely.

We provide "No questions asked" refunds for any deposits within 14 days of payment provided you haven't used your deposit to request data through the API. Email us at [email protected] to request a refund.

Get started

Your first X API request is five minutes away.

No platform approval, no subscription, no X account to connect. Create a key and start pulling public X data — from your own code or straight from your AI assistant — and pay only for the results you get back.

No credit card required