Documentation Index
Fetch the complete documentation index at: https://docs.zerct.com/llms.txt
Use this file to discover all available pages before exploring further.
Zerct support is API and CLI first. Agents should create tickets only after
they have collected the exact command, app id, build id, deploy id, and first
actionable log line.
Create a ticket
npx @zerct/zerct support create \
"Deploy failed" \
"The deploy failed after the Rust check step. The agent already ran doctor and reproduced the same error." \
--app app_1 \
--build job_1 \
--deploy deploy_1 \
--failing-command "npx @zerct/zerct deploy --wait --json" \
--first-log-line "cargo check failed in src/main.rs" \
--severity normal \
--json
agent_instruction, rate-limit state, and a next command.
List tickets
npx @zerct/zerct support list --json
Resolve tickets
When the agent fixes the issue or no longer needs Zerct support, resolve the
ticket from the CLI:
npx @zerct/zerct support resolve ticket_0123456789abcdef0123 --json
API
GET /v1/support/tickets
POST /v1/support/tickets
POST /v1/support/tickets/{ticket_id}/resolve
{
"subject": "Deploy failed",
"details": "What the agent already tried and why the issue needs Zerct support.",
"app_id": "app_1",
"build_id": "job_1",
"deploy_id": "deploy_1",
"failing_command": "npx @zerct/zerct deploy --wait --json",
"first_log_line": "cargo check failed in src/main.rs",
"severity": "normal"
}
low, normal, or urgent. Ticket creation is rate-limited per
account.
When payment is the fix
When a free-tier plan limit blocks work, agents should create a hosted Stripe
Checkout URL instead of opening the dashboard:
npx @zerct/zerct billing checkout "Project limit reached" --json
checkout.url to the human. Do not collect card details in
the app, CLI, or agent.