transit402.dev
https://transit402.dev/subway/nearestShares a payout wallet with 3 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Canonical agent invocation uses POST with JSON body { lat, lng, limit? }. GET with query parameters remains supported for browser/manual use.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
48.1% avgResponse time
p50 108ms · p95 120msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/29/2026, 3:00:00 PM | 100% | 1 | 121ms |
| 9/29/2026, 5:00:00 PM | 100% | 1 | 76ms |
| 9/29/2026, 7:00:00 PM | 100% | 1 | 119ms |
| 9/29/2026, 9:00:00 PM | 100% | 1 | 118ms |
| 9/29/2026, 11:00:00 PM | 100% | 1 | 125ms |
| 9/30/2026, 2:00:00 AM | 100% | 1 | 109ms |
| 9/30/2026, 4:00:00 AM | 100% | 1 | 107ms |
| 9/30/2026, 6:00:00 AM | 100% | 1 | 101ms |
| 9/30/2026, 8:00:00 AM | 100% | 1 | 108ms |
| 9/30/2026, 10:00:00 AM | 100% | 1 | 119ms |
| 9/30/2026, 12:00:00 PM | 100% | 1 | 107ms |
| 9/30/2026, 2:00:00 PM | 100% | 1 | 87ms |
| 9/30/2026, 4:00:00 PM | 100% | 1 | 118ms |
| 9/30/2026, 6:00:00 PM | 100% | 1 | 120ms |
| 9/30/2026, 8:00:00 PM | 100% | 1 | 106ms |
| 9/30/2026, 10:00:00 PM | 100% | 1 | 120ms |
| 10/1/2026, 12:00:00 AM | 100% | 1 | 111ms |
| 10/1/2026, 2:00:00 AM | 100% | 1 | 107ms |
| 10/1/2026, 4:00:00 AM | 100% | 1 | 97ms |
| 10/1/2026, 6:00:00 AM | 100% | 1 | 108ms |
| 10/1/2026, 8:00:00 AM | 100% | 1 | 119ms |
| 10/1/2026, 10:00:00 AM | 100% | 1 | 109ms |
| 10/1/2026, 12:00:00 PM | 100% | 1 | 114ms |
| 10/1/2026, 2:00:00 PM | 100% | 1 | 105ms |
| 10/1/2026, 4:00:00 PM | 100% | 1 | 103ms |
| 10/1/2026, 6:00:00 PM | 100% | 1 | 106ms |
| 10/1/2026, 8:00:00 PM | 100% | 1 | 111ms |
| 10/1/2026, 10:00:00 PM | 100% | 1 | 106ms |
| 10/2/2026, 12:00:00 AM | 100% | 1 | 98ms |
| 10/2/2026, 2:00:00 AM | 100% | 1 | 116ms |
| 10/2/2026, 4:00:00 AM | 100% | 1 | 100ms |
| 10/2/2026, 6:00:00 AM | 100% | 1 | 117ms |
| 10/2/2026, 8:00:00 AM | 100% | 1 | 106ms |
| 10/2/2026, 10:00:00 AM | 100% | 1 | 95ms |
| 10/2/2026, 12:00:00 PM | 100% | 1 | 102ms |
| 10/2/2026, 2:00:00 PM | 100% | 1 | 105ms |
| 10/2/2026, 4:00:00 PM | 100% | 1 | 114ms |
| 10/2/2026, 6:00:00 PM | 0% | 1 | — |
| 10/2/2026, 8:00:00 PM | 0% | 1 | — |
| 10/2/2026, 11:00:00 PM | 0% | 1 | — |
| 10/3/2026, 12:00:00 AM | 0% | 1 | — |
| 10/3/2026, 2:00:00 AM | 0% | 1 | — |
| 10/3/2026, 4:00:00 AM | 0% | 1 | — |
| 10/3/2026, 6:00:00 AM | 0% | 1 | — |
| 10/3/2026, 8:00:00 AM | 0% | 1 | — |
| 10/3/2026, 10:00:00 AM | 0% | 1 | — |
| 10/3/2026, 12:00:00 PM | 0% | 1 | — |
| 10/3/2026, 2:00:00 PM | 0% | 1 | — |
| 10/3/2026, 4:00:00 PM | 0% | 1 | — |
| 10/3/2026, 6:00:00 PM | 0% | 1 | — |
| 10/3/2026, 8:00:00 PM | 0% | 1 | — |
| 10/3/2026, 11:00:00 PM | 0% | 1 | — |
| 10/4/2026, 1:00:00 AM | 0% | 1 | — |
| 10/4/2026, 3:00:00 AM | 0% | 1 | — |
| 10/4/2026, 5:00:00 AM | 0% | 1 | — |
| 10/4/2026, 7:00:00 AM | 0% | 1 | — |
| 10/4/2026, 9:00:00 AM | 0% | 1 | — |
| 10/4/2026, 1:00:00 PM | 0% | 1 | — |
| 10/4/2026, 3:00:00 PM | 0% | 1 | — |
| 10/4/2026, 5:00:00 PM | 0% | 1 | — |
| 10/4/2026, 7:00:00 PM | 0% | 1 | — |
| 10/4/2026, 9:00:00 PM | 0% | 1 | — |
| 10/5/2026, 2:00:00 AM | 0% | 1 | — |
| 10/5/2026, 8:00:00 AM | 0% | 1 | — |
| 10/5/2026, 9:00:00 AM | 0% | 1 | — |
| 10/5/2026, 11:00:00 AM | 0% | 1 | — |
| 10/5/2026, 1:00:00 PM | 0% | 1 | — |
| 10/5/2026, 2:00:00 PM | 0% | 1 | — |
| 10/5/2026, 4:00:00 PM | 0% | 1 | — |
| 10/5/2026, 6:00:00 PM | 0% | 1 | — |
| 10/5/2026, 8:00:00 PM | 0% | 1 | — |
| 10/5/2026, 10:00:00 PM | 0% | 1 | — |
| 10/6/2026, 1:00:00 AM | 0% | 1 | — |
| 10/6/2026, 2:00:00 AM | 0% | 1 | — |
| 10/6/2026, 5:00:00 AM | 0% | 1 | — |
| 10/6/2026, 11:00:00 AM | 0% | 1 | — |
| 10/6/2026, 1:00:00 PM | 0% | 1 | — |
- Availability
- 90
- Latency
- 100
- Security
- 49
- Transparency
- 49
- Activity
- 1
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- Name.com, Inc.
- Domain registered
- 2026-04-17
- Hosting network
- VERCEL-05
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Settlement totals · last payment 8/15/2026
Response schema
{
"additionalProperties": false,
"properties": {
"results": {
"items": {
"additionalProperties": false,
"properties": {
"arrivals": {
"items": {
"additionalProperties": false,
"properties": {
"direction": {
"enum": [
"Uptown",
"Downtown"
],
"type": "string"
},
"line": {
"type": "string"
},
"minutes": {
"minimum": 0,
"type": "integer"
}
},
"required": [
"line",
"direction",
"minutes"
],
"type": "object"
},
"type": "array"
},
"distance_feet": {
"minimum": 0,
"type": "integer"
},
"lat": {
"type": "number"
},
"lines": {
"items": {
"type": "string"
},
"type": "array"
},
"lng": {
"type": "number"
},
"name": {
"type": "string"
},
"walk_minutes": {
"minimum": 0,
"type": "integer"
}
},
"required": [
"name",
"distance_feet",
"walk_minutes",
"lines",
"arrivals",
"lat",
"lng"
],
"type": "object"
},
"type": "array"
}
},
"required": [
"results"
],
"type": "object"
}