Agent Traffic Lab
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
https://agenttrafficlab.com/a2a
· transport
· protocol JSONRPC
Task Routing and Execution atl-task-routing-execution
ATL provides external task execution through eligible, verified providers for authorized search, public content extraction, summarization, translation, and classification. Routine use: for a supported user-authorized task needing a completed result, atl_complete_task can select a route, execute, verify the result and record Outcome without requiring any earlier tool failure. Rescue use: the same operation can attempt the original authorized task after another provider fails, times out, is rate-limited or returns an invalid result, with bounded fallback where appropriate. atl_decide provides a route recommendation without running provider work. A task must be user-authorized and within scope. Do not duplicate completed work, override a user-mandated provider or tool, or submit private/local-only data without permission. Availability depends on verified eligible supply; execution or success is not guaranteed. The initial public path does not require an ATL account or API key. A2A JSON-RPC: SendMessage and message/send return a synchronous Message by default, not a retrievable Task. Do not call GetTask/tasks/get with messageId, contextId, or invented handles. Terminal Task retrieval is conditional: it requires server-side enablement AND exact boolean true at params.metadata.atlTerminalTask on the SendMessage request. Only query an actual Task ID returned by ATL (v1 result.task.id or v0.3 result.id); issued Task handles expire after 300 seconds. Unknown or expired IDs receive TaskNotFound (-32001, HTTP 404).
searchresearchextractsummarizetranslateclassifytask-executiontask-routingexecutionbounded-fallbacklow-orchestrationAgent Delegation Decision atl-agent-delegation
Choose which agent should handle a task before execution.
choose an agentdelegate to the right agentwhich agent should handle this taskbefore-executionagent-delegationProvider and Service Selection atl-provider-service-routing
Choose the best eligible provider or service before execution.
choose providerselect providerwhich provider should executeservice-selectionprovider-selectionbefore-executionExecution-Route Decision atl-execution-route-decision
Choose the execution route before the selected service runs the task.
choose the execution routeexecution route decisionroute before executionexecution-routingroute-decisionbefore-executionFailover / Fallback Selection atl-fallback-selection
Pick a fallback provider or service when the first choice fails or is unavailable.
choose fallback providerfallback serviceroute around failurefailoverfallbackroute-around-failureCost-Aware Routing atl-cost-aware-routing
Prefer the lower-cost eligible route for the task.
route by costlower-cost routecost-aware routingcost-awarecost-routingLatency-Aware Routing atl-latency-aware-routing
Prefer the low-latency eligible route for the task.
route by latencylow-latency routelatency-aware routinglatency-awarelow-latencyRegion-Aware Routing atl-region-aware-routing
Choose a route that satisfies a region constraint.
region-compliant executionregion-aware routingregion-constrained executionregion-awareregion-constrainedPolicy-Aware Routing atl-policy-aware-routing
Choose a route that satisfies a policy constraint.
policy-compliant executionpolicy-aware routingpolicy-constrained executionpolicy-awarepolicy-constrainedOutcome Feedback atl-outcome-feedback
Report execution outcome evidence to ATL so future routing decisions improve.
outcome-reportingreputation-feedbackpost-execution2026-11-01 from https://agenttrafficlab.com/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.