Skip to content
APIStead

Seller tools

Check the 402 before an agent does.

A valid payment challenge is the first contract with a buyer. Validate the status, headers, price, network and payout wallet before you list.

No account requiredNo payment sent

The validator calls the endpoint once without payment and checks the 402 challenge. It does not pay, sign, or store the response. HTTPS only; private and internal addresses are blocked.

Already valid?

Claim the endpoint so you can manage metadata, payout wallet and verification history.

Request a claim

Need an integration?

The payments guide covers the 402 shape, the facilitator, Base USDC and the provider-side checklist.

Read the payments guide

Common questions

What does the validator check?+

It calls your endpoint once without payment and checks that it returns HTTP 402 with a readable payment challenge. It inspects the scheme, network, asset, amount, payTo wallet and Bazaar extension. It does not pay or sign anything.

Why does it only accept HTTPS?+

A public paid endpoint should be reachable over TLS. The validator also blocks private and internal addresses so it cannot be used to probe internal infrastructure.

Does a passing check mean my endpoint is verified?+

No. A valid 402 only proves that the endpoint asks to be paid. Settlement verification requires a real paid call that returns product and a public receipt.

How do I get the verified badge?+

Submit the listing, then request a paid verification check. APIStead pays one named route from its own wallet, checks the response and publishes the receipt. The badge covers that route, not the whole listing.