MintAPI gives you one paid API layer for Twitter/X, YouTube, TikTok, Instagram, Google Maps, Yelp, and more. Human teams use dashboard API keys; agent runtimes pay per request with x402-native flows.
X / Twitter
YouTube
TikTok
Yelp
Google Maps
Google Search
Amazon
// TWO ACCESS MODES
x402 is an HTTP payment flow: the API returns 402 Payment Required, the agent signs payment, retries, and receives structured JSON.
For teams
Human operators top up credits, create API keys, and call the catalog from apps, scripts, docs, and internal tools.
1curl "https://api.mintapi.dev/api/twitter/user-info?screenname=elonmusk" \2 -H "x-api-key: $MINTAPI_KEY"For agents
Use plain fetch to handle the raw 402 challenge yourself, or use the SDK for a smoother pay-and-retry flow.
1import { paidJson } from "@mintapi/gateway/client"23const profile = await paidJson(4 "https://api.mintapi.dev/api/twitter/user-info?screenname=elonmusk"5)What you can build
MintAPI covers social, video, maps, reviews, marketplace, and search data. Integrate once, then let human operators or autonomous agents call the endpoints they need.
Track profiles, mentions, and trends across X, YouTube, and TikTok through one integration path.
Enrich location data with Google Maps and Yelp for local business intelligence and review monitoring.
Let agents fetch marketplace listings, search results, and review data on demand without pre-provisioned keys.
Why MintAPI instead of direct integrations
| Direct integrations | MintAPI | |
|---|---|---|
| Setup | Auth, billing, and formats per provider | One API surface and contract |
| Agent access | Dashboard-bound keys, manual billing | x402 per-request payment |
| Data shape | Vendor-specific HTML or JSON | Structured JSON by default |
// CREDITS & PRICING
Teams top up credits for dashboard keys. Agent runtimes can pay only when a specific external data request is worth making.
// SDK & TOOLING
The SDK keeps routine buyer logic out of your prompts and app code, but you can always drop down to raw x402 flows when you need tighter control.
TypeScript-first
Use the agent client directly or stay low-level with paidFetch and paidJson.
Managed signers
Route EVM and Solana signing through your own wallet infrastructure instead of hardcoding keys.
Raw protocol compatible
You can still implement the 402 → pay → retry loop yourself when you want full control.
Built for agent runtimes
Works cleanly in Node.js agents, tool wrappers, and backend workflows that buy access on demand.
FAQ
Short answers for teams and agent builders evaluating paid API access.
Go through the dashboard with personal API keys or integrate directly with x402-native agent payments. The API surface stays the same either way.
Dashboard API keys for humans. Stateless x402 flow for agents.