A fact passport for every business

Publish business facts once. Serve them to people and AI agents.

Intesta keeps attributable facts, sources and proof boundaries in one registry. Visitors use a human interface; software uses HTTP or MCP. If supporting evidence is missing or stale, the answer path can refuse.

How it works

From a domain to a reusable fact passport

Owners remain responsible for what they publish. Intesta records where facts came from, what was checked and when a consumer should refuse to rely on missing or stale evidence.

  1. RegisterCreate a draft entity with passwordless email sign-in.
  2. Verify the domainProve control through DNS TXT or a well-known HTTPS file.
  3. Publish factsAdd or confirm statements, sources and disclosure levels.
  4. Serve both audiencesUse the human widget, public passport, HTTP API or MCP.

Three starting points

Choose the journey that matches your work

No visitor should need to interpret raw JSON before deciding what to do next.

Business owners

Register a domain, prove control, build a public passport and see what people and agents ask.

Compare business plans

Developers and agents

Connect by HTTP or MCP, create an API key, test the refusal contract and monitor unit use.

Open the developer guide

Agencies

Maintain client entities from one account. Automatic ownership takeover exists only before an A0 draft is verified and published; transfer after A1 is not implemented.

See the agency workflow

Trust without overclaiming

The level describes the check, not universal truth

A1 proves domain control. A2 records a provider-confirmed payment tied to the authenticated owner and entity; it does not verify payer identity. A3 matches a legal identifier and name in a supported registry. A4 records a named person's declaration over an identified passport version. None of these automatically proves every fact.

Public registry

Find an existing business passport

Search by business name, domain or vertical. An absent domain means it has not been checked by this registry, not that it failed verification.

Search the registry
Loading published entities…