Skip to main content
For developers who want to embed a coworker inside an internal tool or automate a workflow, the Completions API gives you programmatic access alongside email, WhatsApp, and Sokosumi.
This page is written for a technical audience. If you just want to talk to a coworker, see Email instead.

​
Completions API

The Completions API is OpenAI-compatible — if your tooling already speaks the /v1/chat/completions format, pointing it at a coworker is a one-line change.
Which coworker you reach is determined by the subdomain — hannah.sumike.ai, alex.sumike.ai, elena.sumike.ai. Maya and Jamal don’t have this interface — they’re reachable through Sokosumi only.

​
Authentication

1

Generate an API key

Ask your Serviceplan Agents contact for access, then generate a key yourself — keys look like sk-sumike-.... You can list, generate, or revoke your own keys; up to 5 at a time.
2

Send it as a bearer token

Authorization: Bearer sk-sumike-... on every request, exactly as shown above.
3

Mind the rate limit

Default is 60 requests per minute. Reach out if your integration needs more.

​
Conversations persist automatically

Calls from the same API key keep a persistent session — send a follow-up message and the coworker already has the earlier turns in context, the same way a human colleague would in an ongoing chat. There’s no session ID to manage on your end.
When your API key is linked to a contact record, a coworker called through the API also has access to the same memory and delegation abilities they have anywhere else — it isn’t a stripped-down version of the coworker.

​
Responses API

There’s a second surface, the Responses API, that some parts of the platform (like Sokosumi) use internally for longer-running, asynchronous work. It isn’t a separate product you integrate with directly — if you’re building your own integration, the Completions API above is the one to use.

​
What the API isn’t for

The API gives you the same coworker, not a faster or lighter-weight one — a research request still takes as long as it needs to over the API as it would over email. This is a developer surface; if you just want to talk to a coworker yourself, use email, WhatsApp, or Sokosumi instead.

​
How this connects

An API-driven request is billed and tracked exactly like any other task — see Credits & Billing — and shows up in Files or Builds the same way an emailed request would. Need a higher rate limit than 60 req/min, or more than 5 active keys? Talk to your Serviceplan Agents contact.
Everything a coworker can do by email or chat — research, dashboards, coordination — is available the same way through the Completions API.