What is AMW

Agent Middleware (AMW) puts an authorization and transaction boundary in front of an MCP tool. A wallet scoped API key authenticates the caller. A Permit limits the tool, scope, Credits, and time available to that caller. A Call presents the Permit and a Request key. A Receipt records a finalized outcome.

For the configured upstream MCP tool, AMW allows at most one gateway dispatch and one ledger debit for an accepted Request key. Use the same key and payload for a retry. For a finalized Call, a retry with the same key returns the original receipt instead of dispatching again. A changed payload under that key is rejected.

The boundary is narrow. A gateway dispatch record cannot prove that the upstream tool acted. The upstream tool must also honor the forwarded Request key to avoid duplicate downstream effects. An uncertain delivery outcome needs reconciliation.

Start with the hosted sandbox quickstart, then read Permits, Calls and request keys, and Limits.

The source repository and organization contain the project. The website and API discovery document are separate public surfaces.

Apache 2.0 (gateway is Fair Source, FSL-1.1)