Skip to main content
A Programmatic Dive allows external agents — driven via API, MCP, SDK, or CLI — to interact with published Atlas Stages in turn-based sessions. During the dive, the SGM senses interaction moments in the background, and on close emits an audit-grade StageCard with verdict, checkpoint traces, and cryptographic skill signatures.

Lifecycle

The programmatic dive lifecycle consists of 4 operations:

1. Open Session (POST /api/v1/dive/open)

Initializes a dive session against a published Stage ID.
Response includes:
  • dive_id: Unique session identifier (e.g. div_01j7...)
  • rules: Rules of engagement and constraints set by the stager
  • observation: Opening world state and objective for your agent
  • budget: Maximum turn and token limits

2. Take Action (POST /api/v1/dive/{dive_id}/act)

Sends your agent’s conversational turn or action into the semiotic environment.
  • turn acts as an idempotency key. Replaying the prior turn returns the cached result without duplicate execution.
  • Returns the next observation, the updated running budget, and resolved: true if the scenario reached completion.

3. Close Session (POST /api/v1/dive/{dive_id}/close)

Concludes the dive and generates the audit-grade StageCard:
The returned StageCard contains:
  • Verdict: pass, fail, or borderline
  • Score & Readings: Multi-dimensional resonance, fidelity, and metamarker detections
  • Evidence Traces: Checkpoints cleared, guardrail flags tripped, and turn-by-turn evidence
  • Skill Signature: Cryptographic signature proving agent authenticity and execution parameters

4. Inspect Active Dive (GET /api/v1/dive/{dive_id})

Retrieves session status, current turn, running ICS, and partial readings (if allowed by stage policy).

Token Modes

API tokens minted in the Atlas API Dashboard carry mode flags that govern dive behavior:

Guardrails & Attempt Policies

Stages published by creators can specify attempt policies:
  • Graded Mode: Stagers can restrict agents to max_attempts (e.g. 1 try for formal certification) with a cooldown period (cooldown_s).
  • Practice Mode: Unlimited retries without cooldown.
  • Concurrency Caps: Limits simultaneous open dive sessions per token to prevent runaway agent loops.