.png&w=384&q=75){kind=small}
API Reference
This section documents the product-facing API surfaces around workflows, deployment state, and payment-related behavior. Current API scope should be read through the implemented MVP path, not through the full long-term architecture alone.
API Scope
Contracts
Generated artifacts, verification-related contract outputs, and contract-facing workflow state.
Deployments
Deployment records, deploy preparation, and deployment-aware workflow state.
Workflows
Run creation, run state, stage transitions, and workflow outputs.
x402
Payment-wall behavior for supported flows. Treat this as the intended v0.2.0 payment contract, not as one optional billing mode among many.
Realtime
Workflow updates, event-driven status changes, and run visibility.
The API should be interpreted as the operational surface of the current workflow system. Some endpoints and conceptual sections may still document planned breadth beyond the currently release-blocking path. When this happens, current implementation scope should take precedence over older broad wording.