The ground truth your AI agents work from.
Docs your team and your agents read and write together. When one agent saves a fact, every other agent reads it, with its source and date. Nothing connects to your accounts.
Your first fact in minutes · MCP, API, CLI or dashboard · No account access needed
Incident escalation path
Each fact has its own name, version, source and date
#paymentsUpdated#severityCurrent#oncallCurrent#customer_updatesCurrent#postmortemsCurrentRefund and credit policy
Each fact has its own name, version, source and date
#approval_limitUpdated#windowCurrent#store_creditCurrent#exceptionsCurrent#chargebacksCurrentVendor onboarding checklist
Each fact has its own name, version, source and date
#security_reviewUpdated#documentsCurrent#payment_termsCurrent#approversCurrent#tax_formsCurrentAgents are doing real work on information nobody can verify.
Stale or wrong facts
Agents pull from wikis, threads and old documents. A renewal date that moved last week still looks true, and the agent acts on it.
No trail
When an agent makes a call, no one can see which fact it relied on or where that fact came from.
Agents contradict each other
Each agent keeps its own notes, so they redo work and give different answers to the same question.
Memory nobody can check
Facts buried in prompts or vector stores can't be read, corrected or audited by the team.
One shared record for your team and every agent.
Docs for people, facts for agents
Your team or its agents write docs like a refund policy or an account brief. Each part is a named fact, from a date to a paragraph, list, table or file, that any agent can ask for by name.
Nothing of yours to connect
You point your agents at Factbed. Factbed never connects to your company's accounts, so there's no access to approve.
Every change is kept and checked
Agent changes can wait for a person or a reviewing agent to confirm. The full history stays, so you can tell what an agent knew and when.
From a customer issue to a fix, and back.
Each team's agents build on what the other team already found, instead of it staying in one person's chat history.
-
1Account manager
Finds the pattern
With her agent, she works through customer data and support notes to see which customers report slow service, since when, and what they share.
-
2Account manager
Saves the findings
Her agent writes them to Factbed as a doc of named facts, each with evidence and a date. Her ticket to the dev team links to the doc.
→ Writes to Factbed -
3Developer
Starts from what's confirmed
His agent pulls her findings from Factbed instead of searching again from scratch.
← Reads from Factbed -
4Developer
Adds what the team learns
As he works, his agent records the root cause, the fix, and the release it ships in.
→ Writes to Factbed -
5Sales
Updates customers
Anyone in sales asks their own agent for an update and can tell customers what changed and when, without chasing developers.
← Reads from Factbed
Use it from your agents, your code or your browser.
Four ways in, one record. A fact written over MCP is the same fact your API calls, scripts and dashboard read.
Recommended for agents
Paste one URL into Claude, ChatGPT, Cursor or any MCP client and sign in. Your agents get tools to read, write and search facts, and to check what changed.
# Claude or ChatGPT: add a custom connector https://mcp.factbed.io/mcp # Claude Code $ claude mcp add --transport http factbed https://mcp.factbed.io/mcp # Cursor, VS Code and others: mcp.json "factbed": { "url": "https://mcp.factbed.io/mcp" }
For your own services
Call Factbed over HTTPS from your backend or agent framework. Read a fact by name, write a new version with its source, or list what changed since a date.
# Read a fact $ curl https://api.factbed.io/v1/facts/customer.northwind%23renewal_date \ -H "Authorization: Bearer $FACTBED_KEY" # Write a new version with its source $ curl -X PUT https://api.factbed.io/v1/facts/customer.northwind%23renewal_date \ -H "Authorization: Bearer $FACTBED_KEY" \ -d '{"value": "2027-03-01", "source": "CRM note"}' { "version": 4, "status": "current" }
For scripts and CI
Read and write facts from your terminal, shell scripts and CI jobs. Useful for loading a price list, or checking a fact before a deploy goes out.
$ factbed get customer.northwind#renewal_date 2027-03-01 v4 · CRM note · 2026-11-02 $ factbed set customer.northwind#renewal_date 2027-03-01 \ --source "CRM note" ✓ Saved as v5 $ factbed import prices.csv --doc pricing.list ✓ 48 facts added, each linked to prices.csv
For people
Write and edit docs in the browser, review what agents changed, and settle conflicts before they spread. Every fact shows its source, date and history.
For teams running more than one agent that need them to agree on the facts.
Built for the engineering or AI lead building the agents. Factbed touches no company accounts, so you can adopt it without a long security review.
- 1Workspace vendors now run autonomous agents on schedules and triggers, so agents act on facts without a human checking each one.
- 2Teams are moving from one agent to several, and each keeps its own memory, so they drift apart.
- 3Agent memory has become its own category, but it's built for one agent's recall, not a record a team can review.
Shared, sourced, and editable by people and agents.
| Alternative | What it does well | What it leaves out |
|---|---|---|
| Wikis and docs (e.g. Notion) | Easy for people to write and read | Pages agents can't cite: no named parts, sources, dates or review when something changes |
| Agent memory (Zep, Mem0, Letta) | Persistent, searchable memory | Built for one agent's recall; hard for people to review and correct |
| Prompts and config files | Simple to start | Go stale silently; no history or ownership |
| Building it in-house | Full control | Months of work on a problem that isn't your core product |
| Factbed | Docs people read, made of named facts with a source, date and version | Nothing to reconcile: agents cite the exact fact, and changes are reviewed before they spread |
Agents you can trust with real work.
-
Every answer has a source
Each answer rests on a fact with a source and a date.
-
One version of the truth
Every agent reads the same record, so they stop contradicting each other.
-
Conflicts land in review
When agents disagree or a fact is going stale, a person or a reviewing agent settles it before it spreads.
-
Start in minutes
Sign up, connect your agent over MCP and save your first fact. No integrations or account access to approve.
customer.northwind#renewal_date| Version | Value | Source | Dated | Status |
|---|---|---|---|---|
| v4 | 2027-03-01 | CRM note · renewals-agent | 2026-11-02 | ✓ Current |
| v3 | 2027-02-28 | Contract amendment · M. Chen | 2026-08-19 | Retired |
| v2 | 2027-01-31 | Support thread · support-agent | 2026-05-04 | Corrected |
| v1 | 2027-01-31 | Signed contract · M. Chen | 2026-01-12 | Retired |
Running two or more agents on shared business facts?
Create a workspace, connect your first agent and load the facts for one workflow.