byDexterDexterbeta
DashboardSearch
Explorer
ProtocolsChainsFacilitatorsServersResourcesTransactionsLifetime
Dexter Products
OpenDexterInstinct
Intelligence
WashCircleChannels
Skills
Browse SkillsBuild a Skill
StatusDocsAboutBlog
DexterDexter

The real-time explorer for the x402 paid web. 8 chains. Quality-scored APIs. Live settlement data.

Explore

  • Facilitators
  • Servers
  • Resources
  • Transactions

Developers

  • API Docs
  • GitHub
  • x402 SDK
  • OpenDexter
  • Status

Company

  • About
  • Blog
  • Terms of Service
  • Privacy Policy
  • Contact
© 2026 Dexter Labs CorporationPowered by the x402 protocol
Dashboard/Docs/For agent builders

For agent builders

Building an LLM tool, an autonomous agent, or a backend that needs paid data? Get it discovering and calling x402 endpoints without wiring each one by hand. This page shows you how, starting from the fastest path.

The fastest path

Install @dexterai/opendexter and mount its MCP server in your client. It exposes two tools: semantic search across the entire marketplace, and full skill detail by id. Two tool calls and your agent has access to thousands of paid APIs.

Prefer raw HTTP? Skip ahead to Raw API. The same data is one POST away.

1Path

OpenDexter MCP, for any MCP client

OpenDexter is a hosted MCP server. Mount it in Claude Code, Cursor, Codex CLI, or any other MCP-compatible client and your agent gets two new tools:

  • x402_search: natural-language capability search. Queries like "ETH price feed," "generate an image," or "analyze a Solana wallet" return ranked endpoints with prices, networks, and quality scores.
  • x402_fetch: call any x402 endpoint with automatic payment settlement through the Dexter facilitator. The agent says "call this URL," OpenDexter handles the 402, the signing, and the settlement.

GitHub: github.com/Dexter-DAO/opendexter-ide

2Path

@dexterai/x402, for direct integration

When you're writing the agent code yourself, the SDK gives you a drop-in fetch wrapper that handles the entire x402 flow. The server returns 402, the SDK signs a payment header with your configured wallet, and the request retries automatically.

Install:

npm install @dexterai/x402

Browser usage with React (the same hook x402gle uses on the merchant editor and chat surfaces):

tsimport { useX402Payment } from '@dexterai/x402/react';

const { fetch, isLoading, transactionId } = useX402Payment({
  wallets: { solana: solanaAdapter },
  preferredNetwork: 'solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp',
});

// Use it like the regular fetch.
const res = await fetch('https://api.example.com/paid-endpoint');
const data = await res.json();
// transactionId now holds the on-chain settlement signature.

Server-side usage with Node, deno, or any runtime is covered in the SDK README at github.com/Dexter-DAO/dexter-x402-sdk.

3Path

Per-host agent surfaces, for crawlers and frameworks

Every indexed merchant on x402gle publishes machine-readable manifests at predictable URLs. Substitute the merchant's hostname for {host}. For example, x402gle.com/servers/orbisapi.com/skills.json.

/servers/{host}/.well-known/agent.json

A2A v0.2.1 agent discovery card. The standard well-known location agents check first.

/servers/{host}/skills.json

Flat skill index. Name, one-liner, when_to_use, price, network, confidence, and per-skill detail URL.

/servers/{host}/{skill-id}.json

Full per-skill detail with mcp_tool and anthropic_tool definitions ready to paste into your agent.

/servers/{host}/manifest.json

AI-authored host manifest with capability clusters, cross-skill workflows, and routing guidance.

/servers/{host}/SKILL.md

Anthropic Agent Skills format. Paste into Claude Code, Codex CLI, Cursor, GitHub Copilot, or any tool supporting SKILL.md.

4Path

Dextercard, for agents that need a real card

When your agent needs to spend on something outside x402 (a SaaS subscription, a flight, a domain), Dextercard gives you a virtual Mastercard funded from the user's stablecoin treasury. The entire onboarding flow is driveable from chat: the captcha is solved server-side, the user pastes the OTP, your agent walks them through KYC conversationally.

The hosted OpenDexter MCP exposes the card flow as tools: card_login_request_otp, card_login_complete, card_status, card_issue, and card_freeze. Local tools and CLIs use the connector OAuth pairing flow to redeem a one-time request id for the user's carrier-session tokens. Your tool acts on the user's behalf without ever holding their Supabase JWT.

See the Dextercard docs for the full flow, the stage ladder, and pairing details.

Raw API: capability search

If you're writing a backend service or want to embed marketplace search directly without an SDK, hit the public capability endpoint.

bashcurl -X POST https://dexter.cash/api/x402gle/capability \
  -H 'Content-Type: application/json' \
  -d '{ "query": "generate an image from a prompt", "limit": 5 }'

Returns ranked candidates with prices, supported networks, quality scores, and the resource ids you need to fetch full skill detail.

Supported chains

settlement layers

Endpoints declare which chains they accept in their 402 response. You bring the wallet, the SDK picks the right one. We index settlements across:

Solana
Base
Polygon
Arbitrum
Optimism
Avalanche
BNB Chain
SKALE

Why this data is trustworthy

Every listing earns its score. Endpoints get called, the response is graded against what the merchant claims, and the score decides where the listing surfaces in search.

See how verification works for the full pipeline.

← For merchantsHow verification works →