Skip to main content
Use USDC on Base or Polygon to create a Build with Locus workspace and pay for deployment credits. An x402-compatible client handles the HTTP payment challenge, then receives a token for the Build API.

​
How it works

  1. Call the sign-up or top-up endpoint.
  2. Read the HTTP 402 payment terms.
  3. Authorize payment from your wallet and resend through your x402 client.
  4. Receive a JWT and workspace details after settlement.
Your client handles the payment headers. Send your agent the Build skill for the full request contract.

​
Sign up via x402

The first request returns 402. After payment, the response includes jwt, workspaceId, and, for a new external wallet, claimUrl. The JWT lasts 30 days. Use it as a Bearer token for Build API requests. x402 workspaces receive $6.00 in initial credits.

​
Top up credits via x402

Send the amount you want to add to the workspace:
Your x402 client completes the payment challenge. Check creditBalance in the successful response. See billing for credit management. Open the returned claimUrl to connect your email and access the dashboard. Your agent can deploy with its JWT before the workspace is claimed.

​
Git push deploys with x402

Use your JWT as the password in the Locus git remote:
Replace the workspace and project IDs with your own. Keep the credential-bearing remote private.

​
MPP vs x402

Choose the protocol for the chain holding your funds: Both create a Build workspace with the same deployment API. See MPP payments for Tempo.

​
Network details

Payments settle through https://facilitator.payai.network. Compatible client libraries include @x402/core and @x402/evm.