Build with Evidentia

5-minute quickstart

Create a proof from your backend, then share verification evidence.

1. Create an Open Beta workspace and generate an API key.
2. Store the API key server-side only; never expose it in frontend code.
3. Send proof metadata with Authorization: Bearer API_KEY and an Idempotency-Key.
4. Poll proof status, then store proof_id and verification_url in your own system.
5. Share the public verification link or export package only for proofs intentionally made public.

Why Evidentia exists

Logs explain. Evidence proves.

AI outputs and usage records are becoming operational evidence. Evidentia gives teams a way to preserve verifiable records while keeping raw prompts, outputs, and sensitive context in their own systems.

API

API Overview

Use server-side authentication, a unique Idempotency-Key, and minimized proof metadata to create Proofs safely.

Create a Proof via API

POST /api/proof/request

Request proof. Check proof status. Store proof_id and verification_url.

curl -X POST "$EVIDENTIA_API_BASE_URL/api/proof/request" \
  -H "Authorization: Bearer <API_KEY>" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: <UNIQUE_KEY>" \
  -d '{
    "event_type": "ai_decision",
    "input": {
      "request": "Sample decision request"
    },
    "output": {
      "decision": "approved",
      "reason": "Sample result"
    },
    "metadata": {
      "source": "api_example"
    }
  }'

How it works

From backend event to verifiable proof

1. Your backend sends proof metadata.
2. Evidentia hashes and signs the proof.
3. The proof is stored with verification metadata.
4. The proof may be anchored to a blockchain network.
5. Anyone with the public URL can verify the proof.

Call Evidentia from your backend, avoid sending raw AI data by default, and use public verification without exposing raw prompts or outputs.

Client storage

Store the IDs you will need later

After a Proof is requested and completed, store these values in your own system.

• decision_id
• idempotency_key
• job_id
• proof_id
• verification_url
• public_proof_api_url
• status
• created_at
• related_internal_log_id

Proof request

POST /api/proof/request

Request proof. Check proof status. Store proof_id and verification_url.

curl -X POST "$EVIDENTIA_API_BASE_URL/api/proof/request" \
  -H "Authorization: Bearer $EVIDENTIA_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: decision_123" \
  -d '{
    "event_type": "ai_decision",
    "event": {
      "prompt": "sha256:<input_hash>",
      "output_summary": "sha256:<output_hash>",
      "context": {
        "decision_id": "decision_123",
        "model": "gpt-4.1",
        "environment": "production",
        "source": "customer_backend"
      }
    }
  }'

{
  "ok": true,
  "queued": true,
  "job_id": "decision_123",
  "status": "processing",
  "status_url": "/api/proof/status/decision_123",
  "message": "Proof request accepted"
}

GET /api/proof/status/decision_123
Authorization: Bearer <EVIDENTIA_API_KEY>

{
  "ok": true,
  "status": "completed",
  "job_id": "decision_123",
  "proof_id": "EV-...",
  "verification_url": "https://<domain>/public/verify/EV-...",
  "public_proof_api_url": "/api/public/proofs/EV-..."
}

Share public verification URLs with auditors, customers, or third parties only for proofs that have been intentionally published. During Open Beta, customer proofs are private by default.

Evidentia does not replace your application logs. Send a payload that references, summarizes, or hashes the decision, then store the returned proof identifiers in your database.

Example code

Start from the repository examples

Use the Node.js / Express example as a base, then adapt it to your backend.

• packages/evidentia-node - Node SDK foundation
• packages/evidentia-python - Python SDK foundation
• cli/evidentia-verify - Verification CLI foundation
• docs/postman/Evidentia.postman_collection.json - Postman collection
• docs/http/evidentia.http - HTTP examples
• examples/node-express/server.js
• examples/node-express/.env.example
• examples/nextjs-api-route/route.js
• examples/python-fastapi/main.py
• examples/node-proof-request.js
• examples/python-proof-request.py
• examples/curl-proof-request.sh
• docs/QUICKSTART.md
• README_INTEGRATION.md
• docs/DEVELOPER_ONBOARDING.md
• DEMO_PROOF.md

Stable public demo proof: EV-DEMO-PUBLIC-001. Open the fixed Public Verification page.

System proof: EV-SYSTEM-PROOF-001. Open the System Integrity Proof page to verify Evidentia’s proof generation, anchoring, and verification operations at a structural level.

Fixed demo and system proofs use Solana devnet anchoring. Mainnet, multi-chain verification, and dedicated infrastructure are planned production capabilities and are not self-service during Open Beta.

Current Open Beta uses platform-managed signing infrastructure intended for technical evaluation. Developer access is self-serve, paid plans are request-only, and live billing remains gated.

Verification export packages are available for public proofs and authorized private proofs; raw AI payloads are not included by default.