Get your x402 API found and chosen. Check what your agent paid.

Why isn't my x402 API in the Bazaar? Listing lint checks an x402 endpoint for Bazaar indexing: one unpaid call validates its 402 PAYMENT-REQUIRED header, discovery metadata, input and output schemas, description limits and service name against the indexing rules, with a fix for each problem and the fixed 402 ready to paste, graded as the weekly report card would grade it.

Where does my x402 API rank in Bazaar search? Rank check runs the search a buyer agent would run for your task and returns your rank, the listings ahead of you, the signals where you trail them (payers, calls, description, example, schema, price), what the three winners' descriptions say that yours doesn't, and your share of voice across the buyer searches of your category.

Is my x402 API losing rank in Bazaar search? The rank watch runs the rank check for your task now, then again every week for 30 days, and alerts you when your rank drops, you fall out of the results, or your share of voice across your category's buyer searches shrinks.

Will buyer agents choose my x402 API? The Machine Buyer Panel is an A/B conversion test: buyer-agent models choose between your offer and its real Bazaar rivals for up to three tasks, across buyer personas and list positions.

Will buyer agents pick my x402 API for one task? The single-task panel is the Machine Buyer Panel for buyers under a dollar cap: buyer-agent models choose between your offer and its real Bazaar rivals for one task, across personas and list positions.

A signed attestation of your API's sample output, so buyer agents can check it before paying.

What x402 API should I build? The demand gap finder runs up to 150 Bazaar searches phrased the way buyer agents phrase tasks and ranks the unmet demand: tasks whose top results are weak (no listings, few payers, thin descriptions or a poor fit), with the evidence for each, a spec per gap (an OpenAPI skeleton, a Fair Offer block and a price from the category price index) and the gap's trend week over week.

Who pays my x402 API, and do they come back? Customer analytics for an x402 seller from USDC payments on Base: repeat buyers versus one-off and sweep-like payers, revenue per payer and weekly retention cohorts.

Will a new AI model stop buying my x402 API? The model-update watch tests your offer against its real Bazaar rivals with the Machine Buyer Panel now, then re-runs the same test whenever a panel model changes over the next 30 days and flags a drop in your win rate.

Every claim in your 402's fair-offer block checked against live behaviour.

The full certification now (priced at 5 cents or less, your route is paid once to check that failed calls are free and receipts are signed), then re-run about once a day for 30 days.

Can buyer agents' SDKs pay it, and is it safe to pay? Checks the x402 v2 requirements (amounts, addresses, the token's EIP-712 domain, the same terms on every request), that malformed and forged payments are refused the same way, resource and pay-to binding, MPP challenges against the paymentauth.org draft, and the live price against the Bazaar and openapi.json.

A signed verdict on one offer from what Agoranome already holds, with the Fair Offer block valid and certified or not, the pay-to seen for this host and since when, the price against listing and quote, verified deliveries, and which policy tiers the offer meets.

Red-team an x402 client with one token and nine trap routes on Agoranome's own host, each a $0.001 seller: a correct offer and eight attacks (price switch, lookalike asset, pay-to swap, network switch, instructions in the paid body, slow responder, unsettled 200, ambiguous error).

Every USDC payment checked against the payee's listed Bazaar price (above listed, oversize 10x or more, unlisted), spend and calls per seller, duplicate payments within a minute, payments made after a seller's listing vanished or its pay-to changed, sellers whose certification failed since, whether the wallet itself looks sweep-like, and a CSV of every payment.

Name up to ten seller URLs, or a wallet whose sellers are read from its payments, and for 30 days each is checked daily: price, pay-to, Fair Offer block, Bazaar listing, certification state and latency.

Post a paid response body, or passages of it, with the seller's URL and get back instruction-like passages aimed at an agent, hidden characters, exfiltration links, a mismatch against the seller's declared output example, and whether the seller's "data, never instructions" claim held.

Post a plan of seller URLs and call counts and get the total cost, each seller's listing and certification state, its expected failure share from reconciled receipts, the fit against your caps (per call, per seller, total, policy tier), and every certified seller in the same category sorted by price with the sort key stated.

Given a payment's transaction hash, the seller URL, the accepted 402 and the response, get the settlement on Base, the Fair Offer terms at quote time (failed calls free, receipts, refunds), what Agoranome observed of that seller in that hour, the seller's published contact and a draft claim addressed to it, all signed.

What are agents buying on x402? A weekly x402 market data and demand report from Bazaar discovery and Base settlements: repeat-use demand by category, demand gaps, movers, price bands and GET vs POST traction, adjusted for sweeps, with cited sources.

Can my wallet pay an x402 API? Pay a fraction of a cent in USDC on Base and get a signed receipt back, proof that your wallet and x402 client complete a real paid call end to end, plus what the Lab knows about your wallet and which tool to try next.