How it works
- Your agent makes a request to a supported paid endpoint without an
X-API-Keyheader. - The API responds with
402 Payment Requiredand aPAYMENT-REQUIREDheader containing the price and payment instructions. - Your agent signs a USDC payment on Base and retries the request with a
PAYMENT-SIGNATUREheader. - The API verifies the payment, runs the request, and settles the payment on-chain.
PAYMENT-SIGNATURE is the current x402 v2 header. Influship also accepts X-PAYMENT for compatibility with x402 clients that still emit the earlier header name.
Once settlement succeeds, the payment is final, including when the endpoint response is an error. Successful settlement is reported in the PAYMENT-RESPONSE header.
Pricing
x402 prices include a 20% surcharge over API-key/OAuth prices, rounded up to whole cents with a $0.01 minimum. See the API-key/OAuth price table to compare costs.
The quote is based on your requested limit or batch size. A search returning fewer creators keeps the same quoted price.
Quickstart
Use any x402-compatible client. The Coinbase SDK is the reference:Discovery
Use the x402 Bazaar discovery APIs to search the current catalog. A catalog result describes an indexed resource; the API’sPAYMENT-REQUIRED header supplies the quote for your actual request. The supported endpoints above define Influship’s payment surface independently of catalog coverage.