Skip to main content
An authorized agent can discover supported AionCX operations, submit work, and retrieve its results through REST or MCP. Start with the task and input, use the credential for that domain, and follow the returned state to a useful result.

​
1. Read the current documentation

This documentation site exposes a public /llms.txt index and a separate /mcp documentation-search endpoint. Connect that endpoint in clients that support it, or follow the index and page links directly. Documentation search reads instructions. Product processing uses the application endpoint below.

​
2. Select the connection

A person establishes the account, verifies email, configures sources, creates the connection, and funds the account when required. Store the supplied credential in the client environment or secret configuration.

​
3. Discover tools

A standard MCP client initializes the connection and calls tools/list. The server returns tools visible under that credential’s current authority. For a direct discovery check, set MACH1_API_KEY and MACH1_MCP_URL in the environment. Use the workspace query selector on the URL when the key grants multiple workspaces.

​
4. Complete a task

​
Transcribe and analyze a conversation

  1. Use mach1_get_transport for upload endpoints and limits.
  2. Use mach1_list_analysis_definitions when analysis is required. Select real published version IDs; an omitted list requests no analysis.
  3. Submit an audio URL or transcript with the caller’s saved idempotency key. Local audio bytes and oversized transcripts use direct receiver transport.
  4. Retain the interaction ID and revisions. Poll mach1_get_status.
  5. Read mach1_get_transcript and mach1_get_results, following pagination and citing evidence.
See transcription, analysis, and results.

​
Request a forecast

  1. For registered metrics, use mach1_list_forecast_sources with the authorized workspace.
  2. Construct the numerical or metric request described in forecasting.
  3. Call mach1_submit_forecast with request and the caller’s saved idempotency_key.
  4. Retain run_id and the returned price.
  5. Poll mach1_get_forecast, then retrieve every result page with the same quantile selection.

​
Prepare workforce work in Atlas

Begin with atlas_discover_workforce. Review the source evidence, use the existing setup preview where needed, then use the paired staffing, draft, and publication operations your connection is granted. Follow the Workforce contract for exact selectors, recoverable keys, current-source checks, and publication states. The operator guide explains the same work in application terms.

​
5. Report the outcome

State the task, saved request/run ID, result state, useful findings or forecast, and relevant limitations. Cite available source evidence. Distinguish a completed result from accepted work still waiting to run. After an uncertain submission, retry the original payload with its original key. Explain a funding or permission blocker and direct the person to the appropriate screen. Billing-ledger reconciliation requires an authorized billing view; scoped result access alone does not supply it. The Mastra example provides an executable client. Setup, funding, and key replacement remain human setup steps in that example.