Use the verification API during approved integration work.
This page is intentionally limited. Approved integrators receive endpoint, interface, verifier, and sandbox material through the appropriate review channel. Integrations connect existing automation and event systems to the release boundary. They do not replace the systems that schedule, route, or stream work.
Integration contract
Review channel
Gateway hostnames, request formats, response fields, sandbox credentials, and verifier material are provided through approved integration review.
TaskHawk integration work is scoped to release checks, release-token verification, and evidence output. Workflow orchestration, event streaming, and model execution remain in the customer's existing environment.
Public documentation intentionally describes the integration boundary without publishing field-level request or response examples.
Reference
| Primary surface | REST verification request with signed release-token response. |
|---|---|
| Additional protocols | Reviewed through controlled integration channels. Use only the live gateway material issued for your account. |
| Delegation/Budget | The public draft-02 reference covers request-bound delegation patterns for budgeted software action. Use the Datatracker record and account-issued integration notes as the review sources. |
| x402 gateway composition | Authority before x402 settlement describes the pre-payment authority layer for x402-paid APIs, datasets, and MCP tool calls. |
| Decision classes | ALLOW · CONSTRAIN · DENY |
| Authentication | X-API-Key header unless your account documentation states otherwise. |
| Formal verification | Public repository: taskhawk-systems/kevros-formal-verification |
| Integration review | integrations@taskhawktech.com |