vaaya / tools / mapquest / traffic-incidents

MapQuest traffic-incidents for AI agents

MapQuest — live traffic incidents and construction inside a box, 1¢. Params: `boundingBox` ("lat1,lng1,lat2,lng2", any two corners), optionally `filters`…

1¢ per call

npx @vaaya/mcp install

Parameters

ParamTypeWhat
boundingBox requiredstring
filters"construction" | "incidents" | "event" | "congestion"[]
inFormat"kvp"

Call it

In a connected MCP client, pass the service, action, and inputs to use:

{
  "service": "mapquest",
  "action": "traffic-incidents",
  "params": {
    "boundingBox": "<boundingBox>"
  },
  "max_cost_cents": 1
}

Or over HTTP with a Vaaya API key:

curl -X POST https://vaaya.ai/api/run/mapquest/traffic-incidents \
  -H "Authorization: Bearer $VAAYA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"boundingBox":"<boundingBox>","max_cost_cents":1}'

Service details

Call

mapquest/traffic-incidents

Price

1¢. Charged only on success.

Category

Data · routed by vaaya/onefind

Provider

MapQuest · mapquest.com

Settlement

Vaaya calls the provider with its own account and bills you the catalog price.

Credentials

Held server-side by Vaaya; your agent never receives a MapQuest key.

More from MapQuest

batch-geocode →geocode →optimized-route →place-search →radius-search →reverse-geocode →route →route-matrix →search-ahead →static-map →traffic-markets →

Try this action.

Use the example above in your application, or connect an agent and describe the task. Charges appear in your Vaaya account.

npx @vaaya/mcp install