AIDRESS
Get startedConceptsSDKs & toolsAPI referenceReferencellms.txt
DocsReference

Standards & Protocols

Aidress is built on open standards. This page lists every protocol the API implements or is compatible with, with links to the authoritative specs.

Ed25519 — HTTP Message Signatures (RFC 9421)

All cryptographic request signing in Aidress uses Ed25519 over the IETF RFC 9421 — HTTP Message Signatures standard. Three headers are signed per request: Content-Digest, Signature-Input, and Signature.

PropertyValue
AlgorithmEd25519 (EdDSA on Curve25519)
StandardRFC 9421 — HTTP Message Signatures
Key formatJWKS OKP (kty: OKP, crv: Ed25519)
Replay protection300-second window + nonce
Body integrityContent-Digest: sha-256

See Authentication for setup instructions and the full header format.

Web Bot Auth — keyless discovery

Aidress supports the Web Bot Auth pattern for keyless agent discovery. If your agent serves its Ed25519 public key at a .well-known URL, Aidress discovers and caches it on first contact — no manual key registration required.

text
https://your-domain.com/.well-known/http-message-signatures-directory
PropertyValue
Discovery URL.well-known/http-message-signatures-directory
Response formatJWKS (application/json)
Key typeOKP / Ed25519
Cache behaviourAidress caches on first contact, auto-refreshes on key rotation

Google A2A — Agent-to-Agent Protocol

Aidress is compatible with the Google A2A specification. Agents registered with a2a_compliant: true receive full JSON-RPC 2.0 envelopes via /call. Aidress also publishes its own A2A agent card at https://api.aidress.ai/.well-known/agent.json.

FeatureSupport
JSON-RPC 2.0 envelopeFull pass-through for a2a_compliant agents
Agent card (.well-known/agent.json)Published at api.aidress.ai
Import from A2A cardPOST /import-agent
Plain HTTP bridgingAidress extracts content part for non-A2A endpoints

See A2A Compatibility for the full integration guide.

x402 — HTTP Payment Protocol

Aidress integrates with the x402 payment protocol for programmable settlement. When a transaction requires payment, Aidress routing information includes x402-compatible payment rail details so agents can settle autonomously without human intervention.

PropertyValue
ProtocolHTTP 402 Payment Required
Use caseAutonomous agent-to-agent micropayments
Integration pointRouting object returned by /verify and /call

JSON-RPC 2.0

The A2A message envelope used by /call follows the JSON-RPC 2.0 specification. The method is message/send and the params structure follows the A2A message format.

JWKS / OKP keys

Ed25519 public keys are exchanged in JWKS format (RFC 7517) using the OKP key type defined in RFC 8037.

json
{
  "kty": "OKP",
  "crv": "Ed25519",
  "kid": "your_agent_id",
  "x": "<base64url-encoded 32-byte public key>"
}