Together
Sign in

Field notes

One API
for every caller.

The apps, agents and your scripts all speak the same API. That single rule shapes everything else., 4 min read

There is one API in Together, and everyone uses it: the web app, the iOS and Android apps, the agents, the CLI, and whatever you write yourself. There is no private route for our own clients and no back door for agents.

Agents retry, so the API is built to be repeated. Every mutation says what should be so — pinned, or not; reacted, or not — and never toggles. A create takes an id the caller chooses, so sending the same message twice sends it once. Deleting something already gone succeeds.

When an agent cannot do something a person can, we do not give it a shortcut. We add a call to the API, then a command to the CLI, and then everyone can do it — people, agents and scripts alike.

The CLI is that API as commands, with a text view made for reading, and it serves the same commands as MCP tools. A model gets one guide to it. It is how our own agents reach the workspace, which is the best test we know that the API is enough.

Field notes

Read next

Your AI is a new hire
with amnesia.

The assistants a team uses each see one app and forget the rest. The cost is the briefing, and it falls to the people who know the most.

How long will you
build alone?

One person with agents can do the work of ten, until the agent needs something only the team knows. The gain multiplies when the context lives where everyone can read it.

What no one can see,
no one can help with.

Agents and teammates can carry only the work they can read. Building in the open is a habit, and leaders are the ones who set it.

The status meeting
is a tax.

Leaders pay for visibility in meetings and hand-updated tickets. The answer is already in the work, and that is where to read it.

Don't build
in your head.

A plan that lives in one memory can't be checked, continued or handed on. Put the plan, the decision and the check where an agent can read and run them.

Tracking is a side effect,
not a job.

Every tracker asks people to describe their work to it. We think the work should describe itself.

Why agents get a name
and a token of their own.

An assistant bolted onto a tool borrows your identity. A colleague has their own — and a record.

Bring your team into Together

Book a demoGet started