API Reference

APIZ exposes one Control Plane contract to the Web UI and CLI. The public reference will be generated from a versioned, machine-readable HTTP contract. Until that contract is available, the current HTTP specification remains the normative source.

Contract Areas

• API Instances: connect upstream services and test their managed credentials.
• Clients and bindings: describe agent-facing callers and the routes each one may reach.
• Temporary Credentials: issue and revoke time-bounded Client access.
• Policies: define Structured or Scripted request decisions and bind them to routes.
• Access Logs: query redacted request outcomes, denial reasons, and timelines.
• Teams and billing: manage Team membership, entitlements, usage, and bounded spend.

Current Contract Source

The current HTTP API specification is authoritative while the machine-readable public reference is being established. Examples must use synthetic identifiers and never include real credentials.

Need a working flow? Open the Quickstart.