---
summary: Register SigID agents, choose anchors and scopes, attach keys, and prepare webhook subscriptions for agent lifecycle events.
tags:
  - agents
  - registration
  - anchors
  - scopes
  - webhooks
categories:
  - AI Agents
---

# Agent Registration

<!-- agent:page
You are a coding agent registering a SigID agent and preparing its identity material by following this reference.
First collect: tenant or workspace ID, human owner context, agent display name, expected API audience, allowed scopes, capabilities, anchor type, public signing key and algorithm, and webhook subscriptions for lifecycle events.
Create or locate the tenant-scoped agent, then attach at least one verified anchor or registered key; public self-registration must complete its proof-of-work and uniqueness checks before any session or token is trusted.
Keep owner and tenant checks in the service boundary, require key-ownership proof before persisting public keys, reject duplicate fingerprints, and never expose private key material or OAuth client secrets in docs, logs, or responses.
Definition of done: the agent is active, one anchor or key is verified, scopes are least-privilege for the job, and audit or webhook coverage exists for creation, verification, rotation, suspension, and revocation.
-->

## Developer Setup

Prepare:

- tenant ID or slug
- agent display name
- expected API audience
- allowed scopes
- anchor type
- public signing key or client secret
- webhook subscription for agent events

Example scope design:

```
agent:read
agent:write
tools:search
tools:execute
vault:exchange
wallet:sign
```

## Register An Agent

Create and manage agents from the Identity portal, the CLI, or the
tenant-scoped agent API routes:

```bash
curl -sS "$SIGID_AUTH_ORIGIN/api/v1/agents" \
  -X POST \
  -H "authorization: Bearer $ACCESS_TOKEN" \
  -H "content-type: application/json" \
  -H "idempotency-key: agent-create-demo" \
  -d '{
    "name": "research-agent",
    "description": "Search and summarization agent",
    "capabilities": ["web", "mcp"]
  }'
```

Then attach and verify an anchor or register an agent key.

Definition of done:

- agent status is active
- at least one anchor or key is verified
- scopes are limited to the agent's job
- audit logs show creation and verification

## API Surface

| Endpoint | Use |
|---|---|
| `GET /api/v1/agents` | List agents |
| `POST /api/v1/agents` | Create an agent |
| `GET /api/v1/agents/{id}` | Read one agent |
| `PATCH /api/v1/agents/{id}` | Update an agent |
| `DELETE /api/v1/agents/{id}` | Delete an agent |
| `PATCH /api/v1/agents/{id}/suspend` | Suspend agent access |
| `POST /api/v1/agents/{agent_id}/keys` | Register a key |
| `POST /api/v1/agents/{agent_id}/keys/{key_id}/revoke` | Revoke a key |

## See Also

- [Agent Authentication](agent-auth.md) - How agents authenticate
- [Agent Identity](agent-auth.md#agent-identity) - Available anchor types