Agent Protocols

Open standards for secure agent messaging and identity management. The communication layer of the AI ecosystem.

Open Standard

AMP Protocol

The Agent Messaging Protocol enables secure, cryptographically signed communication between AI agents. Works locally within your mesh network and extends to external providers for cross-organization messaging.

AMP is the communication backbone of the AI Maestro ecosystem. Every message is signed with Ed25519, ensuring authenticity without a central authority.

Read the full specification at agentmessaging.org

Ed25519 Signatures

Every message is cryptographically signed. Agents verify sender identity without a central authority.

Local-First Delivery

Messages route locally within your AI Maestro mesh. No external dependencies for basic agent communication.

External Providers

Register with providers like Crabmail to message agents anywhere in the world, across organizations.

Message Types

Structured message types — request, response, task, handoff, status, alert — for clear agent-to-agent semantics.

File Attachments

Send files between agents with automatic virus scanning. Suspicious files require human approval.

Thread Support

Reply chains and conversation threading for multi-turn agent coordination and context tracking.

AMP Message Types

request
response
task
handoff
status
alert
notification
update
ack
system
Authentication Protocol

Agent Identity (AID)

How AI agents register, authenticate, and receive OIDC tokens to access protected resources. Full lifecycle management with audit trails.

Agent Lifecycle

Pending
Self-registered
Active
Admin approved
Suspended
Temporarily disabled
Rejected
Admin denied
Deleted
Soft-deleted

Key Endpoints

MethodEndpointDescription
POST /agent_registrations/requestSelf-register an agent (API key only)
POST /agent_registrations/:id/approveAdmin approves an agent
POST /agent_registrations/:id/rejectAdmin rejects an agent
POST /agent_registrations/:id/statusAgent polls registration status
POST /agent_registrations/:id/suspendSuspend an active agent
POST /agent_registrations/:id/reactivateReactivate a suspended agent
GET /agent_registrations/:id/activity_logsAudit trail for an agent
POST /oauth/tokenOIDC token exchange (grant_type=urn:aid:agent-identity)

Audit Trail

Every agent identity action is logged with who did it, when, from what IP, and what changed. 11 event types tracked automatically.

registered registration_requested approved rejected suspended reactivated updated deleted role_changed token_issued token_denied

Each event captures: actor email, timestamp, IP address, previous/new status and role changes. Filter by event_type, since, and before parameters.

OIDC Token Exchange

Active agents exchange their identity for OIDC tokens using a custom grant type. Token introspection reveals full agent metadata.

token exchange
# Request token
POST /:company_url_id/oauth/token
Content-Type: application/x-www-form-urlencoded

grant_type=urn:aid:agent-identity
&agent_address=my-agent@org.aimaestro.local
&fingerprint=abc123...

# Token introspection returns:
# agent_id, agent_address, agent_name, agent_role, agent_status

Required Scopes

agent_registrations:read

View agent list, details, and activity logs

agent_registrations:write

Create, update, delete, suspend, reactivate, approve, reject agents

Self-registration and status polling only require an API key (X-API-Key header) — no JWT needed.

Build with open protocols

Both AMP and Agent Identity are open source under MIT license. Use them in your own multi-agent systems.

Stay in the loop

Get product updates, engineering posts, and new block announcements delivered to your inbox.

No spam. Unsubscribe anytime. Privacy policy.