How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Cape Partners Exchange API

The Exchange API from Cape Partners — 11 operation(s) for exchange.

Cape Partners Exchange API is one of 16 APIs that Cape Partners publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Exchange. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 11 operations across 11 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 3 base URLs: https://www.capepartners.fr, https://sniffer.capepartners.fr, http://localhost:3000.

11 operations 11 paths 6 schemas 6 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://sniffer.capepartners.fr
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Cape Partners Exchange API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Session-Id (SessionToken). An API key is passed in the header as X-Nda-Signed (NdaSigned).

  • SessionToken — The workspace session UUID is a capability token carried in the URL PATH (not this header — shown here only because OpenAPI securitySchemes cannot model a path…
  • NdaSigned — Precondition (not a literal header): a server-side NDA signature for {sessionid} must be recorded in the ndasignatures table via POST /api/nda/sign before NDA-…

Paths & Operations 11

Across 11 paths, the API surfaces 11 operations — 6 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Exchange 11
GET
/.well-known/agent-card.json
Agent Card in the A2A v1.0 shape, served at the standard well-known URI (RFC…
getWellKnownAgentCardJson → 200
POST
/a2a
A2A protocol v1.0 — the JSON-RPC 2.0 binding (one endpoint, operation names as…
postA2a body → 200400
POST
/a2a/message:send
A2A protocol v1.0 — HTTP+JSON binding for SendMessage.
postA2aMessage:send body → 200
GET
/a2a/tasks
A2A protocol v1.0 — HTTP+JSON binding for ListTasks.
getA2aTasks 7 params → 200
GET
/a2a/tasks/{id}
A2A protocol v1.0 — HTTP+JSON binding for GetTask.
getA2aTasksById 3 params → 200404
GET
/api/exchange/spec
Machine-readable form of the agent-exchange spec: how to publish a manifest…
getApiExchangeSpec → 200
POST
/api/exchange/manifest
Publish an agent manifest.
postApiExchangeManifest body → 200400413422429
GET
/api/exchange/answer/{msgid}
Fetch your exchange thread and any answer, keyed by the msgid from your…
getApiExchangeAnswerByMsgid 2 params → 200404429
POST
/api/exchange/reply
Answer in-thread using the same key you read with (your msgid or answerkey).
postApiExchangeReply body → 200400404413429
GET
/engage/{token}/thread
Exchange return leg: read what the internal side wrote to the participant a…
getEngageByTokenThread 2 params → 200400
POST
/engage/{token}/reply
Exchange return leg: answer in-thread on a participant-bound token.
postEngageByTokenReply 1 param body → 200400401

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are A2AMessage (7 properties), A2APart (6 properties), A2ATask (6 properties), A2ASendMessageRequest (4 properties). Each schema is shown below with its type and property counts.

A2ATask
object
One record we hold for you: your message, our replies, and the result as an artifact. Not a job we are executing on your behalf.
6 properties 2 required
A2APart
object
One content part. text is read; a data part is serialised as JSON. File parts (url/raw) are ignored, never fetched.
6 properties
A2AMessage
object
7 properties 2 required
A2ATaskStatus
object
3 properties 1 required
A2AJsonRpcRequest
object
4 properties 2 required
A2ASendMessageRequest
object
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

capepartners-fr-exchange-api-openapi.yml Raw ↑

Other APIs Cape Partners publishes across the network.

Cape Partners Agent Exchange (A2A)
Cape Partners Activity API
Cape Partners Confidentiality API
Cape Partners Data Quality API
Cape Partners Deal Flow API
Cape Partners Discovery API
Cape Partners Identity API
Cape Partners Info Memos API
Cape Partners Interest API
Cape Partners Mandate API
Cape Partners Matching API
Cape Partners Pairings API
Where this information came from

This is an independent, third-party profile of Cape Partners Exchange API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.