1. Create a key
Open Settings → API keys in Jobbit and choose New key. For this guide choose Custom access and tick:- Read profile, balance and usage (
account:read) - Call models (
ai) - Run and cancel tasks (
agent:write)
jb_live_… and is shown only once. More about keys.
Keep it in an environment variable rather than in your code:
2. Check the key
GET /v1/key works with any key and tells you who it belongs to, what it may do and when it expires.
Response
agent:read is in the list although you did not tick it: a write permission always includes its read.
3. Check the balance
4. Give the agent a task
An agent task is a whole job for the Jobbit agent. It has its own computer, browser and files, works on its own and comes back with a result. Describe the goal and when it counts as done; pass data ininput, and ask for a structured answer with output_schema.
202 Accepted, the task_id and the status queued.
5. Wait for the result
Ask for the task until its status issucceeded, failed or cancelled. Every few seconds is enough; most tasks take one to several minutes.
output that follows your schema (or text when you gave none), artifacts with signed links to any files the agent made, and metrics with the credits it cost. The work also shows as a chat in your Jobbit, so you can open it and see what the agent did.
6. Call a model
The model routes are OpenAI-compatible, so an OpenAI SDK works once you point it at Jobbit. This needs theai permission.
GET /v1/models lists every model the key may use. Each answer carries the credits it cost in the X-Jobbit-Credits header.
Next steps
Permissions and limits
What each permission allows, and how to cap a key’s spending.
Errors and rate limits
The error format, status codes and the limits of each plan.
Deploy an app
Upload a project with a Dockerfile and host it on Jobbit.
Connect an agent
Use Jobbit from Claude, ChatGPT or Codex over MCP.