FAQ

Sealed recipes vs projects?

Sealed recipes — use when Computalot provides the runtime you need (AMM evaluation, packing, LightGBM, Echidna, etc.). No project setup. Just send a typed payload.

Projects — use when you need to run your own code. Create a project, push a tarball, and submit jobs with runner_command.

See Sealed Recipes and Projects.

How do I give my agent access?

Tell your agent to install the Computalot skill from https://computalot.com/skill.md, or have it read https://computalot.com/llms.txt. See Agent Integration.

Debugging failed jobs

Check the job: GET /api/v1/jobs/:id — look at error and recommended_action
Check tasks: GET /api/v1/jobs/:id/tasks — per-task error, output, exit_code, latest_progress
Check project: GET /api/v1/projects/:name/status
Check billing truth: GET /api/v1/account/balance, GET /api/v1/account/holds, GET /api/v1/account/ledger, and GET /api/v1/account/quotes

Symptom	Likely cause	Fix
`402 Payment Required`	Insufficient credits	Fund your account via x402 or the returned shortfall quote, then retry the same blocked request
Project init rejected	Balance below $5	Top up, then retry `POST /api/v1/projects/:name/init`
Tasks stuck in `queued`	Cold start or capacity catch-up	Check project status and job diagnostics; the first job can wait while runtime preparation happens on demand
Tasks fail immediately	Dockerfile missing deps or runtime issue	Fix Dockerfile or manifest, push a new revision, then retry with a small smoke job or optional `/init`
Useless error message	Truncated output	Check per-task `output` field (full 10KB)
Recipe payload rejected	Schema mismatch	`GET /api/v1/recipes/:name` to check schema

Poll for job completion


while true; do
  STATUS=$(curl -sS -H "Authorization: Bearer $TOKEN" \
    https://computalot.com/api/v1/jobs/<job_id> \
    | python3 -c "import sys,json; print(json.load(sys.stdin)['status'])")
  case $STATUS in
    completed|partial|failed|cancelled) break ;;
  esac
  sleep 5
done

Cancel a job


curl -sS -X PUT -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  https://computalot.com/api/v1/jobs/<job_id>/cancel \
  -d '{"reason":"no longer needed"}'

How long are results kept?

Terminal jobs and their results are queryable for 30 days. Artifacts are retained for 7 days.

What languages are supported?

For sealed recipes: you don’t need to write code — just send payloads.

For projects: Python, Node.js, Deno, Bun, Ruby, Julia, R, Rust (cargo), and any language you install in your Dockerfile. Shell scripts as the direct entry point are blocked — use a supported language wrapper.