M0 developer preview

Governed wallet infrastructure for agentic teams

Alloy exposes a modular control plane for WalletKit, PolicyKit, and Mesh. Start with mock-backed receipts and stable public contracts while private custody internals stay out of the docs.

Start quickstart Open API reference

POST /v1/wallets/actions/simulate

{
  "policy": "agent-low-risk-transfer",
  "asset": "USDC",
  "amount": "250.00",
  "destination": "design-partner-sandbox"
}

receipt_status: "approved_mock"
backend_route: "mesh-m0-local-quorum"
human_approval_required: false

What you can test now

Model the wallet

Create a sandbox wallet intent with policy scope, signer topology, and receipt requirements.

Simulate action approval

Run a low-risk transfer through the mock policy evaluator and inspect the receipt shape.

Trace contract versions

Tie SDK, OpenAPI, and Mesh contract versions together before any live signing path is exposed.

Public developer surface

Module	Role	M0 exposure
WalletKit	Application-facing wallet abstraction	Quickstart, action simulation, receipts
PolicyKit	Policy and approval control plane	Mock policy checks, escalation fields
Mesh	Cryptographic execution substrate	Public contract and mock quorum receipts

Try the sandbox receipt

This is a safe client-side mock. It does not touch live custody, production keys, or private wallet internals.

{
  "status": "ready",
  "message": "Submit the sandbox form to generate a mock receipt."
}

Public/private boundary

Public in M0

WalletKit and PolicyKit developer flows
Mock-backed Mesh contract behavior
OpenAPI/Swagger references and version matrix
Receipts, approval fields, and sandbox examples

Private until approved

Live signer topology and custody implementation details
Partner-specific endpoints or secrets
Sepior/MPC operating internals beyond public behavior
Production policy thresholds and customer data