Pay with MPP (cards, Tempo USDC, agent-native)

Use the Influship API with Stripe cards or USDC on Tempo via the Machine Payments Protocol

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 coexists with x402 on the same endpoints. Pick whichever your client supports — we accept both.

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.

Pricing

MPP prices match x402 pricing — same 20% surcharge over the credit-based pricing.

Endpoint	Price
POST /v1/search	\$0.3000 + \$0.0240 × requested_limit, rounded up to the next whole cent with a $0.01 minimum (capped at 100 results)
GET /v1/creators/:id	\$0.0100
POST /v1/creators/lookalike	\$0.0180 × requested_limit, rounded up to the next whole cent with a $0.01 minimum (capped at 100 results)
POST /v1/creators/match	\$0.0120 × creators_in_request, rounded up to the next whole cent with a $0.01 minimum
GET /v1/raw/instagram/post/:shortcode	\$0.0200
GET /v1/raw/instagram/transcript/:shortcode	\$0.0600
GET /v1/raw/*	starts at \$0.0100 unless the endpoint cost is higher

You pay for what you ask for — limits and array sizes determine the price, not what we deliver.

Supported rails

Rail	Method	Settlement
Stripe card	stripe/charge	Stripe SPT (Shared Payment Token), USD via card or Link
USDC on Tempo	tempo/charge	On-chain USDC, settled in seconds

Both are advertised in the same WWW-Authenticate header. Your client picks based on which rails it supports.

Quickstart

Use any MPP-compatible client. The reference SDK is mppx by wevm:

import { Mppx, tempo } from 'mppx/client';
import { privateKeyToAccount } from 'viem/accounts';

const account = privateKeyToAccount(process.env.TEMPO_PRIVATE_KEY as `0x${string}`);

const mppx = Mppx.create({
  methods: [tempo({ account })],
});

const response = await mppx.fetch('https://api.influship.com/v1/search', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ query: 'fitness creators in NYC', limit: 25 }),
});

const data = await response.json();

Or use AgentCash for a turnkey CLI wallet that speaks both x402 and MPP:

npx agentcash@latest discover https://api.influship.com

Discovery

Influship endpoints are listed in the MPP services directory. Search for “Influship” or “influencer search” to find them programmatically.

Pick your protocol

If your agent supports…	Use
Both x402 and MPP	Either — pick based on rail availability
Only MPP	MPP (this guide)
Only x402	x402 guide
Neither (only API keys)	Get an API key for lower per-request cost and per-tier rate limits

Need higher rate limits or volume pricing?

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