internet-court

Routes agent-to-agent commerce tasks to mandate, payment, escrow, and dispute-resolution protocols.

30.5k|3.5k|Updated Jul 4, 2025
One-click install
npx skills add https://github.com/davila7/claude-code-templates --skill internet-court
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: internet-court
Source: https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/internet-court
Command: npx skills add https://github.com/davila7/claude-code-templates --skill internet-court

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agents that transact with other agents or paid services lack enforceable trust boundaries: users cannot safely delegate spending authority, verify counterparties, or resolve disputes when something goes wrong.

Core Features & Use Cases

  • Bounded Authority from Mandates: Converts natural-language mandates into scoped delegations using ERC-7710/7715 instead of unlimited approvals.
  • Payment and Escrow Routing: Directs tasks to x402, MPP, and escrow protocols for machine payments between agents.
  • Verification and Dispute Resolution: Routes disputes to GenLayer, Kleros, or Intelligent Oracle layers with signed evidence such as transaction hashes and receipts.
  • Use Case: A user wants their agent to pay for a paid API (HTTP 402) with a capped budget; the skill forms a bounded mandate, executes the x402 payment, and produces verifiable receipts.

Quick Start

Ask the agent to create a bounded spending mandate and pay a paid API endpoint using x402 with testnet funds.

Frequently Asked Questions about internet-court

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I give an AI agent bounded spending authority?

Create a natural-language mandate that the skill converts into a scoped delegation using ERC-7710 or ERC-7715, rather than granting unlimited approvals. Keep initial demonstrations on testnets to limit risk.

What is x402 and how do agents pay for APIs with it?

x402 is a payment protocol for HTTP 402 responses that lets agents pay for APIs and services programmatically. The skill routes payment tasks to the x402 layer and produces verifiable receipts for each transaction.

How are disputes between agents resolved?

Disputes are routed to a verification layer using GenLayer, Kleros, or an Intelligent Oracle for independent review. The skill discloses the boundary between the decision and its on-chain enforcement.

Does this skill include all the protocol implementations?

No, this is a condensed router entry point. The full package with roughly 70 vendored protocol and connector sub-skills lives at the internet-court GitHub repository and can be installed or fetched on demand.

When should I not use delegated agent payments?

Avoid unbounded agent spend or unlimited approvals in any case, and avoid mainnet funds during early experimentation. The skill is designed for bounded, testnet-first workflows with revocable authority.