SO
Identity & Enrichment · x402 · early usage
Get an X (Twitter) profile by handle or numeric user id
Get an X (Twitter) profile by handle or numeric user id.
by api.socialfetch.dev · discovered, not yet claimed by its owner · updated 2026-10-02
30d calls1
30d payers1
MethodGET
Outputjson
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Get an X (Twitter) profile by handle or numeric user id.
Tags: Twitter · social-data · bazaar · payment-identifier
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-10-02
Input example from Bazaar metadata
{}Output example
{
"data": {
"lookupStatus": "found",
"metrics": {
"favourites": 16987,
"followers": 92390102,
"following": 117,
"listedCount": 96930,
"mediaCount": 28139,
"tweets": 74284
},
"profile": {
"_truncated": true,
"accountCreatedAt": "2007-12-19T20:20:32.000Z",
"avatarUrl": "https://pbs.twimg.com/profile_images/1321163587679784960/0ZxKlEKB_400x400.jpg",
"bannerUrl": "https://pbs.twimg.com/profile_banners/11348282/1788992290/1500x500",
"bio": "Making the seemingly impossible, possible. ✨",
"blueVerified": true,
"displayName": "NASA",
"handle": "NASA",
"platform": "twitter",
"platformUserId": "11348282",
"privateAccount": false,
"profileUrl": "https://x.com/NASA",
"verified": false
}
},
"meta": {
"creditsCharged": 1,
"requestId": "req_example_twitter_profile",
"version": "v1"
}
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/29623.jsonfor the price and payment options. - Pay. Call
GET https://api.socialfetch.dev/v1/twitter/profiles/:handle. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.014 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 1 calls · 1 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.014 | 0x02C2fCAfCe36B4AAdB39625866Bc6B1699d83043 | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x02C2fCAfCe36B4AAdB39625866Bc6B1699d83043",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "14000",
"amountUsd": 0.014,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl
curl -X GET 'https://api.socialfetch.dev/v1/twitter/profiles/:handle'
# -> 402 Payment Required; read PAYMENT-REQUIRED
# retry the identical request with PAYMENT-SIGNATUREJavaScript
const res = await fetch("https://api.socialfetch.dev/v1/twitter/profiles/:handle", {
"method": "GET"
});
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}Python
import httpx
res = httpx.request("GET", "https://api.socialfetch.dev/v1/twitter/profiles/:handle")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- api.socialfetch.dev
- Endpoint
- https://api.socialfetch.dev/v1/twitter/profiles/:handle
- Machine-readable
/resources/29623.json