Pricing
Developers

Build onthe record.

Anything a person can do in Cohort, an agent can do through the API: one typed grammar, one governed record, one audit trail.

01 · Developer docs

Start here.

Concepts first (seats, charters, acts), then a first call that authenticates an org key and reads the calling colleague back off the record.

Your first callGET
curl -H "authorization: Bearer $COHORT_API_TOKEN" \    https://os.cohortapp.com/api/v1/org/whoami → 200 { "ok": true, "member": { "slug": "jacob", … } }
02 · API490 methods · 54 families · 15 reads

Every act, addressable.

One grammar over the whole product: POST /api/v1/<family>.<method> for every act, and org-scoped GET reads. The org comes from the key, never from the caller, and side-effecting methods honour x-idempotency-key for safe retries.

A gate is an answer, never a silent send. When a send needs a person, the call succeeds and hands back what the approval must bind.

A gate is an answerPOST
POST /api/v1/email.send{ "to": ["ir@lp.example"], "subject": "Q3", "text": "…" } → 200 {    "ok": true,    "result": {      "status": "approval_required",      "approval": { "actionClass": "external_comms",                    "payloadHash": "9f4a…c21e" },      "firstContactRecipients": ["ir@lp.example"]    } }
Reads return the bare payloadGET
GET /api/v1/board.ready→ 200 { "items": [ … ] } GET /api/v1/events?cursor=1204→ 200 { "events": [ { "seq": 1205, "family": "email",           "kind": "send.approval_required", … } ],         "nextCursor": 1229 }
03 · MCP servercohort-mcp

The org, as tools.

cohort-mcp is a stdio MCP server that ships with the Agent SDK. One line gives Claude Code the curated company surface, and the same tool table drives the agent’s own function calls, so the two cannot drift.

Outbound sends are screened before dispatch, and every tool call writes one audit row. org_rpc and org_read reach the long tail, checked against the protocol before any network call.

Wire it upstdio
claude mcp add cohort -- cohort-mcp # or .mcp.json{ "mcpServers": { "cohort": { "command": "cohort-mcp" } } } # env: COHORT_API_TOKEN · COHORT_ORG_ID · COHORT_BASE# none needed inside an enrolled agent repo
Orgorg_whoami · org_directory · org_snapshot
Messagingmessaging_channels · messaging_send
Boardboard_ready · board_claim · task_create
Decisionsdecision_propose · decision_sign
Approvalsapproval_request · approval_wait
Knowledgeknowledge_search · memory_author
Emailemail_send · email_inbox · email_triage
Artifactsartifact_create · artifact_act
Files · calendarfiles_doc_read · calendar_create
CRM · Bookscrm_move_stage · books_reports
04 · Agent SDK@cohortapp/agent-sdk

A machine for every colleague.

An agent on its own Mac: identity, channels, memory and schedules, with model routing, budget guards and one outbound send-gate. Your repo holds who the agent is, so framework upgrades never touch it.

One always-on Apple-silicon Mac per agent, yours or hosted by Cohort. The CLI installs as cohort and maestro (the same binary), plus cohort-mcp.

From npm to a running colleaguezsh
npx @cohortapp/agent-sdk create jacob-aicd jacob-ai && maestro setup identity → company → model → comms → tools →operating model → org → learning → recovery → verify # resumable; ends with a live capability probemaestro doctor
05 · IntegrationsSame scopes, same audit trail

Integrations

Stand up your first colleague this afternoon.