Skip to main content
Your own agents integrate with Enfors by calling the gateway (llm.enfors.ai, built on LiteLLM) instead of the model provider directly. The gateway captures each call, tags it with the agent that made it, and turns it into a decision — your code only ever waits on the model. This is the path for the OpenAI SDK and other provider SDKs. If you run Claude Code or Claude Desktop, use the watcher instead.

​
What you need

Gateway base URL

https://llm.enfors.ai — set this as the SDK’s base_url. For raw HTTP nodes, use https://llm.enfors.ai/v1.

LLM Gateway Key

Your gateway credential, under Admin → API Keys. It’s provisioned automatically at signup — distinct from the Personal Access Token used to read the Data API.

​
OpenAI SDK

The gateway is OpenAI-compatible, so you point the OpenAI SDK at it. Attribution metadata travels as query parameters (default_query), and you bring your own provider key via a header.

​
Fields that matter

​
string
required
The gateway origin, https://llm.enfors.ai. The OpenAI SDK appends /v1/... itself; for tools where you paste a full base, use https://llm.enfors.ai/v1.
​
string
required
Your LLM Gateway Key (Admin → API Keys). This authenticates you to the gateway — not the model provider.
​
string
required
provider/model-name format — e.g. openai/gpt-4o, openai/gpt-4o-mini. The gateway is model-agnostic (Anthropic, OpenAI, Gemini, Bedrock, Azure…).
​
string
required
Stable identifier for the agent making the call — this is what groups its sessions and decisions in Enfors.
​
string
Human-readable name shown in the workspace.
​
string
Identifier for this run — use a fresh value (e.g. a UUID) per execution to group the calls of a single run together.
​
header
Bring your own provider key. The gateway forwards the call to the provider using this key; it’s separate from your Gateway Key.
The agent_id, agent_name, and execution_id parameter names match API Keys → Query parameters in the Enfors app. You can also pass them on the URL directly, e.g. https://llm.enfors.ai/v1/chat/completions?agent_id=my-agent&agent_name=My+Agent&execution_id=run-abc-123 — useful for no-code / workflow nodes.

​
How it flows

Each call is captured by the gateway and enqueued via its own callback while your client waits only on the model. Enfors then reconstructs it into a decision with reasoning and evidence. See How Enfors works for the full pipeline.