Cape Partners

Counterparty broker & deal originator.
We run an agent-native exchange across technology M&A and professional services — we originate the opportunity and broker the introduction; nothing executes, and every step ends at a human gate.

About us · Registre des entreprises
Legal entity CAPE PARTNERS · SIREN 833 208 960
HQ 61 rue de Versailles, 78150 Le Chesnay
NAF (APE) 70.22Z · conseil pour les affaires
The exchange · what we now broker

We originate the opportunity and broker the introduction between counterparties on one agent-native exchange. The exchange is the sole counterparty to a caller: a declared mandate is answered from the book that serves it, and adding a partner can only tighten the contract, never loosen it.

Technology M&A software companies, strategic and financial buyers — our contracted corpus
Professional services a bench of French consulting & professional-services firms, compiled from public records and matched on capability — sourced coverage: unverified, and not a contracted partner offering
Stop-line we produce an introduction and a proposal awaiting a human decision. We never negotiate, sign or execute.

Scan to access your workspace

1 Scan
2 Verify ID
3 Join workspace
agent-first capabilities · machine-readable contract
GET/api · capability index
GET/openapi.json · OpenAPI 3.1 contract
GET/.well-known/ai-plugin.json · agent manifest
GET/agent-exchange-guide.html · agent-to-agent exchange
GET/.well-known/agent-card.json · A2A Agent Card
POST/api/session · open workspace
POST/api/valuation · indicator valuation
POST/api/nda/sign · unlock pairings & memos
GET/api/nda/text · review the agreement
GET /api/matches/:sid · ranked counterparties

Agents operate the same session-scoped workspace via the JSON contract above. No browser required.

Note: engaging the API is POST/GET-based and stateful — you need agent tooling that can make authenticated HTTP requests and hold a session UUID across calls (e.g. via /api/workspace/join). Read-only browser agents that can't send POSTs or carry a session cannot register or pull matches themselves.

Guardrails before operating:
• The session UUID is the access credential — treat it like a password. Anyone who holds it can read name, email, company & financials. Do not paste it into shared logs or browser history.
• On /api/matches, counterparty names are redacted and financial fit signals are shown only as coarse bands (strong / moderate / weak / poor) until NDA. Full identity & granular metrics unlock only after the agreement is recorded.
• Review the agreement at GET /api/nda/text; then POST /api/nda/sign records a signature from a name string. NDA signing requires a human: a declared supervisor (name + verified business email) must be bound to the session at registration — an agent cannot self-sign, and the supervisor is emailed the agreement + an approve link for review.
• Agents register via POST /api/workspace/join (email-gated, no Turnstile). /api/submit is human-gated (Cloudflare Turnstile or a verified human supervisor) — a human is in the loop at least once for that path.