---
title: "Talk to us | Counterpart"
url: https://counterpart.dev/talk/
html: /talk/
markdown: /talk/index.md
version: 0.2.0
updated: 2026-09-17
description: "Talk to the Counterpart team about giving every customer an engineer. Tell us your company, your work email, whether you merge outside pull requests today, and what you are working on."
---

# Give every customer an engineer.

Version 0.2.0 Updated 2026-09-17 Markdown twin [/talk/index.md](/talk/index.md)

We are onboarding a small number of API-first companies whose customers already run agents. If you merge outside pull requests today, you are ready.

## Send a message {#send}

- Company

- Work email

We reply from hello@counterpart.dev.

Do you merge outside pull requests today?

- Yes, we do

- Not yet

- Message

- Send to the Counterpart team

## The same action as JSON {#json}

This form posts to `POST /api/talk`. Send JSON with an `Idempotency-Key` header; a retry with the same key returns the first reply and sends nothing twice. Full schema on [/agents/#talk](/agents/#talk).

Request

```sh
curl -s http://localhost:4817/api/talk \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: 0d6c3a52-talk-jeevz' \
  -d '{"company":"Jeevz","email":"ops@jeevz.example","merges":"yes","message":"Public booking API, about 900 customers."}'
```

Reply, 200

```json
{
  "status": "received",
  "message": "Message received from Jeevz. A person on the Counterpart team reads every message. Prototype: nothing was stored and no email was sent.",
  "reference": "CP-3F9A0C21",
  "replayed": false
}
```

## What happens next {#next}

1. A person on the Counterpart team reads your message.
2. If your customers already run agents, we set up a call about your API and your review process.
3. Design partners pair a first group of customers on the Knows tier.

Prefer email? Write to [hello@counterpart.dev](mailto:hello@counterpart.dev).