DELXCOMMERCE Buyer decision center

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.

987 governed routes980/991 Bazaar-indexeddiscovery freeself-buys ≠ external revenue
01
orientDescribe the outcome

The intent router returns a governed recommendation or an explicit non-payable gap.

FREE
02
compareCompare the market

Use the Bazaar snapshot, semantic rank readback and coverage matrix before choosing a route.

FREE
03
preflightValidate the contract

Inspect price, network, schema, receipt and refund behavior; Coinbase validate is read-only.

FREE
04
payPay the exact route

Pay only the canonical resource after the buyer's own policy checks; one request is one result.

PAY
05
verifyVerify delivery

Check the returned artifact, receipt hash, delivery outcome and refund path; a challenge is not a sale.

FREE

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. 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. 2. Read the payment challenge · Inspect the HTTP 402 amount, network, recipient, resource URL, schema and deadline before signing anything.
  3. 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. 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. 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.

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.

For agents

Carry the same evidence into code.

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.