Skip to main content
The Influship API supports the Machine Payments Protocol (MPP) on its paid public data endpoints. AI agents can pay per-request via Stripe cards (Shared Payment Tokens) or USDC on Tempo, no API key required. MPP and x402 are available on the same supported endpoints. Choose the protocol your client supports.

How it works

  1. Your agent makes a request to a supported paid endpoint without an X-API-Key header.
  2. The API responds with 402 Payment Required and a WWW-Authenticate: Payment ... header advertising the supported MPP methods.
  3. Your agent attaches an Authorization: Payment <credential> header proving payment authorization (signed by the user’s wallet or backed by a Stripe SPT).
  4. The API verifies, runs the request, and returns the response with a Payment-Receipt header.
The same 402 response includes both MPP and x402 challenges, so the client can pick. MPP settles before the endpoint runs. Once settlement succeeds, the payment is final and the response keeps its Payment-Receipt even if the endpoint later returns an error.

Pricing

MPP prices match x402 pricing — same 20% surcharge over the credit-based pricing. The total is rounded up once to whole cents, with a $0.01 minimum. Stripe card payments are offered only when that quote is at least $0.50; lower-priced requests use USDC or account credits. The API does not increase a quote to meet the card minimum. See the complete supported-operation price table. The quote is based on your requested limit or batch size and stays the same if fewer results are returned.

Supported rails

Eligible methods are advertised in the WWW-Authenticate header. Your client picks from that request’s offers. For variable-price operations, larger batches can qualify for cards even when smaller requests do not.

Quickstart

Use any MPP-compatible client. The reference SDK is mppx by wevm:
Or use AgentCash for a turnkey CLI wallet that speaks both x402 and MPP:

Discovery

Use the MPP manifest to discover the supported payment methods and operation templates. Its endpoints array is a subset for verification. The endpoint_templates array covers the full paid surface. The public OpenAPI spec defines request inputs and payment offers. To see the price and eligible methods for a specific request, send it without credentials and read the WWW-Authenticate header in the 402 response.
The header’s request value is base64url-encoded JSON. Use Challenge.fromResponseList to read the amount and currency. This example makes an ordinary HTTP request and prints the quote.
For this request, the Tempo offer contains amount: "10000" and currency 0x20c000000000000000000000b9537d11c60e8b50. That token is USDC.e on Tempo with six decimals, so the quote is $0.01.

Pick your protocol

Need higher rate limits or volume pricing?

Get an API key — same endpoints, lower per-request cost, no x402/MPP surcharge.