2s.io/api/gov/district
As of 2026-09-14, 2s.io/api/gov/district on Base held 97.1% uptime across 35 reliability checks over the past 30 days, with only occasional misses. Responses came back sluggish at 755 ms average from a single EU vantage point (so this includes network distance to the endpoint) and it has held its advertised price steady at $0.0045. Its x402-trust grade is A (score 85.9 from a moderate sample, tracked for 92 days), so it currently looks safe to use.
The latest analysis recorded 1 warning for this endpoint.
This page is a cached snapshot (computed 2 hours ago, refreshed at least every 24h): it tells you what the verdict is, not why. What each flag says, which wallet or network it concerns and the evidence behind it is the paid trust report, re-probed live at the moment you ask.
A wallet payment page opens first; approve the USDC payment and the full JSON report loads right in your browser. Agents use the x402_trust_score MCP tool or POST /v1/x402-trust directly. Want a taste first? Read a free full sample report.
Resolve a US street address to its congressional district (119th Congress), state, and county, via the US Census Bureau geocoder. Returns the matched/normalized address, latitude/longitude, state (name + 2-letter abbreviation), county, and the district number within the state (null for at-large or non-voting delegate districts). The point-in-polygon district lookup is something an agent can't do from a sandbox. Pair it with the gov/congress.* endpoints to find the representatives once you have the state + district. Public domain, keyless.(Provider-supplied: an unverified claim, not checked by us. The trust grade above is our independent measurement.)
Latency is measured from a single EU vantage point; includes network round-trip distance to the endpoint; a geographically distant endpoint reads slower even when its server is fast, so it is only lightly weighted in the score.
Full observation record ▾
| Trust grade | A (score 85.9) |
| Recommendation | proceed |
| Confidence | 0.65, full-density (every probe in the 30-day window) |
| 30-day uptime | 97.1% |
| Avg latency (EU vantage) | 755 ms |
| Probes (30d) | 35 |
| Advertised price | $0.0045 USDC |
| Price stability (30d) | stable |
| Pay on Base | $0.0018 USDC · to 0x2b6D…32C5 ↗ |
| Pay on Solana | $0.0018 USDC · to TW6nta…yWhn ↗ |
| First seen | 2026-06-14 |
| Last probed | 2026-09-14 |
| Status | listed |
| Snapshot computed | 2026-09-14 20:03 UTC |
- ✓Live probe at decision time:
We re-check the endpoint the moment you ask (timestamped) and compute the score from all scores up until this moment, instead of this cached snapshot that may be up to 24h old. - ✓Instant snapshot refresh:
Every paid call also re-writes this cached snapshot, so the page, badge and card update immediately instead of waiting for the 24h cycle. - ✓Confidence band, full component breakdown & structured risk flags:
Exactly why the score is what it is, machine-readable. - ✓On-chain settlement proof:
Real USDC volume & distinct-payer count for the payTo wallet: is anyone actually paying it? - ✓90-day raw history:
Every listing/price/payTo change and probe result (viaPOST /v1/x402-history), up to 90 days back. - ✓The ranked better-scored alternatives:
The resource URLs, scores & prices we don't reveal above (viaPOST /v1/similar), if there are better alternatives available. - ✓Change & liveness alerts:
Get notified on payTo/price changes, spec regressions or downtime (viaPOST /v1/watch-endpoint-30d). Connect up to 10 Discord / Slack webhooks or poll regularly with bearer auth. Increases probe-density to every 5 minutes instead of the usual 30 for the watched endpoint.
... Simply give your agents the tools to do all of that for you, with a simple command
npx -y x402-trust-mcpPrefer HTTP? Call POST /v1/x402-trust directly (pay-per-call over x402, from $0.005).