API in production

If it ran,
you can prove it.

Serial Alice turns compute into verifiable proof. Every workload becomes a signed, independently verifiable record — no trust required.

GPU. CPU. RAM. AI jobs. Pipelines. Any compute workload. Same proof.

Run your first proof View API docs

Ed25519SHA-256MerklePolygonCT log

terminal — issue compute proof

$ curl -X POST https://api.serialalice.pt/v2/certificate-requests   -H "Authorization: Bearer sa_..."   -d '{
    "workload_id":"training_run_001",
    "measurement_source":"nvml",
    "energy_wh":847.3,
    "grid_region":"EU-PT"
  }'

# 202 Accepted — proof being issued...

{
  "certificate_id": "sa-a087bcd798724d5c",
  "status": "ISSUED",
  "proof": {
    "signature": "ed25519:7f3a...",
    "overall_valid": true
  },
  "verify_url": "https://api.serialalice.pt/v2/certificates/.../verify"
}

certificate · cert_abc123

Issued · Verified

Certificate ID

cert_abc123

Verify endpoint

https://api.serialalice.pt/v2/certificates/cert_abc123/verify

Verification result

overall_valid: true

hash_valid: true

signature_valid: true (Ed25519)

merkle_valid: true

anchor_valid: true (Polygon)

What can you prove?

Compute is no longer a black box.

Use Serial Alice wherever execution needs evidence — internally, for customers, or for audit and compliance workflows.

AI training runs

Turn long-running GPU training into signed records with verifiable energy and execution evidence.

GPU inference jobs

Prove batch and production inference workloads without relying on screenshots, spreadsheets or manual reports.

Batch data pipelines

Attach proof to ETL, scheduled compute and data processing jobs across broader infrastructure contexts.

CPU workloads

Support broader compute environments beyond GPU-first workflows, including CPU and system-level measurement evidence.

Energy reporting

Move from internal estimates to signed evidence for customers, procurement and technical review.

Carbon accounting

Use verifiable compute records as input for sustainability and CSRD-related reporting processes.

How it works

Four steps from workload to proof.

Step 01

Send workload data

POST your compute job metadata — workload ID, energy reading, measurement source, grid region.

POST /v2/certificate-requests

202 Accepted. Processing is async.

Step 02

Certificate is issued

The policy engine computes energy and CO₂ from your measurement. A signed certificate is persisted.

GET /v2/certificate-requests/{id}

Poll until status: ISSUED.

Step 03

Signed and anchored

Ed25519 signature over SHA-256 hash. Merkle batch submitted to Polygon. CT log entry appended.

GET /v2/certificates/{id}

Proof lives in certificate.proof.*

Step 04

Anyone verifies independently

Verification is public. No auth. No account. No trust in Serial Alice. Just math.

GET /v2/certificates/{id}/verify

overall_valid: true means verified.

Cryptographic proof

Verification does not require trusting Serial Alice.

Every certificate carries a complete cryptographic evidence chain. An auditor with no Serial Alice account, using only the public key and standard cryptography libraries, can independently confirm authenticity.

View public trust registry →

SHA-256

Hash integrity

Certificate payload is hashed. Any modification invalidates the hash.

Ed25519

Ed25519 signature

Hash is signed. Public key published at /v2/trust/keys. Offline verification supported.

Merkle

Merkle inclusion

Certificate batched into a Merkle tree. Root submitted to Polygon calldata.

Polygon

Blockchain anchor

Merkle root confirmed on-chain. Independent of Serial Alice database.

RFC 6962

CT log chain

Append-only transparency log. Hash chain from genesis. Tampering detectable.

Why now?

AI workloads are exploding. Proof is no longer optional.

Compute is under scrutiny. Energy use is under scrutiny. Reporting expectations are rising. The missing layer is not more dashboards. It is proof.

Pricing

One metric. Three tiers.

Choose based on how much proof you need to issue — not on how much marketing text you can tolerate.

Free

Start issuing

For testing the API and issuing your first compute proofs.

€0 /month

10 certificates / month

1 host

run + read access

no webhooks

Get started free

Pro

Scale workloads

For real usage, repeated issuance and operational integration.

€99 /month

500 certificates / month

10 hosts

webhooks included

standard support

Run your first proof

Enterprise

Audit and compliance

For production-scale proof, reporting and internal controls.

€999 /month

Unlimited certificates

enterprise endpoints

SSO and dedicated support

audit-ready workflows

Start proving your workloads.

Serial Alice is the missing layer between compute and trust. Issue signed records, verify them anywhere, and stop asking counterparties to "just trust the dashboard."

Run your first proof Open docs

If it ran,
you can prove it.

Don't take our word for it.

Compute is no longer a black box.

AI training runs

GPU inference jobs

Batch data pipelines

CPU workloads

Energy reporting

Carbon accounting

Four steps from workload to proof.

Send workload data

Certificate is issued

Signed and anchored

Anyone verifies independently

Verification does not require trusting Serial Alice.

Hash integrity

Ed25519 signature

Merkle inclusion

Blockchain anchor

CT log chain

AI workloads are exploding. Proof is no longer optional.

One metric. Three tiers.

Start proving your workloads.

Try it right here

If it ran,you can prove it.

Don't take our word for it.

Compute is no longer a black box.

AI training runs

GPU inference jobs

Batch data pipelines

CPU workloads

Energy reporting

Carbon accounting

Four steps from workload to proof.

Send workload data

Certificate is issued

Signed and anchored

Anyone verifies independently

Verification does not require trusting Serial Alice.

Hash integrity

Ed25519 signature

Merkle inclusion

Blockchain anchor

CT log chain

AI workloads are exploding. Proof is no longer optional.

One metric. Three tiers.

Start proving your workloads.

Try it right here

If it ran,
you can prove it.