Verified company facts

Every answer your team and your AI give, backed by a fact someone actually owns.

Nuggetbase turns scattered company docs into verified facts - each with a named owner, evidence and a review date - and serves only those to your team and any AI tool over MCP. No citation, no answer.

Join the waitlist See how it works

Drive doc

Northland licensing.docx

Wiki page

Payments / Clearing

Old RFP

RFP_2024_final_v3.pdf

AI assistant · via MCP

Are you licensed for clearing in Northland?

Yes - Acme Payments Northland Ltd holds a Type-7 clearing licence [1].

[1] Licence register · owner Compliance · verified as of 12 Oct 2026

The problem

Your facts live everywhere. Nobody owns them.

Same question, every bid

Every RFP and security questionnaire asks what the last one asked. Someone still hunts through Drive, the wiki, Slack and people's heads to find the answer.

Three answers, one fact

The wiki says one thing, the website another, last year's bid a third. Nobody is sure which is current, or who would know.

AI repeats the wrong sentence confidently

Point an AI tool at your docs and it will happily quote the outdated one. It sounds sure. It has no idea who checked it.

How it works

From scattered docs to answers you can stand behind

1
Extract
Read-only connectors pull from where your facts already live. AI proposes nuggets and fills in the context: product, country, segment.
- Google Drive · live
- Confluence Coming soon
- Slack Coming soon
- Notion Coming soon
Context, de-duplicated
QuickPay live in 5 markets, PayLink in 3 - 6 distinct overall.

Owner verifies

The named owner confirms each nugget with evidence and a review-by date. Agents can suggest edits, but they go to the owner for approval.

Verify from Slack Coming soon

nugget.json

{
  "specVersion": "0.1",
  "id": "urn:acme:nugget:licence.clearing.northland",
  "statement": "Acme Payments Northland Ltd holds a Type-7 clearing licence.",
  "object": { "type": "licence.clearing" },
  "scope": { "summary": "Northland", "dimensions": { "market": "northland" } },
  "owner": { "id": "team:compliance", "displayName": "Compliance" },
  "citations": [{ "kind": "document", "locator": "https://wiki.acme-payments.example/compliance/licences", "retrievedAt": "2026-10-12T09:00:00Z" }],
  "status": "verified",
  "recorded": { "at": "2026-10-12T16:00:00Z" },
  "reviewBy": "2027-04-12"
}

Served over MCP

Only verified nuggets reach your team and any MCP-compatible AI tool. Each answer carries its citation and a "verified as of" date.

mcp response

{
  "answer": "Yes - Acme Payments Northland Ltd holds a Type-7 clearing licence [1].",
  "citations": [{
    "ref": 1,
    "nugget": "nug_7f3k",
    "owner": "Compliance",
    "verified_as_of": "2026-10-12"
  }]
}

Conflicts

When two sources disagree

We don't quietly pick a side. Conflicts go to the person who owns the fact, and only the answers that depend on it wait.

Internal wiki

Northland QuickPay clears in Cycle-A

Public site

Northland QuickPay clears in Cycle-D

Conflict · routed to Treasury

QuickPay clearing cycle in Northland

Keep currentAccept newBoth true (split scope)Not mine

Dependent answer

"Which clearing cycle does QuickPay use in Northland?"

Blocked until Treasury resolves

Why it's different

Built around the fact, not the document

Per-fact, not per-page

Owner, expiry and evidence sit on every fact, not on a whole document.

Conflicts routed to owners

Disagreements go to the person who knows. Nothing gets silently overwritten.

"Verified as of" travels with every answer

Whoever reads the answer can see who checked it, and when.

One fact, reused everywhere

RFPs, security reviews, sales answers and agents all draw on the same fact. It isn't locked inside one RFP project.

Principles & trust

Rules we hold ourselves to

Cite or refuse

Enforced in the server, not in a prompt. No citation, no answer.

Intelligence proposes, owners decide

AI drafts and suggests. A person signs off.

Read-only

We never write back to your systems.

We never train on your data

Your facts are yours. Full stop.

Clean export, any time

Take everything with you in a standard JSON format.

Built to keep tenants apart

Multi-tenant Postgres with row-level security, per-tenant encrypted connector tokens, EU hosting. US region Coming soon

Who it's for

For the people who answer the same questions all year

RevOps and bid / proposal teams answering RFPs, RFQs, DDQs and security questionnaires. We're starting with mid-market fintech and payments.

RFPsRFQsDDQsSecurity questionnaires

And for the people who own the facts

Compliance, Finance, Product / Eng and Legal confirm what's theirs in seconds.

Waitlist

Get early access

We're opening Nuggetbase to a small number of teams first. Leave your details and we'll be in touch.

Simple self-serve pricing Coming soon

FAQ