Developer overview
A familiar API with a stricter runtime behind it.
Connect with an OpenAI-compatible client, then layer in customer scope, governed knowledge, agents, metering, and audit as the product requires.
First request
Change the base URL. Keep the client.
The credential represents the user and organization calling through your application. Model access and balance are checked before provider spend.
Technical paths
Go deeper by control boundary.
Public API reference is provided with technical access. These guides explain the product and operating model behind the endpoints.
Gateway
Point an OpenAI-compatible client at Deeplinq and send the caller’s tenant credential.
02Governance
Understand roles, model grants, dataset grants, guardrails, and approval boundaries.
03Knowledge
Ingest governed data and return cited answers from only the datasets the caller may use.
04Agents
Configure an assistant, start a durable run, and handle approval-required tool calls.
05Audit trail
Verify chain integrity and export bounded audit evidence for independent review.
Next step
Bring your current client and deployment constraints.
We will map the shortest integration path and identify the controls that need configuration before the first production request.