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 the credit-based pricing — the “x402 tax” covers settlement costs. For high-volume use, an API key is cheaper.
You pay for what you ask for, not what we deliver. If a search returns fewer creators than requested, the price still reflects the requested cap.