Enterprise discovery, without the theater
Find. Compare.
Verify delivery.
One free handoff for agents and humans. Start with an outcome, inspect the exact contract, compare the public market signal, pay only the canonical route, and verify the receipt.
The intent router returns a governed recommendation or an explicit non-payable gap.
Use the Bazaar snapshot, semantic rank readback and coverage matrix before choosing a route.
Inspect price, network, schema, receipt and refund behavior; Coinbase validate is read-only.
Pay only the canonical resource after the buyer's own policy checks; one request is one result.
Check the returned artifact, receipt hash, delivery outcome and refund path; a challenge is not a sale.
Payment rails
Pay USDC on Base + Solana.
Read the live HTTP 402 challenge before signing. Base and Solana must both be declared for every governed Commerce route; on Solana, PayAI sponsors network fees, so the buyer needs USDC but not SOL for gas.
Buyer method
How to evaluate an x402 API before paying.
Discovery is read-only. Use these five checks to decide whether a pay-per-result route fits the job and your risk policy before signing a payment.
- 1. Match the outcome · Describe the result you need and select a governed route whose declared purpose matches it. A similar name is not proof of equivalent behavior.
- 2. Read the payment challenge · Inspect the HTTP 402 amount, network, recipient, resource URL, schema and deadline before signing anything.
- 3. Check delivery and refund policy · Confirm the output shape, receipt or artifact evidence, timeout behavior and the documented refund path for that route.
- 4. Pay one canonical route · Authorize only the exact resource that passed your own policy checks. Discovery and a successful preflight never authorize payment.
- 5. Verify the result · Validate the returned artifact, receipt hash, delivery status and settlement evidence before treating the request as complete.
Observed market signal
What agents are already buying elsewhere.
These are public Bazaar signals, not Delx sales. 53 semantic queries put Delx in the result set 45 times.
- web-search · 38885 calls · 232 payers · $0.01 (blocked)
- chain-and-rpc-reads · 36340 calls · 1 payers · $0.01 (partial)
- chain-and-rpc-reads · 16084 calls · 1 payers · $0.002 (partial)
- social-search · 9134 calls · 21 payers · $0.006 (blocked)
- maps-and-travel · 4896 calls · 11 payers · $0.02 (blocked)
- website-content-extraction · 4477 calls · 2 payers · $0.002 (covered)
- crypto-market-and-risk · 4363 calls · 8 payers · $0.02 (partial)
- social-search · 4080 calls · 11 payers · $0.005 (blocked)
Open the complete evidence map ↗ · Open buyer-rank readback ↗ · Open index coverage ↗
Capability matrix
Covered, partial and blocked — honestly.
6 covered · 4 partial · 6 blocked · 1 not planned. A blocked capability is a roadmap signal, never a payable substitute.
- media-generation · partial · generate_image, transform_image · next gate: Restore sale only after the canonical per-product economics, rights, delivery and refund gates pass.
- weather-data · covered · get_weather_forecast_nws
- currency-exchange-rates · covered · get_fx_rates_ecb
- agent-integration-and-x402-audit · covered · util_api_health_report, util_openapi_summary, util_x402_resource_summary, util_x402_server_audit
- website-content-extraction · covered · util_page_extract, util_links_extract, util_docs_site_map, util_website_intelligence_report
- loyalty-workflows · partial · util_loyalty_reward_quote · next gate: Only add stateful recipient, balance, voucher or settlement routes after an owner-approved ledger and live authorization path.
- data-conversion · covered · util_csv_to_json, util_json_to_csv, util_email_validate
- agent-utility-primitives · covered · util_json_validate, util_token_estimate, util_uuid_generate, util_timestamp_convert
- social-search · blocked · next gate: Owner-approved provider agreement and bounded account; then verify source terms, privacy/retention limits, worst-case cost, refund behavior, protocol parity and one external paid smoke before enabling social search.
- web-search · blocked · next gate: Do not create an OpenSerp account or top up. Keep search_web blocked until a written commercial search license with redistribution rights exists. Free-data extraction and news flagships remain the covered demand path. Receipt: docs/discovery-receipts/web-search-engine-rights-2026-08-03.json
- people-and-company-enrichment · blocked · next gate: Obtain written provider resale rights and an owner-approved personal-data policy; bound fields, retention, abuse handling, cost and refunds before a paid production smoke.
- chain-and-rpc-reads · blocked · next gate: Obtain written commercial RPC authorization and a bounded Node credential; then set a spend cap, prove worst-case cost and margin, define refunds/telemetry and run one external paid smoke before enabling live reads.
- crypto-news-and-market-data · partial · search_news_gdelt, search_crypto_news_gdelt · next gate: Owner approves a commercial market-data provider and risk policy; then verify freshness, redistribution rights, bounded cost, margin, refund behavior and paid delivery telemetry before enabling live quotes.
- maps-and-travel · partial · geocode_us_address, search_open_entities · next gate: Keep current bounded routes live; only add global geocoding, live places or travel after written provider rights, field/privacy limits, cost and refund telemetry are verified.
- mailbox-and-file-upload · not_planned · next gate: Requires an explicit owner re-open with a named storage/identity owner, retention and deletion design, abuse controls, egress budget and restore/refund evidence.
- model-chat · blocked · next gate: Owner approves a provider and model allowlist; then prove token ceilings, content policy, cost/margin, timeout/refund behavior, telemetry and one external paid smoke.
- prediction-markets · blocked · next gate: Requires owner-approved legal/risk scope, licensed market source, freshness SLO, bounded cost, refund path and an external paid smoke; until then it stays non-payable.
For agents
Carry the same evidence into code.
- Machine-readable decision brief ↗
- Portable commerce manifest ↗
- Traversable discovery graph ↗
- AI agent API production-readiness checklist ↗
- x402 versus MPP payment protocol guide ↗
- Free intent router and capability backlog ↗
- Paid resource manifest ↗
Revenue is counted only after an externally verified payment and successful delivery. Challenges, crawlers, rankings and indexing are not sales.
FAQ
Common x402 buyer questions.
What is an x402 API buyer supposed to check first?
Start with the outcome, then inspect the live 402 challenge and the route schema. Price, network, recipient, delivery evidence and refund terms must fit the buyer's policy before payment.
Does discovering an x402 service authorize payment?
No. Discovery, rankings and read-only validation are orientation only. Payment remains an explicit caller decision for one canonical resource.
What proves that an x402 request was delivered?
Use the service's declared output contract plus its delivery receipt, artifact URL or hash, status and settlement evidence. A 402 challenge alone is not a sale or delivery.
Can a blocked capability be purchased through Delx Commerce?
No. Blocked and partial categories remain non-payable until provider rights, cost, margin, privacy, refund behavior and delivery telemetry are evidenced.