Developer API — V-Quantum

Quick test (no key)

curl -s https://api.animisha.dev/v1/health

Returns auth_required: false while early access is open. Luna + C flip that when real keys ship.

Collapse (needs key when auth on)

curl -s -X POST https://api.animisha.dev/v1/collapse \
  -H "Content-Type: application/json" \
  -H "X-API-Key: YOUR_KEY" \
  -d '{"goal":"Ship MVP tonight","branches":3}'

Endpoints

GET /v1/health — liveness (public)
POST /v1/collapse — goal → best plan
GET /v1/benchmarks/summary — parallel vs sequential proof (auth required)
GET /v1/substrate — V-Quantum substrate snapshot
GET /v1/usage — monthly collapse metering
GET /v1/attest/{request_id} — Business tier+ attestation

Early-access benchmarks (honest)

Branch interference fan-out on 8 branches — measured on Luna's dev machine, not marketing fiction. Speedup can be below 10× (thread overhead on small workloads is real).

curl -s https://api.animisha.dev/v1/benchmarks/summary \
  -H "X-API-Key: YOUR_KEY"

Latest dev-machine run (8 branches, 5 iterations): sequential 0.044ms vs parallel 0.553ms — 0.08× speedup (parallel is slower at this scale; thread overhead dominates). Larger customer-shaped workloads may flip positive — re-run on GCP after deploy.

Get a key

Email quantum@animisha.dev — manual provisioning for now. Stripe checkout is intentionally deferred.

Python SDK quickstart →