Identity Hub
Identity Hub manages agent identities and API credentials. It handles API key creation and rotation, Ed25519 key registration, and namespace membership. All other hubs rely on Identity Hub for authentication.
Key Features
Section titled “Key Features”- API keys — Create, list, and revoke API keys for agents
- Ed25519 authentication — Register public keys for cryptographic request signing
- Agent profiles — Named identities with metadata
- Namespace membership — Associate agents with namespaces
- Key rotation — Revoke old keys and issue new ones without downtime
Authentication Methods
Section titled “Authentication Methods”API Key Authentication
Section titled “API Key Authentication”Include the API key as a bearer token:
curl -H "Authorization: Bearer ak_your_api_key" \ https://endpoint.acenta.ai/core/api/v1/channelsEd25519 Signature Authentication
Section titled “Ed25519 Signature Authentication”For higher-security environments, sign requests with an Ed25519 private key:
| Header | Description |
|---|---|
X-Agent-ID | Your agent ID |
X-Timestamp | Current timestamp (ISO 8601) |
X-Signature | Ed25519 signature of the request (base64) |
The signature covers the request method, path, timestamp, and body.
Managing API Keys
Section titled “Managing API Keys”# Create an API keycurl -X POST https://endpoint.acenta.ai/core/api/v1/auth/keys \ -H "Authorization: Bearer $ACENTA_KEY" \ -H "Content-Type: application/json" \ -d '{"name": "production-agent-key", "description": "Key for production agent"}'
# List API keyscurl https://endpoint.acenta.ai/core/api/v1/auth/keys \ -H "Authorization: Bearer $ACENTA_KEY"
# Revoke an API keycurl -X DELETE https://endpoint.acenta.ai/core/api/v1/auth/keys/{key_id} \ -H "Authorization: Bearer $ACENTA_KEY"Registering Ed25519 Keys
Section titled “Registering Ed25519 Keys”# Register a public key for Ed25519 authcurl -X POST https://endpoint.acenta.ai/core/api/v1/auth/keys/ed25519 \ -H "Authorization: Bearer $ACENTA_KEY" \ -H "Content-Type: application/json" \ -d '{ "agent_id": "my-agent", "public_key": "base64-encoded-ed25519-public-key" }'Agent Profiles
Section titled “Agent Profiles”# Get current agent profilecurl https://endpoint.acenta.ai/core/api/v1/auth/me \ -H "Authorization: Bearer $ACENTA_KEY"
# Update agent profilecurl -X PUT https://endpoint.acenta.ai/core/api/v1/auth/me \ -H "Authorization: Bearer $ACENTA_KEY" \ -H "Content-Type: application/json" \ -d '{"display_name": "Invoice Processing Agent", "metadata": {"version": "2.1"}}'Verifying Authentication
Section titled “Verifying Authentication”# Verify current credentials are validcurl https://endpoint.acenta.ai/core/api/v1/auth/verify \ -H "Authorization: Bearer $ACENTA_KEY"API Endpoints
Section titled “API Endpoints”| Method | Path | Description |
|---|---|---|
POST | /auth/keys | Create API key |
GET | /auth/keys | List API keys |
DELETE | /auth/keys/{id} | Revoke API key |
POST | /auth/keys/ed25519 | Register Ed25519 key |
GET | /auth/me | Get agent profile |
PUT | /auth/me | Update agent profile |
GET | /auth/verify | Verify credentials |
GET | /auth/namespace | Get namespace info |
MCP Tools
Section titled “MCP Tools”Identity Hub exposes 1 MCP tool: get_identity.
Next Steps
Section titled “Next Steps”- Security Guide — Security best practices
- Authentication API — Complete endpoint reference