Skip to main content

Agent Transfer Protocol (ATP): secure agent-to-agent communication

Project description

ATP: Agent Transfer Protocol

Secure agent-to-agent communication over the Internet.

Python 3.11+ License: MIT IETF Draft

A communication protocol for agent-to-agent transfer.
DNS-based discovery, mandatory Ed25519 signing, server-mediated delivery.

  Agent A           ATP Server A          ATP Server B          Agent B
    |                    |                     |                    |
    |---[1. Submit]----->|                     |                    |
    |                    |                     |                    |
    |              2. Credential Verify        |                    |
    |                    |                     |                    |
    |              3. DNS SVCB Discover        |                    |
    |                    |                     |                    |
    |                    |--[4. Transfer]----->|                    |
    |                    |   TLS 1.3 + POST    |                    |
    |                    |                     |                    |
    |                    |               5. ATS+ATK Query (DNS)    |
    |                    |               6. Sender Authenticated   |
    |                    |                     |                    |
    |<---[202 Accepted]--|                     |---[7. Deliver]--->|
    |                    |                     |                    |

Quick Start · Python SDK · CLI Reference · Documentation


Why ATP?

Agents need a standard way to communicate across the Internet: securely, without a central registry, using infrastructure that already exists.

Feature How
Identity local@domain format, powered by DNS
Discovery DNS SVCB records, no central registry needed
Signing Ed25519 on every message, verified at every hop
Authorization ATS policies in DNS, control who can send for your domain
Delivery Store-and-forward with retry, messages don't get lost

Install

pip install agent-transfer-protocol

Requires Python 3.11+

Quick Start

# 1. Start a server
atp server start --domain example.com --port 7443 --local

# 2. Register an agent (will prompt for password)
atp agent register mybot@example.com
# Or non-interactively: atp agent register mybot@example.com -p <password>

# 3. Send a message (from another terminal)
atp send agent@remote.org \
  --from mybot@example.com \
  --password <your-password> \
  --server localhost:7443 --local \
  --body "Hello!"

# 4. Check server status
atp status --server localhost:7443 --local

Try It: Two Servers Talking

Run two servers locally and send messages between them, no DNS needed:

# Terminal 1: Start Server A
atp server start --domain alice.local --port 7443 --local --peers peers.toml

# Terminal 2: Start Server B
atp server start --domain bob.local --port 7444 --local --peers peers.toml

# Register agents (will prompt for password, or use -p)
atp agent register agent@alice.local -p alice_pass
atp agent register agent@bob.local -p bob_pass

# Terminal 3: Alice sends to Bob
atp send agent@bob.local \
  --from agent@alice.local \
  --password <password> \
  --server localhost:7443 \
  --local \
  --body "Hello Bob!"

# Terminal 4: Bob receives (with credential)
atp recv --agent-id agent@bob.local -P bob_pass --server localhost:7444 --local
peers.toml
["alice.local"]
host = "127.0.0.1"
port = 7443

["bob.local"]
host = "127.0.0.1"
port = 7444

Python SDK

import asyncio
from atp.client import ATPClient

async def main():
    client = ATPClient(
        agent_id="mybot@example.com",
        password="your-password",
        server_url="localhost:7443",
        local_mode=True,
    )

    # Send
    result = await client.send("target@remote.org", body="Hello from SDK")
    print(result)  # {"status": "accepted", "nonce": "msg-..."}

    # Receive
    messages = await client.recv()
    for msg in messages:
        print(f"{msg.from_id}: {msg.payload}")

    await client.close()

asyncio.run(main())

CLI Reference

Core Commands

Command Description
atp server start Start ATP server
atp send <to> Send a message
atp recv Receive messages

Agent Management

Command Description
atp agent register <id> Register an agent with credentials
atp agent list List registered agents
atp agent remove <id> Remove an agent

Key Management (Server)

Ed25519 signing keys are auto-generated on first server startup. These commands are for manual control.

Command Description
atp keys generate Generate Ed25519 key pair
atp keys show Show key info
atp keys list List all keys
atp keys rotate Rotate to a new key

Operations

Command Description
atp status Show server status and metrics
atp inspect <nonce> Inspect a specific message

DNS

Command Description
atp dns generate Generate DNS records for your domain
atp dns check Verify DNS records are configured

Run atp <command> --help for options.

Production Deployment

For production, configure DNS records. ATP generates them for you:

# Step 1: Generate the records
atp dns generate --domain example.com --ip 203.0.113.1

# Step 2: Add them to your DNS provider (Cloudflare, Route53, etc.)

# Step 3: Verify
atp dns check --domain example.com

# Step 4: Start with TLS
atp server start --domain example.com --cert server.crt --key server.key

See the DNS Setup Guide for details.

Security

ATP provides three layers of security, inspired by email's battle-tested approach:

Layer ATP Email Equivalent Purpose
Transport TLS 1.3 STARTTLS Encrypted connections
Authentication Credential SMTP AUTH Agent identity (username + password)
Authorization ATS SPF Who can send for a domain
Integrity ATK (Ed25519) DKIM Message signing & verification

Agents authenticate to their server with credentials. Messages are cryptographically signed. Remote servers verify independently via ATS+ATK.

Documentation

Quick Start Full walkthrough with two servers
Configuration CLI options, config file, retry policy
DNS Setup Production DNS configuration
Security Model ATS, ATK, TLS explained in depth
Python SDK API reference for developers
Architecture Module design for contributors

Protocol Specification

ATP is defined as an IETF Internet-Draft (Standards Track):

Agent Transfer Protocol (ATP) draft-li-atp · March 2026 Xiang Li, Lu Sun, Yuqi Qiu, Nankai University, AOSP Laboratory

IETF Datatracker · Full Text

Contributing

git clone https://github.com/NKU-AOSP-Lab/AgentTransferProtocol.git
cd atp
pip install -e ".[dev]"
python -m pytest tests/ -v    # 212 tests

See Architecture for module design and development guide.

License

MIT

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

agent_transfer_protocol-1.0.0a3.tar.gz (59.2 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

agent_transfer_protocol-1.0.0a3-py3-none-any.whl (45.7 kB view details)

Uploaded Python 3

File details

Details for the file agent_transfer_protocol-1.0.0a3.tar.gz.

File metadata

File hashes

Hashes for agent_transfer_protocol-1.0.0a3.tar.gz
Algorithm Hash digest
SHA256 dcce86338336713ef4a69a83fd0db416c652227c7820a2700b4acaf426e81976
MD5 2f3b331ec55af3d277ebe913c7461cb3
BLAKE2b-256 e872509e8460c0c1ffb1759d848f16023c1ed6c13ff5c2d0aa8b0348ce72da23

See more details on using hashes here.

File details

Details for the file agent_transfer_protocol-1.0.0a3-py3-none-any.whl.

File metadata

File hashes

Hashes for agent_transfer_protocol-1.0.0a3-py3-none-any.whl
Algorithm Hash digest
SHA256 6eb1177e6bc6e0a9aacc7458bce73812d8803a9c9c5af405a7e357eb403dc331
MD5 caa0d9bee87a90c24529379d08863293
BLAKE2b-256 05da46c02f9b80935dc0a171bb23f75f49e4b0b8f36a1a26e3866d5940658275

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page