Skip to main content
MPP lets an agent call supported Locus tools and pay inline through HTTP 402 challenges. No Locus account or pre-funded Locus wallet is required; the payer uses a Tempo wallet funded with USDC.e.

​
How it works

1

Send the request

Send the provider request to its MPP endpoint without a payment credential.
2

Receive a 402 challenge

The response identifies the price, USDC.e token, Tempo recipient, and payment requirements.
3

Authorize payment

Inspect the challenge, sign the payment with the Tempo wallet, and resend the same request with the resulting payment credential.
4

Receive the provider response

Locus verifies payment and dispatches the validated request to the provider.

​
Supported providers

MPP supports 37 provider namespaces across 35 dashboard provider groups. The complete Locus-managed registry has 50 namespaces across 48 groups; Diffbot, Diffbot KG, and Diffbot NL appear as one dashboard group. Each generated file below contains the current endpoint paths, request fields, examples, pricing, and provider-specific MPP host. The current machine-readable list is:
Fetch only the provider needed for the current task. For example: curl -s https://paywithlocus.com/mpp/parallel.md.
Each provider host also exposes an OpenAPI 3.1 discovery document at https://<namespace>.mpp.paywithlocus.com/openapi.json.

​
Pricing

The HTTP 402 challenge is the authoritative authorization request. Inspect its amount and asset before signing; generated reference prices are estimates and can be request-dependent. Most supported tools use one payment per request. Origami Research is the exception described below.

​
Refunds for one-time calls

If an upstream call fails after a one-time MPP payment settles, Locus attempts an automatic USDC.e refund to the same verified Tempo payer. A successful refund is confirmed by refunded: true and refundTxHash in the error response.
Refund delivery is best-effort. If the payer cannot be resolved or the refund signer, RPC, or transfer fails, the error response omits those confirmation fields. Do not record a refund until both fields are present.
When a provider returns 429, Locus records its cooldown so later requests can be rejected before another payment is accepted. The first failed paid call still follows the best-effort refund path above.

​
Origami usage sessions

Origami Research uses an MPP usage session over server-sent events instead of a one-time payment. It bills $0.018 per settled origami_credit. The required maxCredits field accepts a whole number from 5 through 10,000. It is both the hard run budget and the basis for the suggested channel deposit; the deposit is a funding hint, not the amount spent. Locus charges only cumulative billable credits reported during the stream.
Already metered Origami credits are not automatically refunded if the stream later disconnects or fails.