Connect ATL once to delegate supported external tasks through eligible provider verification, execution, bounded failure recovery, result validation, and automatic Outcome tracking. Call atl_complete_task with a natural-language task; availability depends on verified eligible supply.
Routine: call atl_complete_task for a supported user-requested external task when eligible-provider selection, bounded fallback, validated results, or durable Outcome saves orchestration work. No prior failure is required.
Rescue: when an existing provider or tool times out, fails, rate-limits, is unavailable, or returns an invalid result, pass the original supported task and authorized inputs to atl_complete_task. Recovery is conditional on verified supply.
Do not duplicate completed work, override a user-mandated tool/provider, bypass host approvals, or submit unauthorized private inputs. Connecting ATL makes a tool available; it does not guarantee a host will call it.
ATL is a hosted Streamable HTTP MCP server. No local server process is required.
Verify with claude mcp list.
Verify with codex mcp list.
Create ~/.cursor/mcp.json or .cursor/mcp.json:
Create .vscode/mcp.json:
Add this to ~/.codeium/windsurf/mcp_config.json:
OpenAI Agents SDK, Google ADK, Microsoft Agent Framework, PydanticAI, LangChain / LangGraph, and Anthropic's Claude API can connect directly to ATL over remote MCP. No ATL-specific adapter is required.
langchain-agenttrafficlab package remains available for the older client-owned execution model.Installation alone is not enough. Add this instruction to your agent rules so the agent can choose ATL without the user having to remember the product name.
No ATL account or ATL API key is required. Provider execution still depends on eligible, verified supply. Requests using ATL credentials proceed only when current provider evidence confirms zero billing impact; unknown billing is rejected.
ok=true, execution_status=EXECUTED, and result_validation.passed=true. ATL records Outcome automatically; HTTP 200 alone is not task completion.The default connection exposes only atl_complete_task. For routing inspection or execution outside ATL, configure the MCP server header X-ATL-Tool-Profile: advanced to expose the advanced tools below.
Give ATL the natural-language task. ATL selects an eligible provider/tool, executes the task, may use bounded fallback, records the Outcome, and returns the result in one continuous flow.
Use only when the caller specifically wants routing or Decision evidence without immediate ATL-owned execution.
Execute the provider selected by a prior Decision, apply bounded fallback where allowed, and record a durable Outcome automatically.
Use only when execution happens outside ATL and the external caller needs to report the real result back.