Coworker API

Build agents on your company's context graph.

The Coworker API connects your context layer to your own agents and applications. Every call draws on permission-aware context graphs from 50+ of your tools, so agents are more accurate, reliable and cheaper to run.

Book a demoAPI docs, coming soon
POST /v1/tools/om2_search/call
curl https://open.coworker.ai/v1/tools/om2_search/call \
  -H "Authorization: Bearer $COWORKER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"arguments": {
        "query": "Acme renewal",
        "time_start": "last month"
      }}'
MCP format?format=openai?format=anthropic

Trusted by

/scaleHarriRapidSOSCortexharnessAllVoicesHuuuge GamesBlackthornAtmosphere TVColumnTalent SystemsSafetyWingpalmstreetUpboundTruecaller/scaleHarriRapidSOSCortexharnessAllVoicesHuuuge GamesBlackthornAtmosphere TVColumnTalent SystemsSafetyWingpalmstreetUpboundTruecaller

84.5%

better quality, preferred in blind review

64%

faster to complete a task

9x

cheaper per answer

Statistically significant benchmarks comparing Coworker MCP vs. 3rd-party MCPs in Claude

The problem

Your internal agents are only as reliable as the context they can reach.

Agents that guess

Without linked company facts, agents fill the gaps with assumptions. Reliability drops, so someone checks every step.

Agents that stall

Without context there's no real autonomy. An agent that can't see who owns what can't finish the job alone.

Context costs more than the model

Agents that can't find the right fact load whole threads and files into every prompt, and you pay on every call.

The solution · OM2

OM2 is the context graph behind every call.

OM2 links the facts across your company's tools, such as customers, projects, people and decisions, and keeps them current, traced to their source and scoped to each person's access. Agents stop guessing because every fact has a source. They stop stalling because they can see who owns what and what changed. And they stop paying to re-read whole threads, because they read the graph instead.

customer14s ago

Mosaic Financial

Series B fintech · $3.1M ARR · 47 seats

24linked
12sources
0.8ssynth
SOC 2 Type II auditPriya NambiarEnterprise onboardingCustomer Success#mosaic-impl
LiveOnboarding kickoff call with Priyavia Gong

Use cases

Built for the agents and apps you're already shipping.

Autonomous agents

Give agents built in LangGraph, CrewAI or any SDK the context a senior employee has. They act as their person, and nothing goes out without approval.

Your own enterprise AI app

Build a branded chat app or in-product assistant. Coworker handles retrieval, model choice and grounding, and threads sync to the Coworker app.

Enterprise search

Add search over your connected tools to your intranet or help desk. Results respect each person's permissions, and search is read-only by default.

Three ways to call Coworker

Bring your own agent, or use ours.

One API, three ways in. Pick the one that matches what you're building.

Your agent reasons

Call Coworker from your own agent.

Call any of the one-off agents in your Coworker workspace as a tool, or run a graph search over your company's context directly. Definitions come back in MCP, OpenAI or Anthropic format, so they drop into the SDK you already use.

  • GET /v1/tools?format=openai
  • POST /v1/tools/{name}/call
tools = requests.get(f"{BASE}/v1/tools",
    params={"format": "openai"}, headers=H).json()["data"]

resp = client.chat.completions.create(
    model="gpt-4.1", messages=messages, tools=tools)

for call in resp.choices[0].message.tool_calls:
    result = requests.post(
        f"{BASE}/v1/tools/{call.function.name}/call",
        headers=H,
        json={"arguments": json.loads(call.function.arguments)})

Security and governance

Your context and your stack stay yours.

Built for enterprises that want to own their AI stack: you keep the graph, choose the models and control who sees what, hosted by Coworker or in your own cloud.

  • SOC 2 Type II
  • AES-256 at rest
  • TLS 1.2+ in transit
  • No training on your data
  • Hosted in the US
  • Self-hosted deployment

Every agent sees exactly what its person can see.

Scoped keys

Eight scopes, none implied by another. A key does exactly what it was minted with.

Act on behalf of a member

Service keys name the member on every request, and acting for others needs an admin-created key.

Read-only by default

Without write scope, agents can search and read but are never offered a tool that changes anything.

Approval before action

Writes from an agent run land as drafts until the member approves them.

Audit sessions

Group related calls with a session id so every agent action is traceable.

Private by member

Conversations, runs and drafts are visible only to the member a request acts as.

Security and Trust

Compare

Three ways to give your agents a context graph.

FeatureCoworker APIData-platform context APIsBuild it yourself
Context graphBuilt and kept current for you: facts about people, deals, meetings, tickets, docs and code, linked across 50+ toolsMetadata and semantic layers over warehouse tables, curated by data stewardsYours to design, build and maintain: connectors, entity linking, freshness
Time to first answerAs soon as your network is set up and your tools are connectedWeeks of modeling and curationMonths of connectors and pipelines
PermissionsPer member, enforced on every callInherited from the data platformBuilt and maintained per agent
ActionsDrafts with approval, by API or in the appLimited or platform-specificCustom code
Model choiceAny model in your loop, or routed for youUsually the platform'sYours

Frequently asked questions

An API that lets your own agents and applications query a context graph. An agent asks a question or calls a tool and gets back linked company facts with their sources, limited to what the person it acts for is allowed to see. The Coworker API is Coworker's context graph API.

Give every agent the context your people have.

See the API on your own data in a 20-minute demo. From there, we'll get your network set up so your team can start building.