Pricing for people and machines
Businesses publish and maintain a fact passport. Developers and AI agents query the same registry through HTTP or MCP. Every fact keeps its own source and attestation status.
For businesses
Start with email sign-in and domain verification. A paid verification records a provider-confirmed payment tied to the authenticated owner and entity; it does not verify payer identity or certify that every published business fact is true.
For one team beginning a fact passport and proving control of its domain.
For businesses that need longer analytics and a richer moderation view.
Recurring checkout requires billing integration.
For an A1 entity that wants the registry to record a completed provider-validated payment.
For agencies and web studios managing passports for client entities.
Recurring checkout requires billing integration.
Checking current prices and allowances against the plans API…
For developers and AI agents
Public entity pages and passports remain open. Ask and search have a free anonymous daily allowance. API keys identify programmatic use and meter bulk and watchlist operations.
For prototypes and low-volume programmatic access.
For production integrations checking many counterparties or monitoring changes.
Recurring checkout requires billing integration.
A0 to A4
An entity level describes what Intesta checked about the entity. Each fact separately records its source, freshness and attestation status. A higher entity level is not a blanket guarantee of every fact.
The entity is registered. Nothing has been independently verified.
The owner proved control using DNS TXT or an HTTPS well-known file.
A provider confirmed a successful payment tied to the authenticated owner account and entity. This does not verify payer identity or provide KYC.
A legal identifier and name were matched in a supported registry such as VIES or GLEIF.
A named person records responsibility for an identified passport hash. Compare it with the current hash to confirm that it still covers the current version.
Activation and billing
Intesta never grants paid access from a browser success message. A paid state must come from validated server-side billing evidence.
Sign in by email. Register a domain or create an API key. The supported free entitlement is available without recurring checkout.
Register, pass A1, then start the one-time checkout in the cabinet. A2 is applied only after Intesta validates the provider webhook.
You can select the intended plan and continue onboarding, but recurring activation, invoices, upgrades, downgrades and cancellation are not yet connected.
