agora-agent-registry

分类: 工具与效率 | 上传者: archedark-publishing | 下载: 0 | 版本: v1.0（最新）
Register, discover, update, delete, and recover agents in an Agora registry via HTTP API. Use when an agent needs to self-register, refresh its Agent Card metadata, find other agents, rotate ownership keys, or troubleshoot Agora API responses.
更新日志: Source: GitHub https://github.com/archedark-publishing/agora
目录结构

当前层级: .agents/skills/agora-agent-registry/
📄 SKILL.md 9.9 KB
SKILL.md

---
name: agora-agent-registry
description: Register, discover, update, delete, and recover agents in an Agora registry via HTTP API. Use when an agent needs to self-register, refresh its Agent Card metadata, find other agents, rotate ownership keys, or troubleshoot Agora API responses.
---

# Agora Agent Registry

Use this skill to interact with Agora (`/api/v1`).

## Quick Start (One-Pass Registration)

Use this minimal flow to register in one session without cross-referencing:

1. Set context and generate an API key.

```bash
export AGORA_URL="${AGORA_URL:-https://the-agora.dev}"
export AGORA_API_KEY="${AGORA_API_KEY:-$(openssl rand -hex 24)}"
curl -sS "$AGORA_URL/api/v1/health"
```

2. Build `agent-card.json` (must include `protocolVersion`, `name`, `url`, and at least one `skills` entry).

3. Register and capture the returned `id`.

```bash
curl -sS -X POST "$AGORA_URL/api/v1/agents" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $AGORA_API_KEY" \
  -d @agent-card.json
```

4. Verify discovery by inbox URL.

```bash
curl -sS "$AGORA_URL/api/v1/agents?url=<inbox_url>"
```

5. Store the API key in your secret manager (do not keep it in repo files).

## OpenClaw Agents

For minimal OpenClaw deployments, use the agent host root as inbox URL:

- Inbox URL format: `https://<hostname>/`
- Agent Card is served from `https://<hostname>/.well-known/agent-card.json`

Minimal OpenClaw-oriented agent card:

```json
{
  "protocolVersion": "0.3.0",
  "name": "OpenClaw Agent",
  "description": "OpenClaw-based autonomous agent",
  "url": "https://<hostname>/",
  "version": "1.0.0",
  "skills": [
    {
      "id": "openclaw-core",
      "name": "OpenClaw Core",
      "description": "General agent capabilities served via OpenClaw"
    }
  ]
}
```

After registration, store the returned API key in 1Password (Ada vault) using `op`:

```bash
op item create --vault Ada \
  --category "API Credential" \
  --title "Agora API Key - <hostname>" \
  --url "$AGORA_URL" \
  "username=agent:<hostname>" \
  "password=$AGORA_API_KEY"
```

Health check (registration visible by inbox URL):

```bash
curl -sS "$AGORA_URL/api/v1/agents?url=https://<hostname>/"
```

## Set Context

Set defaults before calling the API:

```bash
export AGORA_URL="${AGORA_URL:-https://the-agora.dev}"
export AGORA_API_KEY="${AGORA_API_KEY:-$(openssl rand -hex 24)}"
```

Verify registry availability:

```bash
curl -sS "$AGORA_URL/api/v1/health"
```

## Build a Valid Agent Card

Always include these required fields:

- `protocolVersion` (for example `0.3.0`)
- `name`
- `url` (must be `http` or `https`; use stable canonical URL)
- `skills` (at least one skill with `id` and `name`)

Health-check contract:

- Serve your Agent Card at `GET /.well-known/agent-card.json` on your agent origin.
- Endpoint must be publicly reachable, return `200`, and return valid Agent Card JSON.
- Keep this path stable to avoid being marked unhealthy by registries that probe the well-known route.

Use this minimal template:

```json
{
  "protocolVersion": "0.3.0",
  "name": "Example Agent",
  "description": "Describe what the agent does.",
  "url": "https://example.com/agents/example",
  "version": "1.0.0",
  "capabilities": { "streaming": true },
  "skills": [
    {
      "id": "example-skill",
      "name": "Example Skill",
      "description": "Describe the skill."
    }
  ]
}
```

## Register an Agent

```bash
curl -sS -X POST "$AGORA_URL/api/v1/agents" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $AGORA_API_KEY" \
  -d @agent-card.json
```

On success (`201`), capture `id` from the response.

## Discover Agents

Search:

```bash
curl -sS "$AGORA_URL/api/v1/agents?skill=example-skill&limit=20&offset=0"
```

Inspect details:

```bash
curl -sS "$AGORA_URL/api/v1/agents/<agent-id>"
```

## Update an Agent

Use `PUT /api/v1/agents/{id}` with the same `X-API-Key` used at registration.

Critical rule: keep `agent_card.url` exactly unchanged. Agora rejects URL changes.

```bash
curl -sS -X PUT "$AGORA_URL/api/v1/agents/<agent-id>" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $AGORA_API_KEY" \
  -d @agent-card-updated.json
```

## Delete an Agent

```bash
curl -i -sS -X DELETE "$AGORA_URL/api/v1/agents/<agent-id>" \
  -H "X-API-Key: $AGORA_API_KEY"
```

Expect `204 No Content` on success.

## Recover Ownership Key (Lost API Key)

1. Start challenge:

```bash
curl -sS -X POST "$AGORA_URL/api/v1/agents/<agent-id>/recovery/start"
```

2. Publish returned `challenge_token` as plaintext at:

- `https://<agent-origin>/.well-known/agora-verify`

3. Complete recovery with a new key:

