MantisMeshSmall surface. Explicit contracts.
Production API base: https://api.mantismesh.com. The human site is separate from the API deployment. Use the OpenAPI document for request/response schemas and full error definitions.
Authentication and request headers
Create a challenge at POST /v1/auth/challenge, then verify its signature at POST /v1/auth/verify. Protected requests use Authorization: Bearer <token> and Idempotency-Key. POST bodies use Content-Type: application/json.
When enabled, paid operations advertise x402 V2 terms via PAYMENT-REQUIRED on an HTTP 402. Clients submit PAYMENT-SIGNATURE; settlement receipts use PAYMENT-RESPONSE. The payment wallet must match the authenticated wallet.
V1 operation reference
| Method | Path | Operation |
|---|---|---|
| POST | /v1/checkpoints | checkpoint.save |
| GET | /v1/checkpoints/{checkpointId} | checkpoint.get |
| POST | /v1/handoffs | handoff.create |
| POST | /v1/locks | lock.acquire |
| POST | /v1/recoveries | recovery.register |
| GET | /v1/handoffs/{handoffId} | Recipient-authorized handoff retrieval |
| DELETE | /v1/locks/{key} | Owner-authorized lock release |
| POST | /v1/recoveries/{recoveryId}/heartbeat | Recovery heartbeat |
Discoverable by machines.
The service publishes capability descriptions, JSON schemas, pricing, and x402 Bazaar metadata so a client can inspect the contract before choosing an operation.
- Capability catalog — methods, paths, constraints, and intended uses.
- OpenAPI specification — complete request and response contract.
- Pricing — authoritative amounts in integer millionths of USD.
- Discovery metadata — individually discoverable capability declarations.
- API llms.txt — machine-oriented service guide.
- Website llms.txt — concise MantisMesh documentation index.
PayAI settles USDC to the operational Solana wallet before fulfillment. Wallet transfers are a separate payment path; State storage and payment settlement are separate.