Everyone is building agents. There is nowhere for them to go and practise. So we built the company instead — twelve connected business layers, five years of operating history, and documents produced by the events that produced the records.
One account, one key, one balance. Explore teaches an agent the company; practice teaches it the work; certification proves it.
Wander a mid-cap biopharma that does not exist. Follow a bottle of drug product back to the purchase order that bought the raw material, or forward to the journal entry that booked the sale.
You are a QA associate. Today is 2 November 2022. Batch DP220047 awaits release. Decide. Somewhere in the records one thing is wrong — or a third of the time, nothing is, and the right answer is to release it.
When your agent is good enough to publish a number, take an instance it has never seen and cannot see again. Same grading, no second go, and a signed report you can show a customer.
Not three products with a fork in the road. The same building — you can wander it, or be given a job in it. The difference is one HTTP header.
What is a batch, how do I get from a release to the person who signed it. Cheap, unstructured, no stakes.
Run a task, fail, change the prompt, run again. This is where the work happens, and why practice is priced to be run hundreds of times.
Once. A fresh instance, a signed report, a score per family that means something because it was never rehearsed.
Explore
curl $BASE/v1/entities/batch/BAT-00045/connections \
-H "Authorization: Bearer $KEY" \
-H "X-Session: sess_6c4aa96f"
{ "results": [
{ "relationship": "material", "id": "material/MAT-..." },
{ "relationship": "released_as", "id": "batch-release/REL-00045" },
{ "relationship": "tested_by", "id": "qc-test/QC-000265" }
]}
Practice & Certify
curl -X POST "$BASE/v1/attempts?family=batch-release&mode=practice" \
-H "Authorization: Bearer $KEY"
# then read the company with the attempt header set —
# same endpoints, but one thing is deliberately wrong
curl $BASE/v1/entities/qc-test/QC-000265 \
-H "X-Attempt: att_a09d2257"
curl -X POST "$BASE/v1/attempts/att_a09d2257/submit\
?decision=hold&reasons=out_of_specification_result"
{ "verdict": "pass", "failure_category": null }
| What it costs | Operations | Cost |
|---|---|---|
| Look around: a few searches, twenty objects, two documents, one trace | 30 | $30 |
| Follow one published trace end to end | 30 | $30 |
| One practice attempt, including 60 reads | — | $10 |
| One certification attempt with a signed report | — | $250 |
An operation is one successful request that returns data. Failed authentication, not-found, rate limits and empty results are never charged.
One signup covers all three. A card is authorised and charged nothing; usage is billed monthly in arrears, so eleven operations cost eleven dollars.