Back to A2A agents
● healthy

Machine-payable US border-crossing queries over x402. Ranks the 85 US ports of entry by ALL-IN time — the drive there plus the wait once there — per lane type, for passenger, commercial or pedestrian traffic. The nearest crossing is often not the fastest. Live CBP data.

Transport
JSONRPC
Protocol
1.0
Price
—

A2A readiness

A · 95/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 97.4/100), which weighs availability, conformance, card completeness and speed. How the two differ

Valid Agent Card 10/10 Parseable Agent Card with the required fields.
Live JSON-RPC 25/25 Endpoint answers A2A JSON-RPC (539 ms).
Protocol version 10/10 Declares A2A 1.0 with supportedInterfaces[] (v1 card shape).
JWS signature 10/10 Signature verifies (EdDSA, kid 854ae25d92ed49e7) against the provider JWKS.
Uptime (30 days) 15/15 3/3 probes succeeded; final after 5 probes in 30 days.
Skill declaration 10/10 Declares 3 skill(s) with structured metadata.
Verified identity 8/10 Provider declared and domain control verified on agent-tools.cloud (company-registry check not available yet).
Freshness + modern flags 5/5 seen in a source within 7 days; declares a modern payment/commerce flag.
Security declaration 2/5 Declares 1 security scheme(s).
Responsiveness: Responsive (539 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Payment evidence: agent_card — The listing's own card or descriptor declares payment. Also: catalog_listing. Qualifies the payment claim; adds no points.
Measured 2026-11-11.
Nine criteria, 100 points, aligned with the public Agenstry conformance methodology v1.1. Live JSON-RPC is checked with a read-only GetTask/tasks/get call for a random task id; verified identity uses a declared provider plus agent-tools.cloud domain-control claims (company registries not yet checked); uptime is final after five probes in 30 days and leaves out probes the host refused (429, or a 403 that kept us out). Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 6,309 reachable A2A agents in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness
Higher than 100% of peers
This listing 95 · peer median 54
Latency
Faster than 28% of peers
This listing 587 ms · peer median 398 ms

Where it loses the most points, and how to win them back

  • Security declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
    Now: Declares 1 security scheme(s).
  • Verified identity −2 — Claim the listing and prove control of its domain.
    Now: Provider declared and domain control verified on agent-tools.cloud (company-registry check not available yet).

How many agent tools actually work · All statistics

Skills

How to call

A2A endpoint (JSONRPC)
https://borderscout.scalpstream.com/a2a
Agent card
https://borderscout.scalpstream.com/.well-known/agent-card.json
Documentation
https://borderscout.scalpstream.com/.well-known/x402
Homepage
https://borderscout.scalpstream.com/

Listed in

Directories this entry was found in.

a2aregistry since 2026-08-06 submission since 2026-08-23 agenstry since 2026-09-08 a2a-registry since 2026-10-22