agents.x402stock.xyz
https://agents.x402stock.xyz/api/v1/archive/:feedUse to read one immutable archived day of a feed (sol.jlp, hl.perps, prestocks.markets, scores.squeeze, …): the exact payload the live endpoint returned that day, plus provenance (observed/captured/ingested timestamps + a content hash proving contemporaneous capture). Defaults to latest; ?date=YYYY-MM-DD for a past day, ?entity= on multi-entity feeds. From x402stock
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 1431ms · p95 3372msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 7/25/2026, 12:00:00 AM | 100% | 1 | 1399ms |
| 7/26/2026, 12:00:00 AM | 100% | 1 | 1602ms |
| 7/27/2026, 12:00:00 AM | 100% | 1 | 1627ms |
| 7/28/2026, 12:00:00 AM | 100% | 1 | 1351ms |
| 7/29/2026, 12:00:00 AM | 100% | 1 | 1391ms |
| 7/30/2026, 12:00:00 AM | 100% | 1 | 5418ms |
| 7/31/2026, 12:00:00 AM | 100% | 1 | 2562ms |
| 8/1/2026, 12:00:00 AM | 100% | 1 | 1390ms |
| 8/2/2026, 12:00:00 AM | 100% | 1 | 1489ms |
| 8/3/2026, 12:00:00 AM | 100% | 1 | 2019ms |
| 8/4/2026, 12:00:00 AM | 100% | 1 | 1491ms |
| 8/5/2026, 12:00:00 AM | 100% | 1 | 1567ms |
| 8/6/2026, 12:00:00 AM | 100% | 1 | 1500ms |
| 8/7/2026, 12:00:00 AM | 100% | 1 | 1466ms |
| 8/8/2026, 12:00:00 AM | 100% | 1 | 1471ms |
| 8/9/2026, 12:00:00 AM | 100% | 1 | 1386ms |
| 8/10/2026, 12:00:00 AM | 100% | 1 | 2473ms |
| 8/11/2026, 12:00:00 AM | 100% | 1 | 2621ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 1708ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 1646ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 1722ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 2470ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 1414ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 1317ms |
| 8/18/2026, 12:00:00 AM | 100% | 1 | 372ms |
| 8/19/2026, 12:00:00 AM | 100% | 20 | 368ms |
| 8/20/2026, 12:00:00 AM | 100% | 21 | 358ms |
- Availability
- 100
- Latency
- 61
- Security
- 100
- Transparency
- 36
- Activity
- not yet measured
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
- GoDaddy.com, LLC
- Domain registered
- 2026-05-30
- Hosting network
- RS-1125
- 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)
Payout address changed 1 time, last on 8/8/2026
- 0x3cac…4548 → 0x10a1…a53b (base) · 8/8/2026
A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.
Only payments settled on chains and facilitators we index.