API & Automation
Agent API Gateway
Connect OpenAI-compatible agent tools to Orchestris Server while keeping model access, quota, and usage controls in one place.
Key Steps
- There is no separate Agent Gateway screen; the gateway is the server API plus the admin screens that configure and audit it.
- Configure agent clients with the `/openai/v1` base URL and an Orchestris API key.
- Use organization-owned keys for shared agents and user-owned keys when traffic should follow an individual owner.
- Review owner kind, API key, user, model, provider, token, latency, cost, and request-ID data in usage and metrics views.
Article Scope
This guide focuses on the operational steps needed to run Orchestris with team access, provider control, and predictable usage.
Visual Reference
Endpoint shape
The OpenAI-compatible surface is intended for supported chat and responses workflows. It keeps the public request shape familiar while Orchestris performs authentication, model resolution, quota admission, provider routing, and usage recording internally.
- Use `/openai/v1/chat/completions` for supported Chat Completions-compatible traffic.
- Use `/openai/v1/responses` for supported Responses-compatible traffic.
- Use `/openai/v1/models` to list models and aliases available to the API key.
Agent policy
- Issue organization-owned API keys for service agents, shared workers, and production automation.
- Issue user-owned API keys when agent usage should roll up to an individual user and their visible models.
- Scope keys to approved model aliases or direct model IDs.
- Set token or cost limits so runaway loops are contained by server policy.
Usage review
- Capture client request IDs in agent logs so operators can correlate requests with usage records.
- Review top models and providers before changing agent defaults.
- Use provider telemetry and usage reports to catch retries, high latency, or unexpected cost changes.
Related Topics
API & Automation
REST API
Use REST endpoints for authentication, licensing, deployments, billing, and operational automation.
API & Automation
Client Streaming Notes
Understand the native streaming path used by connected clients and private deployments.
API & Automation
Webhook Notes
Plan webhook-style automation around documented portal and billing events.