internet-court/internet-court-skill

The trust layer for agent-to-agent commerce — natural-language mandates, ERC-7710 delegated permissions, x402 payments, escrow, and dispute resolution as one open, catch-all Agent Skill / Claude Code plugin.

Internet Court Skill

What it is

Internet Court is an open skill (a package an AI agent can load and use) that lets AI agents make deals with each other and — critically — agree up front on how disputes will be settled, so a broken deal doesn't stall the whole economy of autonomous agents.

The problem it solves

Agents already transact, negotiate, and pay one another without humans in the loop. The building blocks (payments, escrow, identity, contracts) exist, but they're fragmented — each standard covers one slice and assumes everything goes right. When a deal goes wrong, every layer passes the problem down the line. There was no shared way for agents to trust each other.

What it does

Two things:

  1. Connects the fragmented ecosystem — a single master skill (SKILL.md) that routes an agent to the right sub-skill for each step of a deal (discovery, negotiation, contracts, payment, execution, dispute resolution).
  2. Adds adjudication — when two agents make a deal, they also agree in writing who will judge a dispute if one arises (GenLayer, Kleros, UMA, or whatever they choose). Most deals settle fine; the skill standardizes how the contract is structured around that choice for the cases that go wrong.

The six layers of agentic commerce

Layer What it handles Standards cited In this repo?
1. Discovery, identity & reputation Finding counterparties and vetting them ERC-8004, ERC-7857 Yes (via vendored ChainGPT, BNB Chain, Starknet, Certisyn skills); ERC-7857 has no public skill yet
2. Negotiation Agents talking terms A2A Yes (vendored TerminalSkills, OpenServ)
3. Contracts & obligations Formalizing the deal ERC-7710, ERC-8183, Arkhai Yes (Arkhai, MetaMask, GenLayer connector); ERC-8183 has no public skill yet
4. Payment & escrow Moving and holding funds safely x402, MPP, APP Yes (Yellow, Coinbase, ChainGPT, OKX, Tempo, Nansen, Privy)
5. Execution Actual work: compute, data, value rails — Yes (0G, AntSeed, LI.FI, Chainbase, Heurist, NEAR, Starknet, Solana, Nansen, OKX, AltLayer, BNB Chain packs)
6. Verification & disputes Judging when things go wrong GenLayer, Kleros, UMA Yes (GenLayer, Kleros, Certisyn, connectors); UMA has no public skill yet

The 6th layer is the one Internet Court exists to add — every other layer assumes success.

How it's built

  • One catch-all skill — only the root SKILL.md is registered and triggered; it routes to sub-skills on demand, from disk (if the whole repo is installed) or fetched from GitHub raw URLs as a fallback.
  • Two kinds of content:
    • First-party — only the master skill and connector adapters. The repo never re-implements a protocol's own skill.
    • Vendored — 92 skills from 34 owners, committed copies of publicly published official skills, pinned by source + hash in skills-lock.json.
  • No single vendor — built by a consortium of ~30 founding members spanning every layer (GenLayer, MetaMask, OKX, NEAR, Starknet, x402, 0G Labs, ZKsync, Nansen, Kleros, Privy, AntSeed, UMA, Arkhai, BNB Chain, LI.FI, Chainbase, etc.). Openly governed. Any agent can adopt it now.

Installation

Works with Claude Code (recommended, via /plugin marketplace add internet-court/internet-court-skill), npx skills, Codex, opencode, OpenClaw, and Hermes. Installation is just cloning the repo or registering the root skill; sub-skills load on demand. Some vendored skills need their provider's credentials (API keys) to actually act.

License

First-party work is MIT. Vendored skills remain under their own upstream licenses. © 2026 Internet Court Consortium.

Related

  • Project
  • Project
  • Project
  • Project
  • Project