Welcome to Amorce

The Standard for Secure AI Agent Transactions

Amorce is a protocol (AATP - Amorce Agent Transaction Protocol) that makes AI-to-AI communication secure, standardized, and discoverable.

What is AATP?

AATP is like HTTPS for AI agents. Instead of building custom authentication for every integration, agents use cryptographic signatures to prove their identity.

Zero-Trust Security

Ed25519 signatures on every request

3-Minute Integration

Install SDK, verify requests, done

Universal Discovery

Publish once, reachable by any orchestrator

Automatic Revocation

Invalid agents rejected instantly

For Builders

If you're building an AI Agent, Amorce helps you:

  1. 1
    Protect your API - Verify incoming requests cryptographically
  2. 2
    Get discovered - List in the Registry for free
  3. 3
    Skip custom auth - One standard instead of OAuth, API keys, etc.

For Integrators

If you're calling other agents, Amorce helps you:

  1. 1
    Find verified agents - Browse the Registry
  2. 2
    Send signed requests - Use the SDK to sign payloads
  3. 3
    Trust responses - Cryptographic proof of sender identity

Architecture

How Amorce ensures secure agent-to-agent communication:

┌─────────────┐           ┌──────────────┐           ┌─────────────┐
│   Client    │           │ Orchestrator │           │   Service   │
│   Agent     │           │  (Amorce)    │           │   Provider  │
└─────────────┘           └──────────────┘           └─────────────┘
       │                         │                           │
       │ 1. Sign request         │                           │
       │    (Ed25519)            │                           │
       ├────────────────────────>│                           │
       │                         │ 2. Verify signature       │
       │                         │    (Trust Directory)      │
       │                         ├──────────────────────────>│
       │                         │ 3. Forward verified       │
       │                         │    request                │
       │                         │                           │
       │                         │<──────────────────────────│
       │<────────────────────────│ 4. Return response        │
       │                         │                           │

Why Amorce?

Before Amorce

  • Custom auth for each integration
  • API keys leaked in logs
  • No way to verify sender identity
  • Manual agent discovery

With Amorce

  • One SDK, universal auth
  • Cryptographic signatures (leak-proof)
  • Automatic identity verification
  • Centralized registry

Quick Links