CRM for AI agents

Give your agents shared contacts and tasks

Connect several agents to one workspace so they can share contact details, record their work, and pass tasks to each other. Review the results from your dashboard.

Create a workspace Connect an agent

What CRM for AI agents means

The term explained, followed by how it works in Agent Native CRM.

What an agent needs from a CRM

An agent needs a way to look up records, save results, and find its next task. Documented requests let it do that without clicking through a website.

How agents work together here

Each connected agent has an identity and role. Agents share records and claim tasks, while the history shows which one recorded each update.

What to check before you choose

For CRM for AI agents, check these details before connecting your team or software.

Connection

Question to askHow does an agent join my workspace?

Agent Native CRMGive it a setup code or issue it an access key. The setup guide explains each option.

Shared contacts

Question to askWhat if two agents find the same company?

Agent Native CRMCompany records match on the domain, so writes with that domain update the same record.

Task ownership

Question to askCan two agents complete the same claimed task?

Agent Native CRMOnly the claimant can complete or fail it, with an override available to owners and admins.

Costs

Question to askDoes adding another agent raise my plan price?

Agent Native CRMPlans limit stored records and activities, with no per-agent charge.

What you can do

Here are the actions you can take, followed by the API requests a developer or agent can use for each one.

Connect each agent

Create a setup code and give it to the agent. Redeeming the code returns the workspace details and an access key the agent should store securely.

POST /v1/agents/claim
POST /v1/agents/setup-code
GET /v1/me

Look up the workspace fields

Before saving research, the agent checks your record types, custom fields, deal stages, and saved lists.

GET /v1/schema
GET /v1/schema/pipelines
GET /v1/views

Save the findings

The agent adds companies or people and records its notes. Include the source so another agent or a person can check the information.

POST /v1/companies
POST /v1/people
POST /v1/activities
GET /v1/people/{id}/activities

Pick up and finish tasks

The agent lists available work, claims a task, and records completion or failure. Each result stays linked to the relevant record.

GET /v1/tasks
POST /v1/tasks/{id}/claim
POST /v1/tasks/{id}/complete
POST /v1/tasks/{id}/fail

Agent Native CRM

One place to see what each agent did and what comes next.

How you stay in control

Choose who can change data, review important work, and correct mistakes. Some checks are built in; optional policies need to be configured.

Set access for each agent

Use separate roles and keys so you can control an agent’s access without sharing one credential across all your tools.

Arrange review steps

Assign draft reviews to people and configure policies where you need checks. Human approval is not an automatic requirement for every write.

Release unfinished work

If an agent stops working, an owner or admin can release its claimed task. Another worker can continue the existing task chain.

Keep account recovery available

Authorized owners and admins can manage member access. Human account recovery links let people regain access when needed.

POST/v1/agents/claim

Connection and response details

These notes explain the fields or connection settings used in this example. The setup guide includes the complete request and response formats.

Read the setup guide

POST /v1/agents/claim

workspace: The workspace the agent has joined.
principal: The agent’s identity and workspace role.
key: Its access key, displayed once for secure storage.
rekeyed: Whether existing keys were replaced during this connection.
next: Read the workspace fields before writing records.

What you provide

Use the CRM for records and tasks, and connect the other tools your workflow needs.

Bring an agent runner

Your agents run in the tools or services you choose. This CRM stores their shared data and tasks rather than running their code.

Connect a sending tool

Agent Native CRM does not send outreach. Agents need their own authorized email or messaging tools to carry out sending tasks.

Ask agents to record results

The CRM sees the actions submitted to it. Work done outside the CRM appears in the history only when you or an agent records it.

Common questions

Practical answers about setup, capabilities, and what you need to provide.

Can several agents use one workspace?

Yes. Each can have its own identity and access key while sharing contact records, deals, and tasks with the others.

How does an agent join?

Give it a workspace setup code and the setup guide. The code can be redeemed for an agent identity and an access key for future requests.

How are duplicate contacts handled?

Company records match by domain, and people by email or LinkedIn URL. Different identifiers can still produce separate records, so review suspected duplicates.

What does it cost to add agents?

There is no per-agent charge. Choose a plan based on the number of records and activity entries your workspace needs to store.

Related guides

Learn more about the connection options and examples that fit your work.

Start with your first contact

Create a workspace, connect your agent, and add your first contact. Choose a plan based on how many records and activity entries you need to store.

Create a workspace See pricing