Cape Partners Info Memos API

The InfoMemos API from Cape Partners — 4 operation(s) for infomemos.

Business capability
Corporate Development Management BC-100.30

Operations 4

GET /api/infomemo/{session_id} Generate/retrieve the InfoMemo markdown for the session. NDA-gated #
GET /api/infomemo/{session_id}/download Download the InfoMemo markdown with appended matched names and NDA block #
GET /api/light-infomemo/{session_id}/{pair_id} Generate and stream a light (Cape-branded teaser) InfoMemo PDF for a pairing… #
GET /api/product-analysis/{session_id}/{pairing_id} Return seller product analysis for a pairing scoped to the requesting session… #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/capepartners-fr:capepartners-fr-infomemos-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

capepartners-fr-infomemos-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Cape Partners — Sniffer Agent Info Memos API
  version: 1.0.0
  description: Machine-readable API backing the Cape Partners M&A deal-flow workspace (click, humans).
  contact:
    name: Cape Partners
    url: https://www.capepartners.fr
servers:
- url: https://www.capepartners.fr
  description: Production (www) via Cloudflare
- url: https://sniffer.capepartners.fr
  description: Workspace host
- url: http://localhost:3000
  description: Local dev
tags:
- name: InfoMemos
paths:
  /api/infomemo/{session_id}:
    get:
      summary: Generate/retrieve the InfoMemo markdown for the session. NDA-gated
      tags:
      - InfoMemos
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/InfoMemo'
      parameters:
      - name: session_id
        in: path
        required: true
        schema:
          type: string
          format: uuid
        description: Workspace session UUID (acts as the scoped credential)
      security:
      - SessionToken: []
        NdaSigned: []
      operationId: getApiInfomemoBySessionId
      x-operation-id-source: derived
  /api/infomemo/{session_id}/download:
    get:
      summary: Download the InfoMemo markdown with appended matched names and NDA block
      tags:
      - InfoMemos
      responses:
        '200':
          description: InfoMemo markdown download
          content:
            application/octet-stream:
              schema:
                type: string
        '404':
          description: InfoMemo not found
      parameters:
      - name: session_id
        in: path
        required: true
        schema:
          type: string
          format: uuid
        description: Workspace session UUID (acts as the scoped credential)
      security:
      - SessionToken: []
        NdaSigned: []
      operationId: getApiInfomemoBySessionIdDownload
      x-operation-id-source: derived
  /api/light-infomemo/{session_id}/{pair_id}:
    get:
      summary: Generate and stream a light (Cape-branded teaser) InfoMemo PDF for a pairing…
      tags:
      - InfoMemos
      responses:
        '200':
          description: PDF download
          content:
            application/pdf:
              schema:
                type: string
                format: binary
        '403':
          description: Pairing not scoped to this session
          content:
            application/json:
              schema:
                type: object
                description: Not scoped
                properties:
                  error:
                    type: string
                required:
                - error
      parameters:
      - name: session_id
        in: path
        required: true
        schema:
          type: string
          format: uuid
        description: Workspace session UUID (acts as the scoped credential)
      - name: pair_id
        in: path
        required: true
        schema:
          type: string
      operationId: getApiLightInfomemoBySessionIdByPairId
      x-operation-id-source: derived
  /api/product-analysis/{session_id}/{pairing_id}:
    get:
      summary: Return seller product analysis for a pairing scoped to the requesting session…
      tags:
      - InfoMemos
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ProductAnalysis'
        '403':
          description: Pairing not scoped to this session
          content:
            application/json:
              schema:
                type: object
                description: Not scoped
                properties:
                  error:
                    type: string
                required:
                - error
        '404':
          description: No product analysis for this pairing
          content:
            application/json:
              schema:
                type: object
                description: No product analysis
                properties:
                  error:
                    type: string
                required:
                - error
      parameters:
      - name: session_id
        in: path
        required: true
        schema:
          type: string
          format: uuid
        description: Workspace session UUID (acts as the scoped credential)
      - name: pairing_id
        in: path
        required: true
        schema:
          type: integer
      operationId: getApiProductAnalysisBySessionIdByPairingId
      x-operation-id-source: derived
components:
  schemas:
    InfoMemo:
      type: object
      properties:
        markdown:
          type: string
    ProductAnalysis:
      type: object
      properties:
        pairing_id:
          type: string
        website_url:
          type: string
        product_summary:
          type: string
        tech_stack:
          type: string
        quality_score:
          type: number
        buyer_fit_notes:
          type: string
        consolidation_potential:
          type: string
        last_analyzed_at:
          type: string
        buyer_solution_scope_1:
          type: string
        buyer_solution_scope_2:
          type: string
        buyer_solution_scope_3:
          type: string
        tech_stack_flags:
          type: string
        fit_score:
          type: number
        data_quality_flags:
          type: string
  securitySchemes:
    SessionToken:
      type: apiKey
      in: header
      name: X-Session-Id
      description: '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 parameter as a credential). A valid request must present a well-formed UUID-v4 in the path segment {session_id} AND a first-party Origin/Referer (or none). Requests carrying a known-foreign Origin/Referer are refused 403. Per-IP rate limiting applies. All responses carry Referrer-Policy: strict-origin-when-cross-origin.'
    NdaSigned:
      type: apiKey
      in: header
      name: X-Nda-Signed
      description: 'Precondition (not a literal header): a server-side NDA signature for {session_id} must be recorded in the nda_signatures table via POST /api/nda/sign before NDA-gated resources (/api/matched-names, /api/infomemo/*) will serve data. Recorded signatures are enforced server-side (helper `nda_signed`), not by trusting a client header.'