MantisMeshLast updated: October 31, 2026. These are early-service operating terms.
Service scope
MantisMesh V1 provides portable JSON checkpoints, wallet-to-wallet handoffs, logical locks and heartbeat-based recovery callbacks. Your application executes work and chooses how to resume. We do not select replacement agents, hold your wallet keys or promise uninterrupted availability.
Your responsibilities
Use only wallets and data you are authorized to control. Keep wallet keys and bearer sessions secure. Do not submit illegal content, attempt unauthorized access, bypass limits or abuse the service. Do not rely on a logical lock after its expiry or use this early service as your sole copy of critical data.
Prices and payments
When enabled, paid operations use the advertised x402 requirements in USDC on Solana. Review pricing, the receiving wallet, network and spend ceiling before signing. Retrieval is charged separately from saving; a lock contention attempt is also charged. A transaction approval authorizes payment. Blockchain settlement is irreversible; any service credit or refund requires operator review and is not automatic.
Retries and uncertain settlement
Use a distinct Idempotency-Key for each operation. Retry the exact method, path, key and JSON to recover an existing result. After an uncertain settlement, do not pay again with a new key; retain the public receipt and request operator reconciliation. Concurrent expiry or quota changes can prevent fulfillment after settlement and need review.
Retention and availability
Expiry, quotas and delete-after-read rules apply even if your application is offline. Recovery delivery is best-effort and at most one attempt. There is no published service-level agreement or compliance certification. Read the security model and privacy policy before use.