API REFERENCE

Interface with Authority

Programmatic execution control and cryptographic verification via REST. JSON payloads, Ed25519 signatures, deterministic decisions.

Authentication

Public discovery and verification helpers are unauthenticated. The execution gateway requires an API key.

HTTP - execution gateway

Authorization: Bearer tg_live_...

Environments

Surface	Base URL	Auth
Public authority	`https://trigguardai.com`	None
Execution gateway	`https://api.trigguardai.com/v1`	Bearer key

Endpoints

POST/execute

Execution authorization

Submit an execution request. Response is PERMIT, DENY, ESCALATE, or SILENCE, with a receipt when authorized.

JSON request

{
  "surface_id": "sur_827f",
  "action": "TRANSFER",
  "payload": { "amount": 5000, "currency": "USD" },
  "context": { "user_id": "usr_9912" }
}

POST/protocol/verify-receipt

Receipt verification

Stateless shape check for decision and timestamp. No credentials. For Ed25519 signature verification use POST /protocol/verify-signature or the offline CLI.

Need to validate a receipt? → Verification guide

GET/.well-known/trigguard-keys.json

Published keys

Public verification keys for offline receipt checks. No authentication.

Error codes

401Unauthorized
403Policy violation
429Rate limited

Standard limit: 5,000 req/min (enterprise burst up to 10k).