Sense Street Batch API

The enterprise REST API. Callers upload files of broker conversations for asynchronous processing and retrieve the extracted RFQs once parsing completes, or call the prediction operations synchronously against a single conversation or chat snippet. Bond reference data and electronic RFQ records are uploaded through the same surface for instrument resolution and reconciliation. Authentication is a client-signed RS256 JWT bearer assertion with the caller's public key sent in an X-key header; there is no OAuth and no scope surface.

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/sense-street-batch-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.

API entry from apis.yml

apis.yml Raw ↑
name: Sense Street Batch API
description: The enterprise REST API. Callers upload files of broker conversations for asynchronous processing
  and retrieve the extracted RFQs once parsing completes, or call the prediction operations synchronously
  against a single conversation or chat snippet. Bond reference data and electronic RFQ records are uploaded
  through the same surface for instrument resolution and reconciliation. Authentication is a client-signed
  RS256 JWT bearer assertion with the caller's public key sent in an X-key header; there is no OAuth and
  no scope surface.
humanURL: https://docs.sensestreet.com/batch-api
baseURL: https://{tenant}.api.sensestreet.com/api/v1
tags:
- Batch Processing
- Conversation Intelligence
- RFQ Extraction
properties:
- type: Documentation
  url: https://docs.sensestreet.com/batch-api
- type: Authentication
  url: authentication/sense-street-authentication.yml
- type: Conventions
  url: conventions/sense-street-conventions.yml
- type: DataModel
  url: data-model/sense-street-data-model.yml
- type: ErrorCatalog
  url: errors/sense-street-problem-types.yml
- type: X-MCPServerCandidate
  url: mcp/sense-street-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate
    — a tool list derived from the published API contracts, not an existing server. The scorer already
    read the manifest and reported mcp_server correctly; the MCPServer type was crediting the artifact-type
    surfaces with a server that does not exist.'
x-base-url-note: 'The host is per-tenant and issued at onboarding. Evidence: the wildcard certificate
  Sense Street serves carries the SANs *.api.sensestreet.com and *.api.test.sensestreet.com; the first-party
  SDK hard-codes the JWT audience claim aud=api.sensestreet.com and requires the customer to pass api_url
  because there is no default; and the bare host api.sensestreet.com has no A record. The /api/v1 path
  segment is appended by the SDK itself and answers live (HTTP 401, "Invalid or missing token") on the
  Sense Street portal host.'