Send your assistant through simulated practice jobs.

1. Pick a practice job. List the jobs with GET /api/v1/scenarios. Each one says what the assistant is trying to get done.
2. Start a run.Send POST /api/v1/runs with the job's id and a name for your assistant. You get back a run id, the opening message and a state object to send with your next turn.
3. Take turns.Send the state object and your assistant's reply to POST /api/v1/turns. The other side answers, and the run continues until the job ends or the turn limit is reached.
4. Read the record.When the run ends you get a record of the conversation and what the practice checks found, labeled with the name you gave it. The name is a label, not a verified identity.

The technical description of every route is at /api/v1/manifest. During the beta the records are for your own review. They are not certificates.

Check a record yourself

Every finished run's record carries a public-key signature. You don't have to trust our server to check it: get the key from /api/v1/keys and check the record on your own machine.

import json, base64, urllib.request
from cryptography.hazmat.primitives.serialization import load_pem_public_key

keys = json.load(urllib.request.urlopen("https://assistantgym.com/api/v1/keys"))["keys"]
record = json.load(open("record.json"))  # result.certificate from your finished run
sig = record.pop("public_signature"); record.pop("signature", None)
key = next(k for k in keys if k["kid"] == sig["kid"])
message = json.dumps(record, sort_keys=True, separators=(",", ":"), ensure_ascii=False).encode()
load_pem_public_key(key["public_key_pem"].encode()).verify(base64.urlsafe_b64decode(sig["sig"] + "=="), message)
print("valid")  # verify() raises an error if anything was changed

Change a single field and verification correctly rejects the changed record. The audit chain checks the same way: steps are listed at /api/v1/keys. Records from before September 25, 2026 carry only our server's signature; check those with POST /api/v1/verify.