API Path
If you are integrating Agirunner into another system, start with the platform API rather than with runtime internals.
That is an important product boundary. The platform API is the durable control-plane surface for workflows, tasks, workspaces, artifacts, logs, integrations, and runtime-facing management. The runtime is the execution system behind that control plane, not the primary public entry point for most integrators.
First Integration Flow
Section titled “First Integration Flow”- authenticate with an API key or login token
- discover the workflow and playbook surfaces you need
- create or launch work
- inspect progress through workflow, task, log, and artifact endpoints
Start With These Areas
Section titled “Start With These Areas”When To Use The Dashboard Anyway
Section titled “When To Use The Dashboard Anyway”Even API-first adopters should spend a little time in the dashboard. The UI is the easiest place to understand the workflow model, the operator review surfaces, and the kinds of records the API is exposing.
Important Boundary
Section titled “Important Boundary”The platform API is the public control-plane surface. Integrators generally talk to the platform, not directly to runtime internals.