Skip to main content
The API origin is https://api.argalabs.com. The dashboard calls this module Training at /training; its backend routes retain /datasets. Use the Python SDK or TypeScript SDK for typed helpers and customer-side tracing to construct evidence. Selection and filtering must happen before upload. Server validation does not replace your organization’s text-filtering policy.

Authentication

Send Authorization: Bearer <credential>. Full Arga credentials can manage Training. Source-bound upload keys, prefixed arga_trace_, can call only POST /datasets/evidence for their assigned source. The key response contains key, source, expires_at and scope. Treat key as a secret. Upload keys expire after 30 days. Account legacy-key rotation or session revocation invalidates them; individual revocation is not implemented in v1.

Upload evidence

The v1 contract allows selected Gmail/Stripe records, aliased identifiers, an optional selected goal, selected policies and coverage metadata. Structured identities must use the contract’s alias formats; unsupported fields and formats are rejected. Free text still requires your local privacy policy. Generate the exact schema from the Python SDK, or import evidenceSchema from arga-sdk/tracing in TypeScript:
Runtime validation additionally requires contiguous event sequence numbers. Limits are 100,000 bytes, 100 events and 50 records per event. Accepted evidence is immutable and deduplicates per owner by content. A successful upload returns HTTP 201 with the collection metadata and: Accepted incomplete evidence can be inspected even when generation is blocked.

Collections and tasks

All routes below require a full Arga credential and are owner-scoped. Task responses include id, trace_id, status, revision, spec, review history and optional scenario_id. spec includes starting state, provenance, assumptions, rules and the compiled grader. Repeated generation for the same trace and variation returns the existing task.

Review and evidence requirements

Approval requires decision="approved", acknowledge_assumptions=true and acknowledge_grader=true for the current revision. It saves the starting state as a reusable Scenario. Editing makes the task a draft again. Use the returned revision after edits or verifier rebuilds. A grader test requires normalized before/after collections with complete: true and stable records matching the task’s rules. Missing or incomplete evidence is an error, not a passing check. The illustrative example from the grader endpoint is not captured state. See the snapshot contract. Export requires at least one approved task and includes approved tasks only. Environment preparation requires the current task’s approved, unchanged Scenario. Neither operation executes your agent or trains a model.

Status codes

Rejected /datasets/evidence payloads return content-free validation errors. Keep provider exception bodies and raw source data out of your application logs.