Skip to main content
Use the published AionCX contracts for the task you are building. Each surface documents its credential, workspace selector, inputs, results, and recovery behavior.

​
First useful request

Start with transcription, analysis of an existing transcript, or a numerical forecast. Use the Workforce operator journey when implementing its equivalent external operations.

​
Authentication and lifecycle

Read authentication before implementing a client. A browser session and a scoped bearer key have different purposes. Keep the endpoint and workspace selector from the relevant contract. Asynchronous acceptance establishes that work was admitted. Read the saved status and results to determine completion. Retain operation keys across uncertain retries and follow response pagination. Callbacks and status explains available delivery paths. Usage and pricing describes the charging basis. Each contract states its supported limits.