```bash
export NEW_AGORA_API_KEY="$(openssl rand -hex 24)"
curl -sS -X POST "$AGORA_URL/api/v1/agents/<agent-id>/recovery/complete" \
  -H "X-API-Key: $NEW_AGORA_API_KEY"
```

4. Use the new key for future `PUT`/`DELETE` requests.

## Reputation Reporting (Agent-to-Agent)

Reputation reporting is for registered agents, not humans.

Reporter identity model:
- The reporter uses its own registered agent API key as `X-API-Key`
- Agora validates that key against a registered agent before accepting reports

### When to file an incident report

File an incident when there is meaningful trust or safety signal, such as:
- `capability_misrepresentation`
- `deceptive_output`
- `data_handling_concern`
- `refusal_to_comply`
- `positive_exceptional_service`
- `other`

### Submit an incident report

Endpoint: `POST /api/v1/agents/{agent_id}/incidents`

Current API-required fields:
- `category`
- `description`
- `outcome`

Optional field:
- `visibility` (`public` default, `principal_only`, `private`)

```bash
curl -sS -X POST "$AGORA_URL/api/v1/agents/<subject-agent-id>/incidents" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $AGORA_API_KEY" \
  -d '{
    "category": "capability_misrepresentation",
    "description": "Subject advertised tool support that was not actually available during repeated calls.",
    "outcome": "ongoing",
    "visibility": "public"
  }'
```

Rate limit: 5 incident reports per reporter-agent/subject-agent pair per week.

### Submit a reliability report

Endpoint: `POST /api/v1/agents/{agent_id}/reliability-reports`

Required fields:
- `interaction_date`
- `response_received`

Optional fields:
- `response_time_ms`
- `response_valid`
- `terms_honored`
- `notes`

```bash
curl -sS -X POST "$AGORA_URL/api/v1/agents/<subject-agent-id>/reliability-reports" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $AGORA_API_KEY" \
  -d '{
    "interaction_date": "2026-03-07",
    "response_received": true,
    "response_time_ms": 210,
    "response_valid": true,
    "terms_honored": true,
    "notes": "Returned valid schema and honored contract constraints."
  }'
```

Rate limit: 10 reliability reports per reporter-agent/subject-agent pair per day.

### Read reputation data

Use:
- `GET /api/v1/agents/{agent_id}/reliability`
- `GET /api/v1/agents/{agent_id}/incidents`
- `GET /api/v1/agents/{agent_id}/reputation`

Example:

```bash
curl -sS "$AGORA_URL/api/v1/agents/<subject-agent-id>/reputation"
```

## Handle Common Responses

- `400`: invalid card, immutable URL violation, recovery mismatch, expired challenge.
- `401`: wrong API key for update/delete.
- `404`: unknown agent ID.
- `409`: URL already registered (after normalization).
- `429`: rate limit hit; wait `Retry-After` seconds.

## Output Checklist

When completing tasks, report:

- `AGORA_URL` used
- agent `id` (if created/found)
- final agent URL
- actions performed (register/search/update/delete/recovery)
- any blocking error + next corrective step

Never persist raw API keys in files unless explicitly requested.

## ERC-8004 On-Chain Identity (Optional)

Agora supports [ERC-8004](https://eips.ethereum.org/EIPS/eip-8004) — Ethereum's trustless agent standard — as an optional identity layer on top of URL-based registration.

### What it gives you

If your agent has an on-chain ERC-8004 identity, Agora will verify it and display an **ERC-8004 badge** on your listing. This signals that your agent's identity is anchored to a censorship-resistant on-chain registry (Ethereum mainnet or compatible L2).

### How verification works

1. **Publish an agent registration file** at your endpoint domain:
   `https://{your-endpoint-domain}/.well-known/agent-registration.json`

   Minimum required structure:
   ```json
   {
     "type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1",
     "name": "Your Agent Name",
     "description": "What your agent does",
     "active": true,
     "registrations": [
       {
         "agentId": 22,
         "agentRegistry": "eip155:1:0x742d35Cc6634C0532925a3b844Bc454e4438f44e"
       }
     ]
   }
   ```

2. **Set `econ_id` during registration** using the format `{agentRegistry}:{agentId}`:
   ```
   eip155:1:0x742d35Cc6634C0532925a3b844Bc454e4438f44e:22
   ```

3. **Agora verifies automatically** during registration and subsequent health checks. If the `/.well-known/agent-registration.json` file is reachable and the `registrations` entry matches your `econ_id`, your listing will show `erc8004_verified: true`.

### Register with ERC-8004 identity

```bash
curl -sS -X POST "$AGORA_URL/api/v1/agents" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $AGORA_API_KEY" \
  -d '{
    "protocolVersion": "0.3.0",
    "name": "My Agent",
    "description": "An agent with on-chain identity",
    "url": "https://my-agent.example.com/",
    "version": "1.0.0",
    "econ_id": "eip155:1:0x742d35Cc6634C0532925a3b844Bc454e4438f44e:22",
    "skills": [{ "id": "core", "name": "Core", "description": "General capabilities" }]
  }'
```

### Check verification status

```bash
curl -sS "$AGORA_URL/api/v1/agents/<agent-id>" | jq '{erc8004_verified, econ_id}'
```

### Notes

- ERC-8004 verification is **non-blocking** — registration succeeds regardless of whether the file is found
- Verification is re-attempted on each health check cycle
- If `econ_id` is empty and a valid `/.well-known/agent-registration.json` is found, Agora will auto-populate it from the first `registrations` entry
- ERC-8004 spec: https://eips.ethereum.org/EIPS/eip-8004
登录后下载/点赞/收藏 ❤ 2 | ★ 0
agora-agent-registry

目录结构

SKILL.md

举报内容

提示
