AsyncAPI channel · S&P Global · Kensho Scribe Real Time API

/

Single bidirectional WebSocket channel. All client and server messages are JSON objects discriminated by the `message` field. The expected lifecycle is Authenticate -> StartTranscription -> AddData (repeating) -> EndOfStream, with the server streaming AddTranscript messages while data is processed and EndOfTranscript when complete. Audio must be sent in segments of at most 15 seconds.

Open source AsyncAPI → All S&P Global channels S&P Global provider profile
Provider: S&P Global AsyncAPI: v2.6.0 Spec: Kensho Scribe Real Time API Operations: 2 Messages: 10

Channel address

/

Operations

publish
sendClientMessage
Messages sent from client to Kensho Scribe Real Time
receiveServerMessage
Messages sent from Kensho Scribe Real Time to client

Messages

Authenticate
First client message; supplies the Kensho access token.
Content-Type:
StartTranscription
Configures the audio format and opens a transcription session.
Content-Type:
AddData
Sends one chunk of base64-encoded PCM audio. Chunks must represent at most 15 seconds of audio and carry a monotonically increasing sequence_number.
Content-Type:
EndOfStream
Client signal that no further audio will be sent.
Content-Type:
Authenticated
Server acknowledgement that the access token was accepted.
Content-Type:
TranscriptionStarted
Server confirmation that a transcription session is active.
Content-Type:
DataAdded
Server acknowledgement that an audio chunk was accepted.
Content-Type:
AddTranscript
Server-pushed transcript segment for previously sent audio.
Content-Type:
EndOfTranscript
Server signal that all transcripts for the stream have been emitted.
Content-Type:
Error
Server error response carrying a human-readable reason.
Content-Type:

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.

Work with this as data

Every channel 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 event channels

4 MCP tools reach this
  • find_channelsBrowse and filter every channel in the catalog.
  • 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 channel 
curl "https://apis.io/api/v1/channels/untitled"
All event channels 
curl "https://apis.io/api/v1/channels?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.

GitHub Google LinkedIn

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