Observed arrival · 2026-09-18
Limulus puts an inspection gate in front of agent payments
A payment-assurance system freezes agent-initiated transfers at the bank, compares them with approved records, and releases only matching payments.
- For
- Teams authorizing payments through autonomous agents
- Worth noticing
- Receipts are hash-chained and signed with Ed25519 for offline verification.
Field notes
The page frames payment assurance as a sequence of four stages: Test, Qualify, Protect, and Monitor. Its evidence model compares records written by separate parts of the payment flow rather than trusting an agent's account of its own actions. The homepage also exposes implementation details including nine REST endpoints, seven MCP tools, explanation codes, and Ed25519-signed receipt chains. A discrepancy remains in the displayed scenario counts: different sections cite 53, 56, and 60.
Observed signals
Read the marks
Editorial observations of this landing page, not a rating.
One card from the complete issue