Structured APIs, flexible payments

Structured APIs for
live external data and request-based usage.

Access social, trend, creator, and discovery APIs through a developer-first platform built for programmatic use today and more human-friendly purchase flows over time.

request-based billingpay per requestBase • Polygon • Solana
X / Twitter logo

X / Twitter

YouTube logo

YouTube

Soon
TikTok logo

TikTok

Soon
Instagram logo

Instagram

Soon
Facebook logo

Facebook

Soon
Google Maps logo

Google Maps

Soon
Yelp logo

Yelp

Soon
TripAdvisor logo

TripAdvisor

Soon
Pinterest logo

Pinterest

Catalog
Browse all

// WHY THIS MODEL

Built for agents that
buy access on demand.

This is not another account-first API wrapper. It is a paid API layer designed around x402, agent workflows, and clean per-endpoint pricing.

  ┌───────┐
  │ ◉ ◎ ○ │
  │ ◎ ◉ ◎ │
  │ ○ ◎ ◉ │
  └───────┘

Pay per request

Your agent pays only when it actually calls an endpoint. No seats, no monthly minimums, no dashboard dependency.

  ┌─┐   ┌─┐
  │A├──►│B│
  └─┘   └┬┘
        ┌▼┐
        │C│
        └─┘

No account required

Start from a plain HTTP request, receive a 402 challenge, pay, and retry. The protocol does the heavy lifting.

   ╔═══╗
   ║ ◈ ║
  ┌╨───╨┐
  │░░░░░│
  └─────┘

Credits-first pricing

Pricing stays predictable across the catalog. Credits are the product unit, while settlement still maps cleanly to USD.

  │  ▄ 
  │▁ ▄ █ ▄
  │█ █ █ █
  └────────

Structured JSON responses

Endpoints return machine-ready payloads for social, creator, trend, and discovery workflows instead of brittle scraping glue.

    .--.
   /    \
  | (  ) |
   \    /
    '--'

Multi-network settlement

Agents can negotiate accepted payment routes and settle on Base, Polygon, or Solana while the API catalog stays unified.

  GET /api
  ────────►
  ◄────────
  { data }

Fast-growing API catalog

Start with X and YouTube today, then expand into more paid data sources without changing the way your agent buys access.

// AGENT FLOW

Three steps from
request to result.

agent-flow.ts
1const first = await fetch(
2 "https://api.example.com/api/twitter/user-info?screenname=elonmusk"
3)
4
5const challenge = await first.json()
Ready

// PRICING

Simple usage-based pricing
for agentic workflows and apps.

Live catalog pricing|2:06:41 PM
0
credits per $1
shared conversion across the catalog
0
credit from
starting price for lightweight calls
0
credits and up
flexible endpoint pricing as the catalog grows
0
payment networks
Base, Polygon, Solana
Illustrative pricing examples
1 cred.GET /api/twitter/user-infox/twitterlive$0.001
2 cred.GET /api/youtube/trendingyoutubelive$0.002
3 cred.GET /api/twitter/searchx/twitterlive$0.003
5 cred.GET /api/twitter/tweet-infox/twitterlive$0.005

// SDK & TOOLING

Use the wrapper,
or own the protocol.

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.

1import { createSignerResolver, paidJson } from '@x402-api/gateway/client'
2
3const signerResolver = createSignerResolver({
4 signerResolversByFamily: {
5 evm: async ({ network }) => resolveManagedEvmSigner(network),
6 svm: async ({ network }) => resolveManagedSolanaSigner(network),
7 },
8})
$npm install @x402-api/gateway
import from @x402-api/gateway/client

Blog

Themed editorial built for search quality and machine readability.

Articles are static, fast to parse, and structured with FAQs, canonical metadata, JSON-LD, sitemap entries, and agent-facing discovery output.

Browse all articles

Start calling paid APIs today.

Open the docs, pick an endpoint, and wire the buyer flow into your agent. No signup is required for the x402 path.

No signup required for the agent flow