Integrate through the API, a TypeScript or Python SDK, or MCP. This is a control plane, not a chat widget.
Documentation, API, SDK, MCP, and technical architecture for production systems.
Engineers who need to create agents, attach knowledge, grant tools, and read traces from their own services. If you are evaluating the product, start with the platform overview. If you are wiring it into CI or a backend, start here.
Authenticate with an API key. Register knowledge sources and an agent. Grant the tools that agent may call. Start an execution. Read the trace, or subscribe to a webhook when the run completes. Swap the model endpoint later without rewriting the agent payload.
Obliq separates application logic from model providers, knowledge stores, and tool buses. Agent definitions reference capabilities—not vendor SDKs—so you can change an endpoint without rewriting the workflow. The control plane is the contract; the homepage film is not.
A REST control plane for workspaces, knowledge sources, agents, executions, and traces. Authenticate with API keys. Mutating calls are auditable because they create or read the same execution record the product inspects.
TypeScript and Python clients wrap the control plane for local development and CI. When an SDK lags a new field, call the API directly. The HTTP contract is the source of truth.
Subscribe to execution completed, evaluation flagged, and knowledge health events. Use them to start your own pipelines instead of polling for a finished run.
POST /v1/executions
Authorization: Bearer <api_key>
Content-Type: application/json
{
"agent_id": "agt_research_dispatch",
"input": {
"message": "Summarize SLA for ACME and open a ticket"
}
}For protocol-level tool access, see MCP for Obliq.
Use the REST control plane, the TypeScript or Python SDK, or MCP. You create agents, connect knowledge, grant tools, and read executions. There is no chatbot widget to embed as the integration.
Yes. The API covers workspaces, knowledge sources, agents, executions, and traces. Authenticate with an API key. SDKs wrap the same contract.
Yes. Native Model Context Protocol support lets agents discover and invoke tools. See the MCP page for the call shape and the policy boundaries.