Verdatum documentation

Verdatum maintains a durable, source-backed organization profile for one confirmed organization. Your AI agent can resolve the organization, read its profile manifest, read the immutable projection versions it needs, and poll on your own schedule to detect change.

Every profile states what its sources support. It also states where coverage is incomplete, unavailable or unsupported.

Three supported workflows

Resolve one organization

Give your agent a name, identifier, website or ticker. Verdatum returns one resolved organization, a short list of candidates, or a clear unresolved outcome. Your agent must ask you to choose when the identity remains ambiguous. Each candidate carries a resolved organization reference that identifies it to the next read.

Read its profile manifest

After you confirm the organization, your agent reads the profile. The response is the profile manifest: one entry for each typed projection you are entitled to read. A resolved organization reference is short-lived and covers one resolve-then-read exchange; afterwards your agent reads with the stable organization_id the manifest returns.

ownership and governance
filings and financials
public markets
sanctions and compliance
intellectual property
life sciences

Every entry reports the same fields: the projection-version identifier, the schema it was validated against, when it was published, when a refresh last succeeded, its freshness state and any typed limitation. The manifest carries no projection content. Your agent reads a version when it needs the facts, and the evidence behind each claim travels inside that version.

Poll on your own schedule

Verdatum runs no hosted monitor. Your client keeps three values: the organization identifier, the time of its next poll, and the last manifest it read. At each poll it reads the profile again and compares each entry's projection-version identifier with the one it retained. A different identifier is a change, and the new manifest becomes the next baseline.

Two exceptions are worth knowing. The first is entitlement: which projections the manifest contains follows your entitlement at each read, and entitlement changes publish no version. A projection that becomes entitled appears with an identifier your client has never held, which reads as a change although the organization's data did not move. Compare the entry sets of two manifests if you need to tell the two apart.

The second is a schema release. When Verdatum publishes a new projection schema, every projection it covers reports its stored version as legacy until that projection is next refreshed, and that refresh publishes a new projection-version identifier whose facts may be unchanged. Several projections can move this way at once. Each entry reports the schema its version was validated against, so comparing the schema identifier you retained against the one the new entry reports is what tells a schema release apart from a change in the organization's data.

Verdatum stores no subscription, no comparison cursor and no relationship between your organisation and the organizations you read. Stopping means your client stops polling.

Reading a profile keeps that organization's refresh demand alive and makes missing or stale projections due. You cannot select which projections are refreshed, and Verdatum never pushes a notification.

Connect Verdatum

Add Verdatum as a custom MCP connector in a supported host. Use this MCP resource URL:

https://mcp.verdatum.ai/mcp

Verdatum supports Claude, ChatGPT and Codex. The connector-directory listing is a separate publication step. Until it is listed, use your host's custom connector setup.

Sign in with your work email when prompted. Access is contracted at organisation level. If your organisation has a current Verdatum contract, you do not need a personal API key.

If you are told that your organisation is not entitled, ask its administrator or email support@verdatum.ai.

Entitlement and coverage

Every customer organization (the tenant) is entitled to the core intelligence domain. It may additionally be entitled to life_sciences across every profile in that tenant. Domain entitlement is separate from source, jurisdiction, record-type and freshness coverage; it is not bought for one focal organization.

The profile always discloses source coverage and limitations. Patent intelligence is supported within the stated source boundaries. In the intellectual_property projection, content.trademarks.state is unsupported and the projection carries limitation code trademark_source_unsupported. An empty trademark collection is not evidence that no trademarks exist.

Tools

Tools complete every supported workflow. The public MCP service exposes exactly these 3 tools, and nothing else:

Tool	Use
`resolve_organization`	search from identity clues and return bounded candidates, each with its own resolved organization reference
`read_profile`	read the entitled profile manifest for one organization, by resolved organization reference or stable `organization_id`
`read_projection_version`	read one complete immutable projection version, with its embedded evidence, by identifier

The service publishes no resources and no prompts, so one projection version has one access path, and projection-version identifiers reach your agent only through a manifest it has read.

Freshness without jobs

read_profile never waits for source work. It returns what is available now and reports each entry's freshness state:

fresh — the current version, with no refresh scheduled
stale_refresh_scheduled — an aged version, with a refresh now due
stale_refresh_coalesced — an aged version, with a refresh already due or running
not_yet_refreshed — no version yet, with the first refresh now due
refresh_blocked — nothing has refreshed successfully for longer than the service threshold while demand stayed active; bounded retries continue

Poll with backoff at the cadence your workflow needs; do not rapid-poll. Repeated reads coalesce behind the service's own refresh threshold. There are no generic jobs or MCP Tasks in the initial product, and a failed refresh never removes the last published version.

Read profile results safely

A usable profile may still have gaps. Check these fields before relying on a claim:

the freshness state and any typed limitation on the manifest entry
published_at and last_successful_refresh_at
the coverage and limitations stated inside the projection version
the evidence attached to each claim
which projections the manifest contains, which follows your entitlement

An entry with no projection-version identifier has not been built yet; that is not evidence that a fact does not exist. An empty collection is not proof that a fact does not exist. A sanctions candidate is not a designation decision. A patent applicant or recorded assignment is not proof of current ownership.

Retained versions

A retained projection-version identifier resolves indefinitely, so a manifest you kept can be re-read exactly as it was assessed. The single qualification is withdrawal: where a recorded obligation requires content to be removed, that identifier returns a typed withdrawn outcome stating when the content was removed and under which class of obligation — a legal obligation, a source licence or an identity error — rather than the content.

Get help

If Verdatum will not connect or a profile looks wrong, email support@verdatum.ai. Include the organization ID, the projection name and the projection-version identifier where available.

The privacy policy explains how Verdatum stores profiles and other service data. Profile content is source-backed information. It is not financial, investment, legal, tax or accounting advice. See the terms of service.