Developer quickstart

Build on the stewardship evidence layer.

Use the same bounded evidence workflow shown in the public demo, with a tenant-scoped key and deliberately deidentified microbiology text.

Create a temporary key Browse API docs Try the public demo without a key

Checking issuance status 168 hour lifetime One project scope Tenant-isolated

Choose your path

Start with the access you already have.

Judges never need credentials. API keys are only for invited integrations.

Evaluating the product

Run the complete synthetic workflow with no account, invitation, or API key.

Open public demo

Trying it with your own data

Mint a seven-day key here, no invitation needed, and send your own deidentified reports.

Generate a key

Already have a key

Load it into this page session, verify the connection, then use the documented endpoint.

Verify an existing key

Step 1 of 3

Create a temporary key

Name a workspace and press the button. The key is shown once, scoped to that workspace alone, and expires in seven days.

No API key is loaded in this browser session.

Access and safety

Open to try, bounded by design

Anyone can mint one: No invitation, no account. The key is yours, scoped to the workspace you name here.
API key: Authenticates requests, determines the tenant and scope, expires automatically, and can be revoked.

Product boundary

This API supports stewardship evidence only. It rejects detected identifiers, suppresses antibiogram cells below 30 isolates, persists no raw report text, and takes no clinical action.

Only a SHA-256 key digest is persisted.
The key expires automatically after seven days.
No credential is placed in browser storage.
Reading a report is the one call that invokes a model, capped at 25 per key per day.
Key creation is capped per address per day, so an open form cannot be farmed.
The public judge workflow needs no key at all.

Step 2 of 3

Load and verify the key

Generated keys are loaded automatically. Existing key holders can paste one here. It remains only in page memory.

No API key is loaded in this browser session.

API key for this browser session

Revocation is permanent. Clearing removes the value only from this page session.

curl -H "X-API-Key: YOUR_API_KEY" "SERVICE_URL/v1"

Step 3 of 3

Call the project workflow

The example follows this project's real input contract and safety boundary.

curl -X POST "SERVICE_URL/v1/intake" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"subject_ref":"SUBJECT-101","acknowledge_deidentified":true,"document":"CULTURE AND SUSCEPTIBILITY REPORT\\nOrganism: Escherichia coli\\nSpecimen: Urine\\nCEFTRIAXONE <=1 S\\nCIPROFLOXACIN >2 R"}'

Run it here, with the key you made

This is the text that gets sent. Edit it, or paste a report of your own, then press send. Every value that comes back quotes the line it was read from, so you can check the answer against what you typed.

Report to send

Load a key above first.

Synthetic or deliberately deidentified text only. Real patient records do not belong in a public beta, and the service is built to refuse them rather than to trust you.

Interactive reference

Use the API docs without guessing.

Open the schema, select Authorize, paste the API key, then expand an endpoint to see its exact request and response model.

Open API docs Read provisioning guide Return to public demo

AuthorizePaste the temporary API key into the X-API-Key field.
InspectReview required fields and safety acknowledgements before executing.
ExecuteStart with GET /v1, then call the project-specific workflow.

Keep the key private

Do not place it in frontend source, Git, screenshots, videos, or public posts. Clear it from this page when finished.

Need operator-managed access?

The repository provisioning guide covers hash-only Secret Manager keys, rotation, and revocation.

Before broader rollout

Add API Gateway quotas, rate limits, abuse controls, and formal onboarding. The current deployment is an invited beta.