internet-court

Topics in the source

• Internet Court
• When to use
• The stack it routes to
• How to use

The trust layer for agent-to-agent commerce. It turns "I want my agent to transact, but I don't trust it with money" into an enforceable workflow: a natural-language mandate becomes bounded authority, payments, escrow, signed evidence, independent review, and revocation or dispute resolution when something goes wrong. This is a condensed entry point. The full package — a master router plus 70 vendored protocol and connector skills — lives at https://github.com/internet-court/internet-court-skill (homepage: https://internetcourt.org). Install the whole package for the sub-skills, or let this router fetch them on demand from the repo. Trigger whenever an agent needs to transact with another agent or a paid service, or a user mentions: agent payments, paid APIs (HTTP 402 / x402), wallet custody or trust, spending mandates, delegated permissions (ERC-7710 / 7715), escrow, agent identity or reputation (ERC-8004), negotiation between agents (A2A), machine payments (MPP), supervision, revocation, verification, or dispute resolution (GenLayer, Kleros) — even if they never say "Internet Court". | Layer | Concern | Examples in the full package | |---|---|---| | 1 | Identity & reputation | ER

This is an excerpt. Refer to the complete source and its current requirements.