Skip to content
WORKSI AI Control

What each path gives you.

They combine: most teams start with the gateway and add the SDK or MCP where they need more.

What each integration path gives you
Capabilitybase_urlSDKMCPOTLP
Every model call traced, with tokens and cost–
Runs, steps and tool calls–
Model policies, budgets, pause and stop enforced––
Tool allowlists–
A person’s approval before a risky tool––
Business outcomes for ROI––
No Worksi package to install–

Your endpoints and your key.

One screen of the console holds everything an app needs: the endpoints for each path and the key that ties calls to an environment.

  1. 1. OpenAI‑compatible base URL to use instead of api.openai.com.

  2. 2. MCP server endpoint for Claude Desktop, Cursor, VS Code and your own agents.

Then an API key, created on the same screen for one workspace and environment. It decides the tenant, capture mode and policies of every call.

Integrations · sample data from the built‑in demo organization

And out again.

Alerts, exports and the API take what Worksi sees to the tools your team already works in.

Email
Incidents, escalations, approvals, budget thresholds and executed actions, filtered by severity. Every plan.
Slack
The same events in the channel you choose. Pro and above.
Signed webhooks
JSON to your endpoint, with X-AIW-Timestamp and an HMAC‑SHA256 X-AIW-Signature to verify it. Pro and above.
Exports
CSV or JSON of traces, incidents, cost and ROI on Pro and above, and of the audit log on Business and Enterprise.
REST API
Everything the console does, with personal access tokens and your role’s permissions.

Pick a path. Send one request.

Create a key in Governance → API keys and set two variables. The official OpenAI SDKs read both, so your code stays as it is.

  • 3‑day trial with Pro features, no card.
  • The built‑in simulator answers until you add a provider key.
Terminal
# Governance → API keys (the key is shown once)export OPENAI_API_KEY="aiw_sk_live_…"export OPENAI_BASE_URL="https://gateway.worksi.ai/v1"