Crossings
by borderscout.scalpstream.com in Other
BorderScout crossing query (crossings ranked by all-in time: drive + wait, per lane type)
https://borderscout.scalpstream.com/crossings- Price
- $0.01
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 5 h ago, next any minute now
Reliability
Latest check failed 5 h ago: Amount "0.01" is not in atomic token units
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://borderscout.scalpstream.com/crossings
Each call costs $0.01 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://borderscout.scalpstream.com/crossings?lanes=standard%2CSENTRI%2FNEXUS&lat=32.7157&limit=5&lon=-117.1611&vehicle=passengerExample response
The provider's example. We can't check it without paying.
{
"crossings": [
{
"all_in_min": 39,
"border": "Mexican",
"distance_km": 28,
"drive_min": 24,
"lane": "SENTRI/NEXUS",
"port": "San Ysidro",
"updated": "2026-08-06T13:45:00Z",
"wait_min": 15
}
],
"disclaimer": "Wait times are US Customs and Border Protection's own published figures and can change sharply within minutes; CBP reports nothing at all for some lanes, and those are shown as unreported rather than as zero. Drive times are straight-line estimates at an assumed average speed, not routed directions. Confirm at the crossing.",
"place": "San Diego",
"price_usd": "0.01",
"service": "BorderScout",
"source": "U.S. Customs and Border Protection border wait times (bwt.cbp.gov), public domain"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://borderscout.scalpstream.com/crossings?lanes=standard%2CSENTRI%2FNEXUS&lat=32.7157&limit=5&lon=-117.1611&vehicle=passenger'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://borderscout.scalpstream.com/crossings?lanes=standard%2CSENTRI%2FNEXUS&lat=32.7157&limit=5&lon=-117.1611&vehicle=passenger' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fborderscout.scalpstream.com%2Fcrossings
const res = await pay("https://borderscout.scalpstream.com/crossings?lanes=standard%2CSENTRI%2FNEXUS&lat=32.7157&limit=5&lon=-117.1611&vehicle=passenger");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://borderscout.scalpstream.com/crossings?lanes=standard%2CSENTRI%2FNEXUS&lat=32.7157&limit=5&lon=-117.1611&vehicle=passenger")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 5 h ago | Amount "0.01" is not in atomic token units | 402 | 586 ms | $0.01 |
| 13 h ago | Amount "0.01" is not in atomic token units | 402 | 527 ms | $0.01 |
| 21 h ago | Amount "0.01" is not in atomic token units | 402 | 620 ms | $0.01 |
| 30 h ago | Amount "0.01" is not in atomic token units | 402 | 623 ms | $0.01 |
| 38 h ago | Amount "0.01" is not in atomic token units | 402 | 540 ms | $0.01 |
Show 10 older checks
| 46 h ago | Amount "0.01" is not in atomic token units | 402 | 509 ms | $0.01 |
| 2 days ago | Amount "0.01" is not in atomic token units | 402 | 542 ms | $0.01 |
| 3 days ago | Amount "0.01" is not in atomic token units | 402 | 619 ms | $0.01 |
| 3 days ago | Amount "0.01" is not in atomic token units | 402 | 567 ms | $0.01 |
| 3 days ago | Amount "0.01" is not in atomic token units | 402 | 648 ms | $0.01 |
| 3 days ago | Amount "0.01" is not in atomic token units | 402 | 558 ms | $0.01 |
| 4 days ago | Amount "0.01" is not in atomic token units | 402 | 508 ms | $0.01 |
| 4 days ago | Amount "0.01" is not in atomic token units | 402 | 534 ms | $0.01 |
| 4 days ago | Amount "0.01" is not in atomic token units | 402 | 560 ms | $0.01 |
| 5 days ago | Amount "0.01" is not in atomic token units | 402 | 532 ms | $0.01 |