MantisMesh
PUBLIC PAID ACCESS ENABLEDView status ↗
Infrastructure for agent continuity

Portable state and coordination for autonomous agents.

MantisMesh gives agents durable checkpoints, secure handoffs, distributed locks, and recovery state across providers, sessions, and machines. Pay only when you use it with x402.

Get StartedView API
Wallet-ownedEncrypted at restExplicit retention
State moving through a meshA conceptual network connecting two autonomous agents through MantisMesh and encrypted state.ABMANTISMESHSAVERESUMEENCRYPTED STATE
ONE TASK. MANY RUNTIMES.CONCEPTUAL FLOW
POST /v1/checkpoints · authenticated request
POST /v1/checkpoints HTTP/1.1
Host: api.mantismesh.com
Authorization: Bearer <session-token>
Idempotency-Key: research-042-save-01
Content-Type: application/json

{
  "task_id": "research-042",
  "payload": {
    "step": 7,
    "next": "synthesize"
  },
  "retention": "24h"
}
1h → 30dEXPLICIT RETENTION TIERS
64 KBMAX CHECKPOINT PAYLOAD
USDC / SolanaX402 PER-OPERATION PAYMENTS
Your walletYOUR STATE OWNERSHIP
01 / The primitives

Useful work shouldn’t
end with a session.

Agent execution is temporary. Your progress needs a deliberate place to live. Save it, move it, coordinate around it, and register what should happen if execution stops.

01 /

Checkpoint

Persist the context that matters. Retrieve it when your agent is ready to resume.

Explore capability
02 / Take your state with you

Change the runtime.
Keep the progress.

Models change. Processes restart. Work moves between machines. MantisMesh stores the portable JSON your application needs, with ownership attached to a Solana wallet.

Bring your own model, framework, and execution environment. There is no requirement to run your agent inside MantisMesh.

See how handoffs work
01Current agentWorking state
02MantisMesh checkpointEncrypted + TTL
03Next session or agentResume from state
State continuity / conceptual architectureRuntime independent
Agent AAny model / runtime
MantisMeshWallet-authorized handoff
Encrypted stateEncrypted · explicit expiry
Agent BRecipient wallet

The receiving agent loads the snapshot into its own runtime. MantisMesh carries state; your application carries execution.

03 / A machine-native exchange

A request.
A payment.
A useful operation.

From $0.005 per paid operation. No MantisMesh subscription required.

Retention affects checkpoint save pricing. Payments settle in USDC on Solana through x402.

Explore transparent pricing

  1. Authenticate your wallet

    Sign a one-time challenge and receive a short-lived bearer session.

  2. Discover payment requirements

    An enabled paid endpoint returns HTTP 402 and its x402 terms.

  3. Settle, then fulfill

    Your client signs the payment. The service verifies and settles it before executing the operation.

  4. Retry with the same operation key

    Keep the request identical to recover its stored result without another settlement.

04 / Deliberate boundaries

Designed around
ownership and expiry.

Explicit rules for who may access state, how it is stored, and how long it remains available. Clear limits, without zero-knowledge claims.

Wallet-authorized access

Challenge signatures establish ownership. A named handoff recipient accesses its own delegated snapshot.

Encryption before storage

Application-level encryption protects stored payloads. The service decrypts authorized reads; keys are operator-managed.

Nothing retained by default forever

Explicit expiry, scheduled cleanup, optional delete-after-read, and bounded payload and wallet quotas.

Read the security model

Build for continuity

Give your agents a place to pick up.

Start with the wallet-authenticated REST API.

Read the quick start