MantisMeshcheckpoint.save
Checkpoint
Save portable execution state when work may outlive a process, model session, container, or machine.
POST /v1/checkpoints
Example use case
A research agent saves its sources, progress and next step before its session ends.
MantisMesh / Capabilities
Five primitives for agent continuity
Explore checkpoint.save, checkpoint.get, handoff.create, lock.acquire and recovery.register, with real API paths and concrete use cases.
checkpoint.get
Resume
Retrieve a live checkpoint owned by your wallet and continue from the state your application saved.
GET /v1/checkpoints/{checkpointId}
Example use case
A new session loads the same task state and resumes without repeating completed work.
handoff.create
Handoff
Delegate an encrypted snapshot to one named recipient wallet. Its lifetime cannot exceed the source checkpoint.
POST /v1/handoffs
Example use case
A planning agent passes a structured work package to a separate implementation agent.
lock.acquire
Lock
Coordinate access to a global logical key so multiple agents do not simultaneously act on the same resource.
POST /v1/locks
Example use case
Two workers compete for a task key before processing the same queue item. Your application respects the lock result.
recovery.register
Recover
Requires setup with an approved callback destination. Register heartbeats so your system can receive a signed notification when an agent stops responding.
POST /v1/recoveries
Example use case
An orchestrator receives a recovery notification after an agent misses its expected heartbeat window.
Composable by design
A small protocol.
Your orchestration.
Combine these primitives in your own agent framework. MantisMesh does not run your model, launch a replacement agent, or automatically discover a successor.
- Handoff retrieval
GET /v1/handoffs/{handoffId}
Recipient-authorized; no additional operation fee. - Lock release
DELETE /v1/locks/{key}
Owner-authorized; no additional operation fee. - Recovery heartbeat
POST /v1/recoveries/{recoveryId}/heartbeat
Owner-authorized; no additional operation fee.
All protected operations require a bearer session and idempotency key. Locks have no fencing token or renewal protocol. Recovery callbacks require operator-approved origins and are at-most-once attempts.
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.
Build for continuity
Give your agents a place to pick up.
Start with the wallet-authenticated REST API.