Seal it from your own software

If your firm already works in a practice-management tool, you don't need to move: these six steps are enough to seal a document and send it as a verifiable link from where you already are.

Your key

It's in Settings → API. Send it in the X-API-Key header of every call. Don't put it in code that reaches the browser.

1. Create the document

curl -X POST https://www.aim-codex.ai/api/v1/documents/write \
  -H "X-API-Key: TU_CLAVE" -H "Content-Type: application/json" \
  -d '{"title":"Presupuesto reforma","markdown":"Total: 6.000 EUR"}'

2. Seal it

curl -X POST https://www.aim-codex.ai/api/v1/documents/DOC_ID/seal \
  -H "X-API-Key: TU_CLAVE" -H "Content-Type: application/json" -d '{}'

3. Create the client link

curl -X POST https://www.aim-codex.ai/api/v1/documents/DOC_ID/share \
  -H "X-API-Key: TU_CLAVE" -H "Content-Type: application/json" \
  -d '{"label":"Construcciones Lopez","allow_accept":true}'

4. Check opens and acceptances

curl https://www.aim-codex.ai/api/v1/acceptances -H "X-API-Key: TU_CLAVE"

5. Download the evidence dossier

curl https://www.aim-codex.ai/api/v1/documents/DOC_ID/dossier \
  -H "X-API-Key: TU_CLAVE" -o expediente.pdf

6. Check a document with no key

curl https://www.aim-codex.ai/api/v1/verify/HUELLA_SHA256

That's it. The link returned in share_id opens without an account, in your client's browser language, and can be checked against Bitcoin without going through us.

Let it tell you

In Settings → API you set an address of yours and CODEX calls it when something happens. No polling: your practice tool finds out the moment the client signs.

POST https://tu-gestor.example/codex
{
  "event": "document.accepted",
  "doc_id": "doc-XXXXXXXX",
  "content_hash": "6ab026dc...",
  "name": "Antonio Lopez",
  "at": "2026-09-04T09:52:00Z"
}

Events sent:

• document.first_open
• document.accepted
• document.signatures_complete
• document.rejected
• document.counteroffer
• document.revoked
• document.anchored
• document.received

Each call is signed with your secret, so you know it came from us. And since it's a plain HTTP request, it works just as well with Zapier, Make or anything that can receive a webhook.

What about your practice tool?

We don't need to build a connector for each one. Put a Zapier or Make address in the webhook field and route it to whatever you use: Holded, spreadsheets, your CRM or the team inbox. Ten minutes, no code.

We put it this way because it's what works today, not what we'd like to announce. If your tool isn't on either, the API above works just as well.

Credentials in the open standard

If you issue credentials, each one can also be read as a W3C Verifiable Credential: the format wallets and verifiers that follow the standard understand. Public and keyless, like all our verification. The proof inside isn't a signature of ours: it's the Bitcoin anchor.

How the seal is computed, step by step →

curl https://www.aim-codex.ai/v/HUELLA_SHA256/w3c.json

Rather have your assistant do it?

Connect https://www.aim-codex.ai/mcp as an MCP server in Claude or ChatGPT and ask it to check a document. No account, no cost.