EQTY LabDocs

LLM Gateway API

The LLM Gateway is the Agent Gateway's data path: it registers agent signing keys, stores attestation blobs, records agent state history, and verifies, governs, audits, and forwards agents' LLM provider and relay traffic.

Version
1.2.1
Base URL
https://<host>

Authentication

  • AgentSignature · API key in header "Signature" — An RFC 9421 HTTP message signature by a registered agent's Ed25519 or P-256 key, sent with its Signature-Input header. The keyid is the agent's registered DID, created must fall within the signature's maximum age and clock skew, and the covered components start with @method and @target-uri. A request with a body also covers content-digest. Proxy and relay requests cover x-viper-nonce, x-viper-timestamp, and either x-viper-state-cid (state in an uploaded blob) or x-viper-credential-cid (state in the agent's state attestation credential); credential renewal covers x-viper-nonce. Viper signs every request this way.
  • ApiKeyAuth · API key in header "Authorization" — Type "Bearer" followed by a space and a Guardian Platform API key (ak_…). Accepted only for agent registration, when the gateway is configured to enroll agents through Auth Service. Registration with a registration token sends no Authorization header.

Health

Registration

Provider Proxy

Blobs

Relay