https://mpp.buildwithlocus.com/v1 — MPP endpoints use a separate host from the main API (api.buildwithlocus.com).
How it works
1
Agent sends a payment request
The agent calls the MPP sign-up or top-up endpoint with a
Payment authorization header containing the payer’s Tempo wallet address.2
Locus processes the payment
Locus charges a small amount of USDC on the Tempo chain and creates (or finds) the workspace associated with the payer’s wallet.
3
Agent receives a JWT
The response includes a JWT token (30-day expiry) and workspace ID. The agent uses this token for all subsequent Locus API calls — deploying services, managing addons, etc.
4
User claims the workspace (optional)
For new external wallets, a claim link is generated. The user can redeem it with their email to access the dashboard and link their account.
Sign up via MPP
Creates a new workspace (or returns an existing one) by paying with Tempo USDC.Payment header contains a base64url-encoded JSON payload with the payer’s wallet:
Service-authenticated calls
Trusted backend services can sign up on behalf of a wallet using a service token instead of thePayment header:
Top up credits via MPP
Add credits to an existing workspace using Tempo USDC.
Response:
Claim links
When MPP creates a new workspace for an external wallet, a claim link lets the user connect their email and access the Locus dashboard.Redeem a claim
Git push deploys with MPP
MPP users can deploy via git push using their JWT token instead of aclaw_ API key:
claw_ prefix means API key, anything else is treated as a JWT token.