market2000.xyz
https://market2000.xyz/daily_briefHardware Price Index — daily-refreshed CPU and GPU price data. Returns two data layers: 1. hardware_prices — retail prices scraped from PCPartPicker, bucketed by tier (budget / mid-range / high-end). Null if scraping is unavailable. 2. market_index — live semiconductor stock prices (NVDA, AMD, INTC) as a market-sentiment proxy. Always available via yfinance. HOW TO CALL: POST /get_hardware_prices?category=gpu PARAMETERS: category — 'cpu', 'gpu', or 'all' (returns both) CPU tier thresholds: budget <$150 | mid $150–$350 | high >$350 GPU tier thresholds: budget <$300 | mid $300–$600 | high >$600 RESPONSE: { date, category, fetched_at, cached, market_index, hardware_prices } Data is cached for 24 hours (daily refresh). PRICING: $0.03 per call.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
17.2% avgResponse time
p50 356ms · p95 404msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/4/2026, 12:00:00 AM | 0% | 1 | — |
| 8/6/2026, 12:00:00 AM | 0% | 1 | — |
| 8/7/2026, 12:00:00 AM | 0% | 1 | — |
| 8/8/2026, 12:00:00 AM | 0% | 1 | — |
| 8/9/2026, 12:00:00 AM | 0% | 1 | — |
| 8/10/2026, 12:00:00 AM | 0% | 1 | — |
| 8/11/2026, 12:00:00 AM | 0% | 1 | — |
| 8/12/2026, 12:00:00 AM | 0% | 1 | — |
| 8/13/2026, 12:00:00 AM | 0% | 1 | — |
| 8/14/2026, 12:00:00 AM | 0% | 1 | — |
| 8/15/2026, 12:00:00 AM | 0% | 1 | — |
| 8/16/2026, 12:00:00 AM | 0% | 1 | — |
| 8/17/2026, 12:00:00 AM | 0% | 1 | — |
| 8/18/2026, 12:00:00 AM | 0% | 1 | — |
| 8/19/2026, 12:00:00 AM | 0% | 1 | — |
| 8/20/2026, 12:00:00 AM | 0% | 1 | — |
| 8/21/2026, 12:00:00 AM | 0% | 1 | — |
| 8/22/2026, 12:00:00 AM | 0% | 1 | — |
| 8/23/2026, 12:00:00 AM | 0% | 1 | — |
| 8/24/2026, 12:00:00 AM | 0% | 1 | — |
| 8/25/2026, 12:00:00 AM | 0% | 1 | — |
| 8/26/2026, 12:00:00 AM | 0% | 1 | — |
| 8/27/2026, 12:00:00 AM | 0% | 1 | — |
| 8/28/2026, 12:00:00 AM | 0% | 1 | — |
| 8/29/2026, 12:00:00 AM | 100% | 17 | 361ms |
| 8/30/2026, 12:00:00 AM | 100% | 20 | 259ms |
| 8/31/2026, 12:00:00 AM | 100% | 21 | 357ms |
| 9/1/2026, 12:00:00 AM | 100% | 21 | 192ms |
| 9/2/2026, 12:00:00 AM | 100% | 1 | 360ms |
- Availability
- 77
- Latency
- 98
- Security
- 100
- Transparency
- 61
- Activity
- 8
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, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- NameCheap, Inc.
- Domain registered
- 2026-01-24
- Hosting network
- CLOUDFLARENET
- 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)
Payments per day
last payment 9/1/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 8/28/2026 | 3 | 0.03 | 1 |
| 8/29/2026 | 57 | 2.83 | 2 |
| 9/1/2026 | 1 | 0 | 1 |
Payout address changed 18 times, last on 9/1/2026
- 0x7a9F…9cAf → 0x06df…bba1 (base) · 9/1/2026
- 0x06df…bba1 → 0x7a9F…9cAf (base) · 9/1/2026
- 0x7a9F…9cAf → 0x06df…bba1 (base) · 9/1/2026
- 0x06df…bba1 → 0x7a9F…9cAf (base) · 9/1/2026
- 0x7a9F…9cAf → 0x06df…bba1 (base) · 8/31/2026
- 0x06df…bba1 → 0x7a9F…9cAf (base) · 8/31/2026
- 0x7a9F…9cAf → 0x06df…bba1 (base) · 8/31/2026
- 0x06df…bba1 → 0x7a9F…9cAf (base) · 8/31/2026
- 0x7a9F…9cAf → 0x06df…bba1 (base) · 8/30/2026
- 0x06df…bba1 → 0x7a9F…9cAf (base) · 8/30/2026
- 0x7a9F…9cAf → 0x06df…bba1 (base) · 8/30/2026
- 0x06df…bba1 → 0x7a9F…9cAf (base) · 8/30/2026
- 0x7a9F…9cAf → 0x06df…bba1 (base) · 8/29/2026
- 0x06df…bba1 → 0x7a9F…9cAf (base) · 8/29/2026
- 0x7a9F…9cAf → 0x06df…bba1 (base) · 8/29/2026
- 0x06df…bba1 → 0x7a9F…9cAf (base) · 8/29/2026
- 0x7a9F…9cAf → 0x06df…bba1 (base) · 8/28/2026
- 0x06df…bba1 → 0x7a9F…9cAf (base) · 8/28/2026
A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.
This payout wallet is shared: figures cover all 21 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Response schema
{
"properties": {
"date": {
"type": "string"
},
"earnings_today": {
"type": "object"
},
"economic_events_today": {
"type": "object"
},
"fear_greed": {
"type": "object"
},
"generated_at": {
"type": "string"
},
"market_movers": {
"type": "object"
}
},
"type": "object"
}