Overview

Optiak is an AI gateway platform for configuring, routing, protecting, enriching, and observing AI application traffic.

Teams use Optiak in two ways:

• The platform UI to set up provider keys, applications, model access, data sources, guardrails, tools, and observability.
• The Gateway API to send application traffic through Optiak using an application API key.

Why Optiak?

Building AI applications usually means juggling provider accounts, credentials, routing rules, safety controls, enrichment data, billing, and request logs. Optiak brings those workflows into one product:

• Provider management - Connect your own provider keys for OpenAI, Anthropic, AWS Bedrock, Google Gemini API, Vertex AI, and other supported providers.
• Application control - Create separate applications with their own credentials, enabled models, guardrails, tools, data integrations, cost settings, and inference defaults.
• Smart routing - Let Optiak choose among eligible models when a request uses the smart model.
• Prompt enrichment - Add web search or organization data sources when an application needs more context.
• Guardrails - Apply safety policies for prompt injection attempts, personal information, sensitive data, and unsafe content handling.
• Observability - Understand platform activity, application health, request history, cost behavior, and module impact.
• Team access - Let admins manage organization-wide setup while members can view applications and platform configuration.

Core Concepts

• Organization - The workspace that contains your team, provider keys, shared model catalog, data sources, and governance policies.
• Company Setup - Organization-level controls. Admins use it to connect provider keys, enable models, set governance policies, create data sources, and allow tools.
• Application - A project or product surface that sends AI traffic through Optiak. Each application has its own credentials and module configuration.
• Provider key - A credential for an upstream model provider. These are added in Company Setup -> Models and stored encrypted.
• Application API key - A credential your service uses to call the Optiak API for one application. These are created in an application's Credentials tab.
• Data source - A named collection of uploaded documents that vector search can use for retrieval augmented generation.
• Request - A call to the public Gateway API. Requests can target a specific model or use smart when Smart Router is enabled for the application.

The public API base URL is:

https://api.optiak.dev/v1

Next steps

1. Read Platform Navigation to understand where each workflow lives.
2. Follow Quickstart to create an application, connect providers, validate available models, and send a first request.
3. Review Company Setup for organization-wide controls, Applications for app-level settings and credentials, Models and Routing for model access, Guardrails for safety policies, and Data Integrations for retrieval sources and request-level opt-ins.