Transcribe your first recording - AionCX Documentation

Get your first Mach-1 result by submitting a short recording through AionCX Build. Retain its interaction ID, follow processing, and inspect the transcript.

1. Open your workspace

Sign up with email and password, confirm your email, and enter Build. Existing invited people keep their assigned workspace selection. Check the workspace name before submitting. A fresh eligible self-service workspace receives the published Interaction findings Definition. Your workspace, keys, sources, and history continue when you add credit.

2. Submit audio

Open New request. Upload a WAV, MP3, or M4A recording, or provide an HTTPS audio URL. Choose No analysis for transcription alone. To inspect findings from the same request, select Interaction findings or another available published analysis. Review the configured rate and choose Standard or Reserved processing. In Connect your key, create a personal scoped key or connect an existing key with submission and read access. Send the request and retain its interaction ID. Reserved processing starts overnight, from 7 p.m. to 7 a.m. Eastern time including daylight saving time, or on weekends.

3. Inspect the result

Open Requests, select the request, and follow its status. Inspect the transcript, available speaker attribution, and source timing. If analysis was selected, open its findings and supporting evidence. Accepted work can wait for funding. Add credit through Usage, then continue following the same request. A completed analysis can return zero findings.

4. Continue through the pipeline

Read analysis, results and evidence, and forecasting for the next job. Existing transcripts and numerical history have their own direct entry points. You can also connect supported sources for future deliveries.

Start from an existing transcript through REST

Build displays the receiver URL for your workspace. Copy it into MACH1_TRANSCRIPT_URL, then discover a published Definition ID in Build → Analysis or GET /api/ingest/analysis-definitions.

export ATLAS_INGEST_TOKEN='<personal-scoped-key>'
export MACH1_TRANSCRIPT_URL='<receiver-url-from-Build>'
export MACH1_WORKSPACE_ID='<workspace-id-from-Build>'
export MACH1_DEFINITION_VERSION_ID='<published-version-id>'
export MACH1_IDEMPOTENCY_KEY='<new-uuid-for-this-submission>'

curl -sS -X POST "$MACH1_TRANSCRIPT_URL" \
  -H "Authorization: Bearer $ATLAS_INGEST_TOKEN" \
  -H "Idempotency-Key: $MACH1_IDEMPOTENCY_KEY" \
  -H 'Content-Type: application/json' \
  --data "{\"workspace_id\":\"$MACH1_WORKSPACE_ID\",\"external_conversation_id\":\"demo-1\",\"pricing_tier\":\"standard\",\"text\":\"We agreed to send the revised proposal on Friday.\",\"requested_definition_version_ids\":[\"$MACH1_DEFINITION_VERSION_ID\"]}"

The receiver returns an interactionId. Poll GET https://build.aioncx.com/api/ingest/interactions/{interactionId}/status with the same bearer token and X-Workspace-Id header; then request /results and /transcript. Keep the original idempotency key for an uncertain retry. Reusing an external conversation ID with changed content creates a new input revision under the same interaction. To skip paid analysis, submit "requested_definition_version_ids":[]. Omission also requests no analysis in API and MCP calls. Supplied transcripts do not incur transcription charges; each selected Definition uses its service’s configured rate per transcript duration. See Usage and pricing. For an agent connection, use the agent quickstart.

​1. Open your workspace

​2. Submit audio

​3. Inspect the result

​4. Continue through the pipeline

​Start from an existing transcript through REST

1. Open your workspace

2. Submit audio

3. Inspect the result

4. Continue through the pipeline

Start from an existing transcript through REST