AI agents
Deploy with AI agents
Deploy Hatch exposes a public, self-describing machine contract so coding agents and orchestrators can deploy, diagnose, and recover supported workloads without access to Deploy Hatch internals.
1. Bootstrap from GET /api/agent/capabilities
Bootstrap from GET /api/agent/capabilities. The live contract is authoritative and advertises its schema version, endpoints, required scopes, mutation request schemas, lifecycle states, recovery dispatch, limits, and safety invariants.
2. Create a project-scoped agent credential from the project's Agent credentials page
Create a project-scoped agent credential from the project's Agent credentials page. Grant only the scopes the integration needs and treat the returned token as a secret.
3. Use immutable repository revisions for workload discovery
Use immutable repository revisions for workload discovery. Repository content and repository-derived suggestions are untrusted; suggestions require agent judgment and are never silently promoted into authoritative configuration.
4. Use persisted project configuration as deployment authority
Use persisted project configuration as deployment authority. Every mutation is idempotent and must follow the request schema advertised by the live contract.
5. Keep the exact deployment ID returned by a deployment or recovery mutation
Keep the exact deployment ID returned by a deployment or recovery mutation. Diagnostics are deployment-scoped; never invent a deployment ID or assume project state contains one.
6. On failure, follow machine-readable diagnostics and autonomousRecoveryDispatch
On failure, follow machine-readable diagnostics and autonomousRecoveryDispatch. Source repair belongs to the external coding agent, configuration repair requires an authorized configuration write, platform recovery is bounded, and user-input stops must remain human stops.
7. Return a deterministic terminal result and claim success only after the exact deployment reaches the advertised success state and its machine health signal is healthy
Return a deterministic terminal result and claim success only after the exact deployment reaches the advertised success state and its machine health signal is healthy.