Not a list of promises: each point comes with how to check it right now, without an account. If any of it ever stops being true, this page fails before you do.
A PDF with the applicable legal framework, what each piece of evidence proves, and the protocol for the opposing expert to check it without going through us. Limits included: a report that only says what suits it does not hold up before a judge.
Check it →art. 326.2 LECThe fingerprint is on the Bitcoin chain. If CODEX shuts down tomorrow, your document is still verifiable with public tools.
Check it →ots verifyNo signup, no cost, no permission. And not just ours: upload anyone's OpenTimestamps proof and we tell you what it anchors and where.
Check it →POST /api/v1/verify/otsOpen MCP server. Claude or ChatGPT check a document with no work on your side.
Check it →https://www.aim-codex.ai/mcpOn Android, once installed, CODEX shows up in the Share menu: a PDF, a photo, a screenshot, three seconds. On iPhone, from the browser.
Check it →share_targetYour link in your email signature. Whatever they send arrives sealed with name and time, no account on their side.
Check it →/recibir/<your-account>How many documents you've sealed and since when. Never titles or clients. Opt-in.
Check it →/emisor/<your-account>Each credential reads as a W3C Verifiable Credential. Not yet signed by the issuer (what wallets require): the proof points to Bitcoin.
Check it →/v/<fingerprint>/w3c.jsonHow the seal is computed, anchored and verified. Implement it if you like.
Check it →/estandar36 languages, detected from the browser. You do nothing.
Check it →Accept-LanguageNo document cap, no per-seat price: the two grievances the industry squeezes with. (The emails CODEX sends on your behalf do have a daily quota, against spam.)
Check it →/precios