API Reference

Seal is an OpenAI-compatible gateway for a defined pilot workflow. It evaluates policy before a provider call and returns a signed ATTESTATION-v1 decision record with the routed outcome.

Base URL

text
https://api.aqta.ai/v1

Authentication

Send an organisation API key in the Authorization header. Aqta keys begin with aqta_.

http
Authorization: Bearer aqta_your_key

Create and revoke keys in Settings → API Keys after pilot access has been issued. Keep keys in environment variables, never in browser code or source control.

Public endpoints

Method	Endpoint	Purpose
`POST`	`/v1/chat/completions`	Send an OpenAI-compatible routed call
`GET`	`/v1/attestation/public-key`	Retrieve the current published signing key
`GET`	`/v1/attestation/keys`	Retrieve published active and historical key material

Send a routed call

bash
curl https://api.aqta.ai/v1/chat/completions \
  -H "Authorization: Bearer aqta_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-4o",
    "messages": [{"role": "user", "content": "Hello"}]
  }'

The request shape follows the OpenAI chat-completions format. Use a model available through the provider credentials configured for your organisation.

Decision record

Responses include an aqta object. Its attestation field is the signed receipt. Capture the raw JSON response if your SDK discards unknown top-level fields.

The record identifies the decision and its outcome. Verify the signature with a trusted copy of the published public key, not with a dashboard screen or a claim from Aqta.

Verification key

bash
curl https://api.aqta.ai/v1/attestation/public-key

The response includes the current key, key identifier, algorithm, and encoding. Pin a trusted key before relying on it in a verification workflow. The key registry endpoint is for key-history handling; it does not replace your own trust policy.

Errors and retries

Treat error responses as ordinary API failures. Handle 429 and upstream errors with bounded exponential backoff. Do not retry a call blindly when its business action is not idempotent.

Scope

Aqta records a gateway decision. It does not certify your system, make a legal determination, or replace your organisation's review and control duties.