trustless-agents
ERC-8004 Trustless Agents — on-chain agent identity + reputation. Resolve an agent by id (Identity Registry ERC-721 → owner + AgentCard), list the canonical registry addresses, and generate a spec-compliant agent registration card (registration-v1, with x402 support + trust models). Custody-free, read + scaffolding. Triggers: ERC-8004, trustless agent, agent identity, agent registry, AgentCard, agent reputation, on-chain agent, A2A, agent discovery, agent card, 8004.
git clone --depth 1 https://github.com/internet-court/internet-court-skill /tmp/trustless-agents && cp -r /tmp/trustless-agents/vendored/chaingpt/trustless-agents ~/.claude/skills/trustless-agentsSKILL.md
# ERC-8004 Trustless Agents skill
ERC-8004 (draft EIP) gives AI agents a portable on-chain identity + reputation:
the **Identity Registry** is an ERC-721 ("AgentIdentity") deployed as a singleton
at the vanity address `0x8004A169…` across many chains (verified on Base
mainnet). An agent's `tokenURI` points to an AgentCard describing what it does,
its endpoints (A2A/MCP), trust models, and x402 support.
## Tools
| Tool | Purpose |
|---|---|
| `chaingpt_erc8004_resolve_agent` | Resolve `agentId` → owner + decoded AgentCard (handles `data:` and https/ipfs tokenURIs). Read-only. |
| `chaingpt_erc8004_registries` | The canonical Identity + Reputation registry addresses and the chains they're on. |
| `chaingpt_erc8004_agentcard` | Generate a `registration-v1` AgentCard JSON (name, services, `supportedTrust`, `x402Support`) to host at the tokenURI / `/.well-known/agent-card.json`. Optionally emits the `data:` URI form. |
`chaingpt_erc8004_resolve_agent agentId=0 chain=base` → the Genesis Agent.
## Scope
Read + scaffolding are shipped and verified. The **write path** (register /
giveFeedback / validation) is intentionally deferred: ERC-8004 is a draft whose
write ABIs (especially the Validation Registry) are still being revised, so we
don't ship unverified identity/reputation-mutating calldata. Generate the
AgentCard here, then register via the project's reference contracts once the
write ABI is final.
Reads use a public-RPC fallback chain; set `BASE_RPC_URL` for reliability.
0 ChainGPT credits.Entry point for Internet Court — the trust layer for agent-to-agent commerce. Use 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 concerns, spending mandates, delegated permissions (ERC-7710/7715), escrow, agent identity or reputation (ERC-8004), negotiation between agents (A2A), agent jobs (ERC-8183), machine payments (MPP, AP2), supervision of agent behavior, revocation, verification, or dispute resolution (GenLayer) — even if they never say "Internet Court". Routes to the vendored protocol skills and connector skills in this package.
Connect GenLayer Intelligent Contract decisions to ERC-7710-style delegated authority. Use when an agent needs to design the interface, message schema, relayer/bridge path, EVM revocation controller, constraint updates, proof/finality assumptions, and failure handling that turn a GenLayer agent-performance review into ERC-7710 revocation or policy changes.
Internet Court adapter for GenLayer Intelligent Contract supervision. Use to specify agent-performance rubrics, evidence schemas, decision outputs, and ERC-7710 connector expectations, while delegating actual GenLayer contract writing, linting, testing, deployment, and CLI interaction to the official GenLayer skills at https://skills.genlayer.com/.
Design and implement demos combining x402 HTTP payments with ERC-7710 smart contract delegations and ERC-7715 wallet permission requests for subscriptions, bounded agent budgets, recurring spend, pay-per-use APIs, and agentic commerce.
0G Compute Network guide for decentralized AI inference, fine-tuning, and GPU services. Covers chatbots, image generation, speech-to-text, SDK integration (0g-serving-broker), processResponse API, broker.inference methods, CLI commands (0g-compute-cli), and account management. Use this skill for any 0G compute, 0G AI, or decentralized GPU question.
Use this skill when the user asks to list, create, inspect, update, disable, re-enable, or revoke AltLLM Portal API keys for external agents or applications. Do NOT use for wallet login, billing history, or payment links.
Use this skill when the user asks to log in or out with a wallet session, fetch a wallet sign-in challenge, verify an externally signed challenge, or troubleshoot AltLLM Portal wallet login for the local altllm CLI. Do NOT use for API key management, billing history, or payment links.
Use this skill when the user asks to inspect AltLLM Portal balance, redeem a promo code, review billing transactions, or view usage analytics by period, model, or API key using the local altllm CLI. Do NOT use for API key lifecycle management or payment-link execution.