65trust / 100
Berlin Arrivals
by Saylor Innovations Transit in Other
x402 APIPassing, checked 28 min ago
Berlin VBB real-time departures for U-Bahn, S-Bahn, tram and bus - line, direction, delay and platform
GET
https://saylorinnovations.com/api/transit/berlin/arrivals- Price
- $0.01
- per call in USDC
- Uptime
- 78.6%
- last 30 days
- Response time
- 1.4 s
- 2.2 s slowest 5%
- Last check
- Passed
- 28 min ago, next in 5 min
Reliability
All checks passedSome failedAll failedNot checked
How to call it
GET https://saylorinnovations.com/api/transit/berlin/arrivals
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://saylorinnovations.com/api/transit/berlin/arrivals?stop=AlexanderplatzParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
stop | string | No | station or stop name, e.g. Alexanderplatz, Hauptbahnhof (query) |
Example response
The provider's example. We can't check it without paying.
{
"arrivals": [
{
"delay_min": 0,
"direction": "Strausberg Nord",
"line": "S5",
"planned_time": "2026-09-29T23:14:00+02:00",
"product": "suburban"
}
],
"count": 1,
"found": true,
"stop": "S+U Alexanderplatz Bhf (Berlin)"
}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://saylorinnovations.com/api/transit/berlin/arrivals?stop=Alexanderplatz'
# 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://saylorinnovations.com/api/transit/berlin/arrivals?stop=Alexanderplatz' \
| 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%2Fsaylorinnovations.com%2Fapi%2Ftransit%2Fberlin%2Farrivals
const res = await pay("https://saylorinnovations.com/api/transit/berlin/arrivals?stop=Alexanderplatz");
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://saylorinnovations.com/api/transit/berlin/arrivals?stop=Alexanderplatz")
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 |
|---|---|---|---|---|
| 28 min ago | Passed | 402 | 1.5 s | $0.01 |
| 5 h ago | Passed | 402 | 1.2 s | $0.01 |
| 9 h ago | Passed | 402 | 1.4 s | $0.01 |
| 13 h ago | Passed | 402 | 1.5 s | $0.01 |
| 17 h ago | Passed | 402 | 1.1 s | $0.01 |
Show 9 older checks
| 21 h ago | Passed | 402 | 1.1 s | $0.01 |
| 25 h ago | Passed | 402 | 2.6 s | $0.01 |
| 28 h ago | Expected HTTP 402, got 503 | 503 | 7.3 s | - |
| 32 h ago | Expected HTTP 402, got 503 | 503 | 7.5 s | - |
| 36 h ago | Passed | 402 | 1.4 s | $0.01 |
| 39 h ago | Passed | 402 | 1.1 s | $0.01 |
| 43 h ago | Passed | 402 | 1.3 s | $0.01 |
| 46 h ago | Passed | 402 | 2.2 s | $0.01 |
| 2 days ago | Expected HTTP 402, got 503 | 503 | 7.3 s | - |