Troubleshooting
CLI or skill is missing
Section titled “CLI or skill is missing”Run npx --yes agent-data@latest init with your agent’s target flag, then restart the coding agent. Check agent-data --version and agent-data whoami. Follow any partial-installation error reported by setup.
Authentication fails
Section titled “Authentication fails”Run agent-data account. Check that the configured key belongs to the intended account and environment. For MCP, reconnect through your client’s authentication flow.
A call rejects its inputs
Section titled “A call rejects its inputs”Run agent-data docs <api-reference> and compare your route and parameters with its current contract. Preview the corrected request using call --dry-run.
Usage or spending limit reached
Section titled “Usage or spending limit reached”Inspect agent-data account and dashboard billing. Available credits and remaining credit-spend budget are separate requirements after included calls are used. See usage controls.
A build is still running or blocked
Section titled “A build is still running or blocked”Use agent-data parse status <job-id> and agent-data parse events <job-id> --follow. Follow the next action from status. Respond to a question using its interrupt ID; do not create repeated builds for the same source.
When continuation is available, run agent-data parse resume <job-id> to continue its saved checkpoint. If the job cannot resume, follow its reported blocker or contact the team with the job ID. See build progress.
If an extension submission times out, retry its saved, unchanged request. Keep the same request and endpoint IDs. Check extension status before assuming a timeout means the submission failed.
An API is degraded
Section titled “An API is degraded”Open its dashboard page to inspect the latest health status. If you need help, contact justin@agent-data.dev with the API identifier, job or request ID, and the error. Do not include API keys.