Agent Traffic Lab
mcp.agenttrafficlab.com
· Agent Traffic Lab
Find a verified executable provider or MCP tool for a task, with a callable handoff and fallback after failure.
mcp.agenttrafficlab.com via a single DNS TXT record to add the
verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
Dispute or improve this rating
C
Conformance score: 61/100
C-grade: usable but has clear conformance issues, review the breakdown below.
click to expand breakdown ▾
click to collapse breakdown ▴
agent-card.json changed within the last 7 days. We track these so downstream callers can react.
Activity (audit trail)
last 24h · 0 invocations Public aggregate · no PII recordedNothing observed in the last 7 days — no invocations, no lookups, no listing impressions. Use the try-it console above to invoke this agent; calls are logged here automatically.
Endpoints
| Agent card | https://mcp.agenttrafficlab.com/.well-known/agent-card.json |
| Provider | https://agenttrafficlab.com |
| Docs | https://mcp.agenttrafficlab.com/mcp |
Skills · 9 declared · mapped to canonical taxonomy
Choose which agent should handle a task before execution.
Choose the best eligible provider or service before execution.
Choose the execution route before the selected service runs the task.
Pick a fallback provider or service when the first choice fails or is unavailable.
Prefer the lower-cost eligible route for the task.
Prefer the low-latency eligible route for the task.
Choose a route that satisfies a region constraint.
Choose a route that satisfies a policy constraint.
Report execution outcome evidence to ATL so future routing decisions improve.
Health · last 14 probes
Cheaper or better alternatives per-skill
For each canonical skill this agent serves, the cheapest priced competitor and the highest-quality competitor. Only shown when at least one beats the current agent. Skills where this agent is already best on both axes are hidden.
Similar agents embedding-nearest
Embed your Agenstry badge
Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.
Markdown / HTML snippets
[](https://agenstry.com/agents/mcp.agenttrafficlab.com) [](https://agenstry.com/agents/mcp.agenttrafficlab.com) [](https://agenstry.com/agents/mcp.agenttrafficlab.com) [](https://agenstry.com/agents/mcp.agenttrafficlab.com)
Audit-grade evidence bundle
JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against
our JWKS. See the methodology.
Raw agent card JSON
{
"name": "Agent Traffic Lab",
"description": "Find a verified executable provider or MCP tool for a task, with a callable handoff and fallback after failure.",
"supportedInterfaces": [
{
"url": "https://mcp.agenttrafficlab.com/a2a",
"protocolBinding": "JSONRPC",
"protocolVersion": "1.0"
}
],
"provider": {
"organization": "Agent Traffic Lab",
"url": "https://agenttrafficlab.com"
},
"version": "0.1",
"documentationUrl": "https://mcp.agenttrafficlab.com/mcp",
"capabilities": {
"streaming": false,
"pushNotifications": false,
"extendedAgentCard": false,
"extensions": []
},
"securitySchemes": {},
"securityRequirements": [],
"defaultInputModes": [
"text/plain",
"application/json"
],
"defaultOutputModes": [
"application/json",
"text/plain"
],
"skills": [
{
"id": "atl-agent-delegation",
"name": "Agent Delegation Decision",
"description": "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"
],
"examples": [
"Choose which agent should handle this task before execution",
"Delegate the task to the right agent"
],
"inputModes": [
"text/plain",
"application/json"
],
"outputModes": [
"application/json"
],
"securityRequirements": []
},
{
"id": "atl-provider-service-routing",
"name": "Provider and Service Selection",
"description": "Choose the best eligible provider or service before execution.",
"tags": [
"choose provider",
"select provider",
"which provider should execute",
"service-selection",
"provider-selection",
"before-execution"
],
"examples": [
"Choose provider for this task",
"Select service before execution"
],
"inputModes": [
"text/plain",
"application/json"
],
"outputModes": [
"application/json"
],
"securityRequirements": []
},
{
"id": "atl-execution-route-decision",
"name": "Execution-Route Decision",
"description": "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"
],
"examples": [
"Choose the execution route before the service runs",
"Route the task before execution target selection is final"
],
"inputModes": [
"text/plain",
"application/json"
],
"outputModes": [
"application/json"
],
"securityRequirements": []
},
{
"id": "atl-fallback-selection",
"name": "Failover / Fallback Selection",
"description": "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"
],
"examples": [
"Choose a fallback provider if the first choice fails",
"Route around failure"
],
"inputModes": [
"text/plain",
"application/json"
],
"outputModes": [
"application/json"
],
"securityRequirements": []
},
{
"id": "atl-cost-aware-routing",
"name": "Cost-Aware Routing",
"description": "Prefer the lower-cost eligible route for the task.",
"tags": [
"route by cost",
"lower-cost route",
"cost-aware routing",
"cost-aware",
"cost-routing"
],
"examples": [
"Route by cost while keeping the task eligible",
"Choose the lower-cost eligible route"
],
"inputModes": [
"text/plain",
"application/json"
],
"outputModes": [
"application/json"
],
"securityRequirements": []
},
{
"id": "atl-latency-aware-routing",
"name": "Latency-Aware Routing",
"description": "Prefer the low-latency eligible route for the task.",
"tags": [
"route by latency",
"low-latency route",
"latency-aware routing",
"latency-aware",
"low-latency"
],
"examples": [
"Route by latency for this task",
"Choose a low-latency eligible route"
],
"inputModes": [
"text/plain",
"application/json"
],
"outputModes": [
"application/json"
],
"securityRequirements": []
},
{
"id": "atl-region-aware-routing",
"name": "Region-Aware Routing",
"description": "Choose a route that satisfies a region constraint.",
"tags": [
"region-compliant execution",
"region-aware routing",
"region-constrained execution",
"region-aware",
"region-constrained"
],
"examples": [
"Choose a region-compliant execution route",
"Route this task to a region-constrained provider"
],
"inputModes": [
"text/plain",
"application/json"
],
"outputModes": [
"application/json"
],
"securityRequirements": []
},
{
"id": "atl-policy-aware-routing",
"name": "Policy-Aware Routing",
"description": "Choose a route that satisfies a policy constraint.",
"tags": [
"policy-compliant execution",
"policy-aware routing",
"policy-constrained execution",
"policy-aware",
"policy-constrained"
],
"examples": [
"Choose a policy-compliant execution route",
"Route this task under policy constraints"
],
"inputModes": [
"text/plain",
"application/json"
],
"outputModes": [
"application/json"
],
"securityRequirements": []
},
{
"id": "atl-outcome-feedback",
"name": "Outcome Feedback",
"description": "Report execution outcome evidence to ATL so future routing decisions improve.",
"tags": [
"outcome-reporting",
"reputation-feedback",
"post-execution"
],
"examples": [
"Report success with observed latency and cost",
"Report failure with failure type and error code"
],
"inputModes": [
"application/json"
],
"outputModes": [
"application/json"
],
"securityRequirements": []
}
]
}