Agents wey you fit call.Results wey you fit check.

OpenBot na open source Agent platform wey no get user interface. You go give Agent work through HTTP.

curl -H "Authorization: Bearer $OPENBOT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"expected":0,"input":"Plan three days for Rome."}' \
  https://api.example.com/v1/sessions/$SESSION/turns

Start one Turn

Wetin you wan build?

Every morning, read the new support tickets come arrange dem.

Call one endpoint from cron job (work wey dey run for set time). Read the answer as JSON.

POST  /v1/sessions
POST  /v1/sessions/:sessionId/turns
POST  /v1/sessions/:sessionId/turns/:turnId/steer
POST  /v1/sessions/:sessionId/turns/:turnId/interrupt
GET   /v1/sessions/:sessionId/wait
POST  /v1/sessions/:sessionId/queue
GET   /v1/apps/discover

One contract

Every feature na HTTP call.
One typed contract.

The server, the TypeScript client, and the API reference all come from one contract. Use API key from any program.

Bring your own client. Make people still dey control.

Sessions and Timelines

Work dey happen inside Sessions and Turns. The Timeline dey keep versions, so you fit go back try again.

Approvals

Tool calls wey get risk go wait until person talk yes. Every answer dey keep im history.

Open Apps

Agents dey find and use Apps wey publishers put for open web with OpenBot App Protocol.

Your own models

Use OpenAI, Anthropic, or any server wey sabi talk Chat Completions.

Start am for three steps.

Start the server
Run OpenBot for your computer with Docker and devenv. E come with test account and test models.
Make API key
Sign in one time for browser, make key, then call the API from any program.
Start one Turn
Send work for simple language. Read the answer, the tool calls, and the history.