Verification is one request. No key, no account.
Reading a seal is deliberately unauthenticated and unmetered. Anything that writes needs credentials and keeps a person in the loop.
Check a certificate
curl -s https://ugc.veritasdigital.tech/api/v1/verify/<slug>
Returns whether the seal is valid, the moment it was sealed and the Bitcoin block the fingerprint is anchored to. The same information a human sees at the public verification link.
From an AI agent
There is an MCP server exposing a small set of scoped tools, so an assistant can confirm a file is sealed and when, without a person having to relay it. Read operations are open; anything that creates a record requires explicit human approval. That boundary is the design, not a limitation we intend to remove.
Why you can trust the answer
You do not have to trust our endpoint at all. The RFC 3161 seal is verifiable against the issuing authority, and the OpenTimestamps proof is verifiable against the Bitcoin blockchain with the reference client. Our API is a convenience, not the source of truth — which is the only arrangement that survives us going away.