What it does
Agent Middleware is a gateway between agents and a configured upstream tool. A permit names which tool an agent may use, how much it may spend, and when the permit ends. A request key is a name given to one action so that a retry is recognized as the same action. In the quickstart, you get a demo key and a wallet ID, export AMW_API_KEY and AMW_WALLET_ID, and run the Python example permit_echo_retry.py from the amw-demo repository. The first call creates a permit and prints the receipt ID. Agent Middleware says that for an accepted request key on the configured upstream tool, a retry with the same key returns the original receipt instead of dispatching again. A receipt records the gateway decision and the linked outcome. The demo key works only in the demo sandbox, and the site offers a pilot started by email.
Capabilities
- Agent Middleware says one accepted request key permits at most one gateway dispatch to the configured upstream tool and at most one debit.
- Receipt signatures can be checked offline.
- Receipts sign hashes of the request and response, not the content, and do not prove the tool was right or the downstream effect.
- The delivery_uncertain status means the call was charged but it is unknown whether the tool finished.
- Agent Middleware says it never resends a delivery_uncertain call on its own.
When to use it
- You need an agent action to be retried without dispatching it again to the configured upstream tool.
- You need to limit which tool an agent may use, how much it may spend, and when that ends.
- You need to check a receipt signature offline.
