Your API, fluent in AI.
Frege turns your OpenAPI spec and docs into one AI surface that both answers questions about your API and operates it — grounded in your own docs, governed by your own access rules, audited end to end. Self-host the platform and the model, so your data never leaves your network.
- Self-host the platform & the model
- Your data & model never leave your network
- Grounded, cited answers from your docs
- OpenAPI tools, callable by AI
- Per-tool & per-doc access control
- Versioned · Audited · Air-gap-ready
Knowledge + action, one surface
Stop choosing between an "Ask AI" widget and a programmatic API.
Docs AI products give customers cited answers. Custom MCP servers let agents call APIs. Frege does both — over the same docs, tools, and access rules, with a single audit trail.
Grounded answers, with citations
Frege embeds docs and OpenAPI descriptions, hybrid-searches them on every question, and replies with the chunks it used. No hallucinated parameters. No wrong endpoint names.
Answer, then act — in one turn
"How do refunds work?" gets a cited answer. "Refund INV-7741" calls your real API. The agent decides, access rules decide if allowed, the audit log captures both.
Docs are first-class
Markdown, version-pinned, addressable, and embedded. Used by chat for retrieval, exposed to MCP clients for direct reading, updated through the same workflow as the spec.
Version what an agent sees
Draft, diff, publish, pin, archive, roll back. Tools and docs the AI is grounded in are versioned together — clients pin to v3 and see exactly v3 forever.
Govern access precisely
Ory Keto controls which tools, docs, and projects every user or API key can call or read. The retrieval layer respects the same rules as the proxy.
Operate it with confidence
Every tool call, cited source, grant change, and webhook delivery is auditable. Project runtimes are isolated; webhooks become MCP notifications; org credentials are encrypted at rest.
How it works
Ingest your API. Ground the AI. Govern the action.
Frege turns assets you already have — OpenAPI spec, markdown docs — into one hosted surface that any AI client can read, ask, and act through.
Ingest
Upload OpenAPI 3.0/3.1 specs and markdown docs. Frege turns them into a hosted, fine-grained-authorized MCP server — tools, docs, and retrieval under a single endpoint.
Learn moreGround
Agents call search_docs for cited answers; semantic + keyword retrieval, no hallucinated endpoints.
Learn moreAct
The same agent calls real tools through your API, under Keto-scoped access and approval gates.
Learn moreGovern
Immutable versions, per-key scopes, signed approvals, full audit on both retrieval and execution.
Learn moreWorkspace
Ask a question. Approve the action. One transcript.
Frege chatrooms are a workspace where humans and agents share the same docs, tools, and access rules. Answers cite sources. Writes wait for sign-off. Everything is replayable.
Cited, grounded answers
The agent searches your docs and OpenAPI descriptions before replying. Every fact is traceable to a chunk you can click open.
Approval-gated writes
The same agent can execute the action it just explained — with a human approving the irreversible step in line.
One audit per turn
Retrieval calls, tool calls, approvals, and replies live in one signed transcript your auditors can replay.
No more hallucinated endpoints
The agent only calls tools that exist in your spec and only reads docs that have been published.
"refund window duplicate charges"
Duplicate charges are fully refundable within 30 days; partial refunds available after.
{ "id": "INV-7741" }
Confirmed: $148.00 charged twice on Mar 14 — well within window. Issuing the refund.
{ "charge": "ch_3Mp…", "amount": 14800 }
Sovereignty
Self-host every layer. Limit every user. Plug in any MCP.
The platform, the LLM that powers the chat, the limits each user is bound by, and the external tools the agent can call — all of it runs on your hardware, under your rules, with the keys staying in your hands.
Frege on your metal
A single Go binary plus the open dependencies you already trust — Postgres, MinIO, and Ory. Runs on a VM, in Kubernetes, or on an air-gapped cluster. No SaaS calls. No telemetry.
Local LLMs, native
The chat agent speaks OpenAI-compatible APIs and Ollama out of the box. Run Qwen, Llama, DeepSeek, or Mistral on your own GPU — cited answers and tool calls without a chunk reaching a third-party model.
Limits per user, every layer
Rate limits, max input tokens, and max output tokens — set per user, per role, or per API key. Applied uniformly to retrieval, tool calls, and chat.
Agentic chat, MCP-native
The chat inside Frege is a full agentic AI in its own right. It connects to any external MCP server, so the tools your team already runs show up alongside the ones generated from your OpenAPI specs.
Governed by design
Knowledge and action under the same access rules.
Most "Ask AI" widgets retrieve from a public corpus and have no concept of who's asking. Frege treats retrieval as a privileged operation — the same Keto policy model as the proxy, the same audit trail.
Retrieval respects the same scopes as tool calls
The agent can only retrieve doc chunks the caller is allowed to read. No leaking internal runbooks to a guest API key.
Row-level tenant isolation
Tenant-scoped queries run under PostgreSQL row-level security, so cross-tenant leaks are blocked at the data layer.
Per-tool, per-doc, per-group authorization
Ory Keto decides which tools, documents, and projects each user or API key can call or read.
One audit log for retrieval and execution
What the agent searched, what chunks it returned, what tool it called, who approved the write — all in one signed transcript per turn.
cited answers
tools
target api
audit trail
runtime
Why Frege
Two questions, one assistant. Three audiences, one surface.
If you've shipped a docs widget, a custom integration layer, and a bespoke chat for your support team — you've built three things that should be one. Frege is the one.
“In our department, AI cannot improvise. Frege grounds every answer in our own official guidance, with citations our compliance team can verify, and lets our agents act on our APIs under the same access rules. That is the difference between a demo and a deployment we can stand behind.”
Nodir Ruzimurodov
Head of AI / ML, Ministry of Economics & Finance of Uzbekistan
“We run a lot of services across the country, and we evaluate platforms by how they fit our existing operational model. Frege does — versioned per project, isolated per tenant, one audit trail per request. It reads as infrastructure, not as a black box bolted onto our stack.”
Yunus Faxriddinov
DevOps Specialist, Uzinfocom
“AI integrations are a new attack surface for the public sector. Frege's per-resource authorization model and unified audit trail give our reviewers something they can actually approve, with the controls and visibility our regulations require.”
Rasul Urazbayev
Managing Director, Ministry of Cybersecurity
Pricing
Start with one API. Grow to one assistant for everyone.
Self-hosted or cloud-hosted — same product. Self-host the platform and the model to keep your data on your hardware at every tier. Add docs, add tools, add scopes; everything else is incremental.
Developer
Get a single project live in an afternoon — spec, docs, grounded chat, MCP endpoint. Validate tool shapes and answer quality before you commit to a rollout plan.
- Upload OpenAPI & markdown docs
- Hybrid retrieval over your corpus
- Cited answers + tool calls in one chat
- Connect Claude, Cursor, Codex, or Amp
Platform
For teams shipping the AI surface as real infrastructure: versioned, governed, embeddable, with the same access rules across retrieval and execution.
- Draft, diff, publish, rollback, and pin versions
- Per-tool, per-doc, and per-group authorization
- Webhook receivers + MCP notifications
- Internal & client surfaces from one workspace
Enterprise
For banks, ministries, and org-scale rollouts: on-prem or air-gapped deployment, delegated access, encrypted credentials, custom auth, and one buyer-facing security narrative covering both retrieval and action.
- Per-tenant SSO & OIDC providers
- Encrypted org credentials & delegated tokens
- One audit trail for retrieval & execution
- Shareable connect flow for downstream onboarding