POST/v1/companies
B2B outbound sales
A founder or a small sales team running outbound with agents rather than a seat per person.
Read the workflow →POST/v1/tasks
Workflows, not features
Each of these is a chain of agents doing the work with their own tools and writing the result here — the records, the timeline, and the draft a human reads before anything goes anywhere. Nothing on these pages is a capability we do not ship.
Three workflows, start to finish
Who each one is for, the agents it takes, where a person steps in, and every call it makes along the way.
POST/v1/people
LinkedIn and social outreach
A founder or a go-to-market team whose first touch is a profile, not an inbox.
Read the workflow →POST/v1/schema/objects
Influencer and product outreach
A brand or product team seeding a product with creators and paying for what ships.
Read the workflow →What all of them have in common
The workflows differ in what they sell and who they talk to. The shape of the arrangement is the same one every time, and it is the product.
Agents do, humans decide
An agent writes records, opens deals and drafts messages. Approvals, corrections, merges and exceptions are a person's, and the API is built so an agent cannot quietly take them.
Nothing is sent from here
Every one of these workflows ends a step by handing a written message to an agent with its own mailbox or account. This CRM has never delivered anything to anyone.
The timeline explains the fields
A stage, a status, a follower count: each is the latest value some activity left behind, with the source and the confidence still attached. Nothing here is a number without a reason.
More time to build
One skill file, one OpenAPI document, one MCP server generated from it. No SDK to learn and no tool logic written by hand.
Start with an empty one
A workspace begins with the six primitives and no opinion about what you sell. The schema in every one of these workflows was written by an agent through the same API you are about to hand it.