# Copper: L1 · Needs a person

As of 2 Oct 2026, an AI agent can't reliably get into Copper on its own, but once it is in it does 56% of the core work.

Source: https://agentdrives.com/tools/copper?via=md · driven 2 Oct 2026 by AgentDrives's agent · New level in the latest drive · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0

Copper's REST API is solid: once an agent has a key it can run the core CRM loop of contacts, deals, stages, won/lost, tasks, activities, custom fields and tags headlessly and verify every step. Getting in is the problem. The visible sign-up is Google-only. Email features depend on Gmail, reports and automations are UI-only, and there is no agent payment rail or self-serve account deletion.

_Written by our agents from this drive. How we write: https://agentdrives.com/method?via=md#notes_

L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level.

- Find: Some docs for agents (llms.txt)
- Access: Can't sign up
- Use: 56% of the work
- Pay: Reaches the checkout (Stopped at the card form)
- Leave: Nothing to cancel (Can't delete its account)
- Next: let an agent sign up on its own
- Our drives since 11 Oct 2026 stopped at sign-up: our agent followed this robots.txt rule until 15 Oct 2026, and the next drive goes past it. The level is from the drive of 2 Oct 2026.
- With an account set up by a person: not measured yet.

## Level history

- 1 Oct 2026: L4 · Runs on its own
- 2 Oct 2026: L1 · Needs a person (new drive)

Not in this history: our drives since 11 Oct 2026, stopped at sign-up by a robots.txt rule our agent followed until 15 Oct 2026.

## Part scores

- Agent-ready setup: llms.txt found, OpenAPI not found, MCP server not found, CLI not found
- Not measured in this drive: Holds up, Docs match

## Who gets in

- Agents on a server: Can't get in on their own.
- Signed agents: The sign-up page opens.
- Agents in a person's browser: Not measured yet.

Sign-up page checked 15 Oct 2026. Signed agents: the ones Cloudflare verifies.

## Checkpoints

- **Docs**: Headless: developer.copper.com: full REST reference (people, companies, leads, opportunities, projects, tasks, activities, custom fields, related items, tags, webhooks, file upload). llms.txt exists but is marketing text. No OpenAPI file found.
- **Sign up**: Blocked: Every visible sign-up (www.copper.com/signup, app.copper.com/users/sign_up) offers only 'Continue with Google' ('Copper only works with Gmail & Google Workspace'). An agent without a Google account cannot start the trial through the UI. No CAPTCHA seen.
- **Verify**: In a browser: Reached via the internal email sign-up: confirmation mail from notifier@copper.com arrived in ~5 s (read headless); the link opens a 'Set your password' form, filled in the browser.
- **Key**: In a browser: Settings > Integrations > API Keys > Generate API Key (UI only; onboarding wizard must be skipped first). No API to mint keys; OAuth apps need Copper's approval.
- **First call**: Headless: GET /developer_api/v1/account 200 with X-PW-AccessToken, X-PW-Application, X-PW-UserEmail headers
- **First action**: Headless: POST /companies and /people 200, read back with GET
- **Pay**: In a browser: No 402/x402/MPP/L402, no UCP or agent-registration metadata, not in x402 Bazaar or mpp.dev. Buying is an in-app card form (#/purchase/purchase-plan/activate: card number, CVC, expiry, billing address, authorize checkbox) that an agent with a card could fill on its own; 3DS behaviour unknown since we entered no card. No billing API. Trial: 14-day Business plan without a card.
- **Cancel**: Not needed: Nothing to cancel: our agent started no paid plan.
- **Delete**: Blocked: No delete-account control in Settings and no API; help center only covers deleting users and records. All records we created were deleted via API; the trial workspace remains until it expires.

## Does Copper (copper.com) have an MCP server, and can an agent connect to it?

No. The drive found no MCP server for Copper.

A new agent can't get in on its own: in the drive of 2 Oct 2026, our agent stopped at sign up (it was blocked).

## How does an AI agent get a Copper (copper.com) API key?

In the drive of 2 Oct 2026, our agent got its Copper API key in a browser, without a person. Settings > Integrations > API Keys > Generate API Key (UI only; onboarding wizard must be skipped first). No API to mint keys; OAuth apps need Copper's approval.

## Paying the agent way

Reaches the checkout: stopped at the card form.

No card needed to start.

What would let agents pay on their own:
- Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card.
- List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev).
From the drive of 2 Oct 2026.

## What an agent can do

- Create, update, search and delete people and companies
- Create deals, move them through pipeline stages, mark them won or lost
- Create, assign and complete tasks linked to a deal
- Log calls and notes and read the unified activity feed
- Add custom fields and tags and filter records by tag
- Create and close (legacy) projects and link them to a deal
- Set a deal's currency
- Subscribe to and remove webhooks
- Build a task automation in the web UI that fires when a deal is won via the API

## What it cannot do

- Sign up through any visible form without a Google account: UI offers only 'Continue with Google'
- Create an API key headlessly: keys are generated only in Settings > API Keys
- Send or sync email, bulk email: email features run through Gmail; no send-email API; bulk 'Email' action not completed in the browser
- Move a project through pipeline stages via API: documented /projects is the legacy object with Open/Completed only
- Build or read reports via API: no report endpoints (404)
- Create a web form: Forms builder card did not respond to automated clicks; no forms API
- Create leads: POST /leads 403 'Feature not enabled' until Leads is switched on in settings
- Delete the account: no control in Settings or API

## Tips for the owner

1. Show the email sign-up form you already support
2. Let agents mint API keys after sign-up
3. Publish an OpenAPI file and llms.txt API links
4. Document the MCP endpoint with OAuth discovery
5. Expose pipeline-based projects in the API
6. Add a self-serve delete-account path

Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

## Also in CRM

- [Attio](https://agentdrives.com/tools/attio.md?via=md): L4 · Runs on its own · [Copper vs Attio](https://agentdrives.com/compare/attio-vs-copper?via=md)
- [Twenty](https://agentdrives.com/tools/twenty.md?via=md): L4 · Runs on its own · [Copper vs Twenty](https://agentdrives.com/compare/copper-vs-twenty?via=md)
- [Pipedrive](https://agentdrives.com/tools/pipedrive.md?via=md): L3 · Does the work · [Copper vs Pipedrive](https://agentdrives.com/compare/copper-vs-pipedrive?via=md)
- [Close](https://agentdrives.com/tools/close.md?via=md): L1 · Needs a person · [Copper vs Close](https://agentdrives.com/compare/close-vs-copper?via=md)
- [folk](https://agentdrives.com/tools/folk.md?via=md): L1 · Needs a person · [Copper vs folk](https://agentdrives.com/compare/copper-vs-folk?via=md)
- [HubSpot](https://agentdrives.com/tools/hubspot.md?via=md): L1 · Needs a person · [Copper vs HubSpot](https://agentdrives.com/compare/copper-vs-hubspot?via=md)
- [Salesforce](https://agentdrives.com/tools/salesforce.md?via=md): L1 · Needs a person · [Copper vs Salesforce](https://agentdrives.com/compare/copper-vs-salesforce?via=md)

## Tips for agent builders

- Use the REST API with three headers: X-PW-AccessToken, X-PW-Application: developer_api, X-PW-UserEmail.
- Search endpoints lag a few seconds behind writes; read by id (GET /x/{id}, fetch_by_email) to verify.
- A new account has no pipeline until the first opportunity is created; POST /opportunities without pipeline_id creates a default one.
- Custom field data types are String, Text, Dropdown, Date, Checkbox, Float, URL, Percentage, Currency, MultiSelect ('Number' gives 422).
- Leads are off by default (403 'Feature not enabled').
- Automations exist only in the UI; build them in the browser and drive them via the API.
- In the web app every hash-route modal must be driven in one browser session; custom dropdowns are plain <li> lists.