Interfaces
| Binding | A2A version | URL |
|---|---|---|
| JSONRPC | 0.3.0 | https://borderscout.scalpstream.com/a2a |
Capabilities
- Streaming
- No
- Push notifications
- No
- Extended card for signed-in callers
- No
https://github.com/google-a2a/a2a-x402/v0.1
Security and formats
- Requires
- None required
- Schemes
- Not declared
- Accepts
- text/plain
- Returns
- text/plain, application/json
Skills
- fastest border crossing from a location
best-border-crossingGiven a place, returns US border crossings ranked by total time (drive + current wait), honouring lane eligibility (standard, SENTRI/NEXUS, Ready, FAST) and vehicle type.
4 examples
- border wait times near San Diego
- fastest crossing into Mexico from Laredo for a truck
- best border crossing from Buffalo
- I have SENTRI — quickest crossing from San Diego
In: text/plain · Out: text/plain, application/json
- wait times by lane and vehicle type
lane-and-vehicle-waitsCurrent CBP waits broken out per lane — standard, SENTRI/NEXUS, Ready, FAST — and per vehicle type (passenger, commercial, pedestrian), because eligibility changes which crossing is actually fastest.
3 examples
- SENTRI wait at Otay Mesa
- commercial truck wait at Laredo
- pedestrian wait at San Ysidro right now
In: text/plain · Out: text/plain, application/json
- the nearest crossing is often not the fastest
nearest-vs-fastestCompares the closest port of entry against the one with the lowest all-in time, so a longer drive to a shorter queue is surfaced rather than assumed away.
3 examples
- is the nearest crossing to San Diego the fastest
- should I drive further for a shorter border wait from Laredo
- compare crossings near Buffalo
In: text/plain · Out: text/plain, application/json