AI Trust Protocol™ (AITP™)Verifiable records for the AI internet.
A protocol for recording, signing and resolving verification results. It lets people and AI agents inspect what was verified about an entity, who verified it, when, and the scope of the credential, before they buy, cite or recommend.
Live registry lookup. It reads the record cache and never starts a new verification. Responses are signed; you can verify the signature in your own browser against the published public key.
One real record, field by field.
This is the live record for veragraph.ai, our own platform, chosen because it is verified and public. The left side is the actual response. The right side explains each field.
- issuer · standardWho signed the record (VERA™) and under which protocol (AITP™).
- status.recordWhether the record is live or archived. Archived records still resolve, and say so.
- status.recognitionWhether the entity is a recognized, resolvable identity in the registry.
- status.verificationWhether verification has been completed, by whom and to what scope. "Unverified" means nobody has checked yet; it is not a failure.
- status.claimedWhether the entity's owner has claimed the record.
- measurementAI-visibility measurement with its own timestamp. A measurement, never a verdict on truth.
- public_url · as_ofWhere a person can read the record, and the moment this envelope was produced.
- signatureES256 over the canonical body, base64 DER. A valid signature authenticates the record against the published key and lets a verifier detect any change.
A record, four independent statuses, a signature, and one way to resolve it.
One record per entity
Keyed by the entity's domain, the identifier every commerce and answer protocol already shares. Sub-assertions, each dated and expiring, sit inside it and name their issuer.
Four axes, never one score
Record, recognition, verification and claimed are reported separately, so an agent can tell "known but unverified" from "verified" from "verified and owner-claimed".
ES256 over canonical JSON
Sorted keys, compact form, signature excluded. The public key is published. Anyone can check a record without asking the authority.
One GET, one answer
Resolve a domain and receive the signed envelope. Absence is a signed, honest answer, not a failure to retry.
VeraGraph™ operates it. The rest of the family plays one role each.
VeraGraph™
The first and fullest implementation. Verification runs here, credentials are issued here on verified assets, and holders measure whether they are cited and recommended. Bundles V-Verify™ and FeedSync AI™.
V-Verify™
Verifies content, identity and commerce facts and issues signed credentials, including born-verified provenance for images and video.
AITP Cert™
The credential a merchant or organization carries. Verified by V-Verify™, issued through VeraGraph™, recorded by VERA™.
FeedSync AI™
Pushes verified records into the reference channels AI systems read, so a record is found where the answer is written.
Keep Christmas Real
A live commerce marketplace where sellers request verification and carry records on their storefronts.
Use the protocol
Resolve records freely; the endpoint is public and cache-only. Implement it as a registrar by issuing signed sub-assertions under your own name, or as a consumer. Say "Built on the AI Trust Protocol™ (AITP™)" and link here. Attribution stays with the issuer: a record says "V-Verify™ asserts", never a blended verdict.
Enterprise and partnerships
Registrar programs, platform integrations, volume resolution with service levels, and white-label credentials are handled by the sales team. Contact the sales team.
What has shipped, with dates you can check.
Public releases link to something you can open. Development milestones are listed separately and are dated by registry records or company records held for counsel.
- 2026-04-28
- VERA™ Verification Standard v1.0 published, the evidence-based classification framework of the AI Trust Protocol™. Revised to v1.1 on 2026-06-15.
- 2026-06
- VERA™ Registry public launch with free search and signed records. Provisional patent application filed.
- 2026-07-21
- Four independent status axes adopted: record, recognition, verification, claimed.
- 2026-08
- VeraGraph™ issuing commerce credentials on verified product assets. V-Verify™ born-verified provenance live.
- 2026-09-03
- Public resolve endpoint live with a published verification key. Every envelope signed, absence included.
- 2026-09-06
- This site, and AITP Cert™, the annual entity credential with checkout.
- 2011-12-28
- stealthgrid.com registered. Stealth Grid Corp, steward of the VERA™ Registry, begins its decentralized-trust work.
- 2024-12
- AI Trust Protocol™ development begins inside the GemIQ and VtaaS backend. Company records, date confirmed with counsel.
- 2025-02-07
- quantumxproject Google Cloud project created.
- 2025-06-27
- gemiqai Google Cloud project created; vtaas-backend service follows on 2025-09-10.
- 2025-12-07
- feedsyncai.com registered.
- 2026-04-21
- veraregistry.com registered.
- 2026-05
- veragraph.ai and vverify.ai registered.
- 2026-09-06
- aitrustprotocol.ai, aitpcert.com and the aitp.technology, aitp.network and aitp.space family registered.
Short answers.
What does a signed record prove?
A valid signature authenticates the signed record against the published key and lets a verifier detect any change to it. What the record establishes depends on its verification scope and supporting evidence, which the record names. It never asserts that a price is best or a claim is true.
Can a merchant pay for a better status?
No. The authority charges for recording and renewal, never for the outcome. A record that fails verification is not issued.
How does this relate to UCP, ACP and AP2?
Those protocols describe how an agent transacts, including payment authorization. The AI Trust Protocol™ supplies the signed verification evidence an agent can inspect about the merchant, resolved by domain, before it does. An integration point, not an announced partnership.
What does "open specification" mean here?
The specification is published in full and free to read, resolve against and implement. Its current status is v1.1. License and contribution terms are published alongside it; the underlying method is patent pending.
Is the AI Trust Protocol the same project as aitp.dev?
No. The AI Trust Protocol™ (AITP™) is separate from the Agent Interaction & Transaction Protocol published at aitp.dev.
- VERA™ RegistryAuthority
- AITP™Protocol
- VeraGraph™Platform
- V-Verify™Verification
- FeedSync AI™Distribution
The deployed resolve endpoint.
The live endpoint is served from VERA™ production infrastructure. "resolve()" on this page is shorthand for this GET. A same-origin mirror runs on this site at /api/resolve for the boxes above. A branded API path will be documented here when it ships, not before.
GET https://vtaas-backend-220419304601.us-central1.run.app/api/vera/public/resolve?domain=costco.com GET https://vtaas-backend-220419304601.us-central1.run.app/api/vera/public/resolve/meta curl -s "https://vtaas-backend-220419304601.us-central1.run.app/api/vera/public/resolve?domain=costco.com"
- params
domain,slugorq. A URL is reduced to its registrable host.- found
truewith the record, orfalsewith a signed absence.- status
- Four axes:
record,recognition,verification,claimed. - measurement
- AI-visibility measurement with its own timestamp. A measurement, not a verdict on truth.
- signature
- ES256 over canonical JSON (sorted keys, compact, signature excluded), base64 DER. Public key at
/resolve/meta. - cache
- Cache-only by design. Never starts a verification. Safe for agent traffic at any scale.