Before you start
Open AionCX Build and select the correct workspace. You need a key with submission and read access to send the recording and inspect the result. The quickstart covers the browser steps. Direct uploads accept WAV, MP3, and M4A. The current direct-audio boundary is 256 MiB and four hours. An audio URL must be reachable by the processing service and pass its destination checks. Discover the workspace receiver URL in Build → Developers or through MCP transport discovery.Send a recording
In New request, select an audio file or audio URL. Choose No analysis when you want transcription alone, or select the published analysis versions to run afterward. Choose Standard or Reserved processing and connect your scoped key. Reserved processing starts in its overnight or weekend window. Send the request once and retain the admitted interaction ID. For an application, use the direct receiver’s/v1/ingest/audio or /v1/ingest/audio-url contract in the REST reference. MCP can submit an audio URL; local audio bytes use the discovered direct upload endpoint.
Inspect the transcript
Open the request and check its status before reading the transcript.- Review the text and available speaker turns.
- Use source timing when supplied to locate the relevant part of the recording.
- Check which input and transcript revision you are reading.
- Confirm important names, amounts, dates, and commitments against the source.