How it works
MPP (Machine Payments Protocol) uses an HTTP 402 payment challenge: the first request gets a price, the agent pays from its Tempo wallet, and the same request goes through. The agent pays from its own wallet, so your Locus spending controls don’t apply. To compare MPP with x402 and Locus agent wallet payments, see pay without a Locus account.Pricing
Catalog prices are estimates. The payment challenge shows the actual price and asset, so check both before signing.Refunds for one-time calls
If a provider fails after a one-time payment settles, Locus attempts to refund the USDC.e to the same Tempo wallet. Refunds can fail, so treat the payment as returned only when the error response shows bothrefunded: true and refundTxHash.
Origami usage sessions
Origami Research charges through an MPP usage session over server-sent events (a streamed response) instead of a one-time payment.- It bills $0.0012 per settled
origami_credit. maxCreditscaps the run’s budget, from 5 to 10,000 credits.- The suggested deposit funds the payment channel, and the final charge follows billable usage during the stream.
- If the stream disconnects or fails partway, credits already metered aren’t automatically refunded.
Run a Locus task
Give Locus one goal and it plans the work, calls paid tools, checks its claims against the evidence, and returns an answer or a table. You pay a ceiling up front, $1.00 by default, and get back what the task doesn’t spend. See run a Locus task.Supported providers
MPP supports 37 provider namespaces, shown as 35 dashboard provider groups because the Diffbot namespaces share one group. Send your agent the provider reference for request fields, examples, prices, and the correct MPP host:A–D
E–M
O–Z
Each provider host also exposes an OpenAPI 3.1 discovery document at
https://<namespace>.mpp.paywithlocus.com/openapi.json.
Next steps
Pay without a Locus account
Compare MPP, x402, and Locus agent wallet payments.
Run a Locus task
Hand Locus a goal and pay a capped amount.