How it works
- Your agent makes a request to any Influship API endpoint without an
X-API-Keyheader. - The API responds with
402 Payment Requiredand aWWW-Authenticate: Payment ...header advertising the supported MPP methods. - Your agent attaches an
Authorization: Payment <credential>header proving payment authorization (signed by the user’s wallet or backed by a Stripe SPT). - The API verifies, runs the request, and returns the response with a
Payment-Receiptheader.
Pricing
MPP prices match x402 pricing — same 20% surcharge over the credit-based pricing.| Endpoint | Price |
|---|---|
POST /v1/search | whole-cent rounded total of \$0.3000 + \$0.0240 × requested_limit (capped at 100 results) |
GET /v1/creators/:id | \$0.0100 |
POST /v1/creators/lookalike | whole-cent rounded total of \$0.0180 × requested_limit (capped at 100 results) |
POST /v1/creators/match | whole-cent rounded total of \$0.0120 × creators_in_request |
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 |
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 |
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: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 |