Agents Need Receipts, Not More Tool Calls
summary
An open protocol called Froglet publishes a service, another node discovers and invokes it, and a signed receipt proves the whole interaction; the demo runs a simple add-two service (7+5 → 12) against a remote trial node and a local Docker install. Nodes generate keypairs and sign a verifiable chain, temporary tokens (15 minutes) appear, and the system exposes one flow Descriptor to Offer to Quote to Deal to Receipt while integrating with MCP and OpenClaw/NemoClaw via a single Froglet node.
AI-written summary · about
chapters (12)
- 0:00Agentic automation in life sciences
- 1:07More tools vs agent collaboration
- 2:32Agents as supply chain chefs
- 3:55Agents managing budgets
- 5:02Froglet for verifiable transactions
- 7:33Froglet nodes as providers
- 9:42Froglet with agent harnesses and LLMs
- 10:59Demo: Froglet remote use
- 13:53Demo: Froglet local Docker
- 15:21Demo: Froglet with Claude MCP
- 17:51Froglet benefits for agents
- 18:34Froglet in collaborative science
related talks
19mSecuring Agents with Open Standards
18mAgents With Allowances, Embedded Wallet Tools For A New Economy
31mOmniBOR: Bringing the Receipts for Supply Chain Security
32mSaving Bug Bounties from AI Slop
50mAgents That Talk Back: MCP, ACP, A2A, Oh my!
06mLightning Talk: One Header, Portable Proof: PEAC Receipts for K8s APIs
15mIntroduction to the Agent eXchange Layer (AXL)
09mPublic Goods for Agents