Developer quickstart

Build an applicant-controlled appeal workflow.

Use the same preparation and deadline workflow shown in the public demo, with a tenant-scoped key and deliberately deidentified decision-letter 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 for the public workflow, and never need an invitation for the API either.

Evaluating the product

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

Open public demo

Trying the API

Create your own seven-day key here. No invitation, no account, and no approval step.

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 the service mints a key scoped to it. Nothing to request, nothing to wait for.

No API key is loaded in this browser session.

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/cases" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "applicant_ref": "SUBJECT-101",
    "disaster_ref": "DR-101",
    "acknowledge_deidentified": true,
    "document": "DISASTER ASSISTANCE DETERMINATION - SYNTHETIC DEMONSTRATION\\nDate: August 5, 2026\\nDecision: Some requested assistance is not approved.\\nThe inspection did not show disaster-caused damage that made the home unsafe to occupy.\\nWe also need the insurance settlement or denial before we can consider uninsured losses.\\nYour appeal must be received by October 4, 2026."
  }'

The key is masked on screen so it cannot be read from a screenshot or a recording. Copy puts the real key on your clipboard; Run it here sends the request from this page using the key held in memory. Nothing is stored, and no case is created for anyone but 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, per-key throughput limits, and formal onboarding. This deployment caps issuance per address per day; that is a ceiling, not a full abuse-control stack.