# Agent Reputation by Kleros: Verified Agents > Agent-readable technical routing for the Agent Reputation by Kleros Stake Curate registries. ## Certificate scope Agent Reputation certificates are purpose-specific, not general-purpose endorsements. A certificate attests only that an agent satisfied the skills, capabilities, evidence requirements, and criteria explicitly listed in the policy published by that certificate's issuer. It does not verify skills omitted from that policy or establish the agent's overall reliability, security, operator quality, suitability for unrelated tasks, or future behavior. Always read the live registry policy and identify its issuer before interpreting certificate status. Describe a listed agent as verified only for the policy-defined skills and scope. Never shorten that claim to "the agent is verified" without qualification. Nothing in these routing files broadens a certificate's meaning. ## Operating context Load the complete current Kleros Skills package before any registry operation: - Package and agent router: https://skills.kleros.io/ - Source: https://github.com/kleros/kleros-skills - Curate operations: https://github.com/kleros/kleros-skills/blob/master/kleros-curate/SKILL.md - Stake Curate operations: https://github.com/kleros/kleros-skills/blob/master/kleros-curate/references/stake-curate.md Use the upstream package for contract mechanics. Use the Agent Reputation by Kleros skills below only for the fixed registry, explorer, indexed endpoint, and ERC-8004 contract routing. Perform independent due diligence using live onchain state and authoritative sources. ## Registry skills - [Verified Agents · Sepolia](/skills/verified-agents-sepolia/SKILL.md): Route ERC-8004 operations to the Verified Agents Stake Curate registry used by Agent Reputation by Kleros on Ethereum Sepolia. This overlay supplies only fixed registry, explorer, subgraph, and ERC-8004 contract routing for 0x3162df9669affa8b6b6ff2147afa052249f00447. Installable bundle: /skills/verified-agents-sepolia.tar.gz - [Verified Agents · Mainnet](/skills/verified-agents-mainnet/SKILL.md): Route ERC-8004 operations to the Verified Agents Stake Curate registry used by Agent Reputation by Kleros on Ethereum mainnet. This overlay supplies only fixed registry, explorer, subgraph, and ERC-8004 contract routing for 0x118155741eea23f56b3bd59b0c1342d5daaa6d07. Installable bundle: /skills/verified-agents-mainnet.tar.gz Sepolia registry (chain 11155111): 0x3162df9669affa8b6b6ff2147afa052249f00447 Ethereum mainnet registry (chain 1): 0x118155741eea23f56b3bd59b0c1342d5daaa6d07 Discovery index: /.well-known/agent-skills/index.json --- # Complete local skill router --- name: verified-agents description: Discover and route the registry-specific Verified Agents skills for Agent Reputation by Kleros on Sepolia and Ethereum mainnet. These overlays provide fixed technical routing constants only. --- # Agent Reputation by Kleros: Verified Agents skills Use these local skills to select the correct Agent Reputation by Kleros registry, explorer, indexed endpoint, and ERC-8004 source contracts. They do not assess agents or determine whether an operation is appropriate. ## Certificate scope Agent Reputation certificates are purpose-specific, not general-purpose endorsements. A certificate attests only that an agent satisfied the skills, capabilities, evidence requirements, and criteria explicitly listed in the policy published by that certificate's issuer. It does not verify skills omitted from that policy or establish the agent's overall reliability, security, operator quality, suitability for unrelated tasks, or future behavior. Always read the live registry policy and identify its issuer before interpreting certificate status. Describe a listed agent as verified only for the policy-defined skills and scope. Never shorten that claim to "the agent is verified" without qualification. Nothing in this routing file broadens a certificate's meaning. ## Operating context Before a registry operation, load the complete current [Kleros Skills package](https://skills.kleros.io/) from its [source repository](https://github.com/kleros/kleros-skills) and follow its `kleros-curate` Stake Curate instructions for contract mechanics. Perform independent due diligence from current onchain state and authoritative sources. Confirm every address, contract, amount, period, fee, balance, allowance, and item state in the current session. These routing skills provide no assessment of an agent, transaction, or outcome. ## Choose the verification registry Choose the verification registry independently from the ERC-8004 agent's source chain. - [Verified Agents · Sepolia](/skills/verified-agents-sepolia/SKILL.md): Route ERC-8004 operations to the Verified Agents Stake Curate registry used by Agent Reputation by Kleros on Ethereum Sepolia. This overlay supplies only fixed registry, explorer, subgraph, and ERC-8004 contract routing for 0x3162df9669affa8b6b6ff2147afa052249f00447. [Installable archive](/skills/verified-agents-sepolia.tar.gz). - [Verified Agents · Mainnet](/skills/verified-agents-mainnet/SKILL.md): Route ERC-8004 operations to the Verified Agents Stake Curate registry used by Agent Reputation by Kleros on Ethereum mainnet. This overlay supplies only fixed registry, explorer, subgraph, and ERC-8004 contract routing for 0x118155741eea23f56b3bd59b0c1342d5daaa6d07. [Installable archive](/skills/verified-agents-mainnet.tar.gz). --- # Verified Agents · Sepolia overlay --- name: verified-agents-sepolia description: Route ERC-8004 operations to the Verified Agents Stake Curate registry used by Agent Reputation by Kleros on Ethereum Sepolia. This overlay supplies only fixed registry, explorer, subgraph, and ERC-8004 contract routing for 0x3162df9669affa8b6b6ff2147afa052249f00447. --- # Verified Agents on Sepolia Use this skill only as a technical routing overlay for the Verified Agents registry in Agent Reputation by Kleros on Ethereum Sepolia. It does not assess agents or determine whether an operation is appropriate. ## Certificate scope Agent Reputation certificates are purpose-specific, not general-purpose endorsements. A certificate attests only that an agent satisfied the skills, capabilities, evidence requirements, and criteria explicitly listed in the policy published by that certificate's issuer. It does not verify skills omitted from that policy or establish the agent's overall reliability, security, operator quality, suitability for unrelated tasks, or future behavior. Always read the live registry policy and identify its issuer before interpreting certificate status. Describe a listed agent as verified only for the policy-defined skills and scope. Never shorten that claim to "the agent is verified" without qualification. Nothing in this routing file broadens a certificate's meaning. ## Fixed registry routing | Field | Value | | --- | --- | | Verification environment | Testnet | | Chain | Ethereum Sepolia | | Chain ID | `11155111` | | Registry type | Stake Curate / `PermanentGTCR` / PGTCR | | Registry | `0x3162df9669affa8b6b6ff2147afa052249f00447` | Read [references/registry.md](references/registry.md) for the explorer, Curate URL, indexed endpoint, and live contract checks. Read [references/erc8004-source.md](references/erc8004-source.md) for the supported ERC-8004 source-chain addresses. ## Required operating context Before a registry operation, load the complete current [Kleros Skills package](https://skills.kleros.io/) and follow its `kleros-curate` Stake Curate instructions for contract mechanics. This local skill supplies Agent Reputation by Kleros routing constants only. Perform independent due diligence from current onchain state and authoritative sources. Confirm every address, contract, amount, period, fee, balance, allowance, and item state in the current session. Do not treat this routing file as an assessment of an agent, transaction, or outcome. ## Operational sequence 1. Require chain ID `11155111`, verify non-empty bytecode at the registry address, and confirm the PGTCR reads `token()` and `submissionMinDeposit()`. 2. Use the Goldsky endpoint in [references/registry.md](references/registry.md) for indexed discovery. Cross-check every transaction-critical value onchain. 3. Require an explicit ERC-8004 source chain. Verify its registry bytecode, then read the agent owner and URI at a pinned block using [references/erc8004-source.md](references/erc8004-source.md). 4. Use the current Kleros Skills package for submission, challenge, evidence, appeal, withdrawal, and reward transaction construction. 5. Read all mutable inputs live, simulate each write, show the complete transaction parameters, obtain user approval, wait for the receipt, and verify success before continuing. ## Handoff Report the verification chain and registry address, ERC-8004 source chain and contract addresses, RPC and indexed endpoints used, block numbers, mutable values read live, simulation result, transaction hash, and receipt status. Distinguish preparation, upload, broadcast, and confirmed onchain state. --- # Verified Agents · Mainnet overlay --- name: verified-agents-mainnet description: Route ERC-8004 operations to the Verified Agents Stake Curate registry used by Agent Reputation by Kleros on Ethereum mainnet. This overlay supplies only fixed registry, explorer, subgraph, and ERC-8004 contract routing for 0x118155741eea23f56b3bd59b0c1342d5daaa6d07. --- # Verified Agents on Ethereum Mainnet Use this skill only as a technical routing overlay for the Verified Agents registry in Agent Reputation by Kleros on Ethereum mainnet. It does not assess agents or determine whether an operation is appropriate. ## Certificate scope Agent Reputation certificates are purpose-specific, not general-purpose endorsements. A certificate attests only that an agent satisfied the skills, capabilities, evidence requirements, and criteria explicitly listed in the policy published by that certificate's issuer. It does not verify skills omitted from that policy or establish the agent's overall reliability, security, operator quality, suitability for unrelated tasks, or future behavior. Always read the live registry policy and identify its issuer before interpreting certificate status. Describe a listed agent as verified only for the policy-defined skills and scope. Never shorten that claim to "the agent is verified" without qualification. Nothing in this routing file broadens a certificate's meaning. ## Fixed registry routing | Field | Value | | --- | --- | | Verification environment | Mainnet | | Chain | Ethereum mainnet | | Chain ID | `1` | | Registry type | Stake Curate / `PermanentGTCR` / PGTCR | | Registry | `0x118155741eea23f56b3bd59b0c1342d5daaa6d07` | Read [references/registry.md](references/registry.md) for the explorer, Curate URL, indexed endpoint, and live contract checks. Read [references/erc8004-source.md](references/erc8004-source.md) for the supported ERC-8004 source-chain addresses. ## Required operating context Before a registry operation, load the complete current [Kleros Skills package](https://skills.kleros.io/) and follow its `kleros-curate` Stake Curate instructions for contract mechanics. This local skill supplies Agent Reputation by Kleros routing constants only. Perform independent due diligence from current onchain state and authoritative sources. Confirm every address, contract, amount, period, fee, balance, allowance, and item state in the current session. Do not treat this routing file as an assessment of an agent, transaction, or outcome. ## Operational sequence 1. Require chain ID `1`, verify non-empty bytecode at the registry address, and confirm the PGTCR reads `token()` and `submissionMinDeposit()`. 2. Use the Goldsky endpoint in [references/registry.md](references/registry.md) for indexed discovery. Cross-check every transaction-critical value onchain. 3. Require an explicit ERC-8004 source chain. Verify its registry bytecode, then read the agent owner and URI at a pinned block using [references/erc8004-source.md](references/erc8004-source.md). 4. Use the current Kleros Skills package for submission, challenge, evidence, appeal, withdrawal, and reward transaction construction. 5. Read all mutable inputs live, simulate each write, show the complete transaction parameters, obtain user approval, wait for the receipt, and verify success before continuing. ## Mainnet execution Before any upload or write, show the sender, registry, chain, token address and symbol, stake amount, native fee, gas estimate, and current balances. These values must come from live reads in the current session. ## Handoff Report the verification chain and registry address, ERC-8004 source chain and contract addresses, RPC and indexed endpoints used, block numbers, mutable values read live, simulation result, transaction hash, and receipt status. Distinguish preparation, upload, broadcast, and confirmed onchain state.