hypernatt.com
https://hypernatt.com/api/m2m/swap/quoteShares a payout wallet with 6 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
USD Coin
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
99.3% avgResponse time
p50 308ms · p95 334msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/6/2026, 12:00:00 AM | 100% | 17 | 312ms |
| 9/7/2026, 12:00:00 AM | 100% | 15 | 98ms |
| 9/8/2026, 12:00:00 AM | 100% | 21 | 98ms |
| 9/9/2026, 12:00:00 AM | 100% | 21 | 97ms |
| 9/10/2026, 12:00:00 AM | 100% | 15 | 97ms |
| 9/11/2026, 12:00:00 AM | 100% | 9 | 97ms |
| 9/12/2026, 12:00:00 AM | 100% | 9 | 97ms |
| 9/13/2026, 12:00:00 AM | 100% | 16 | 97ms |
| 9/14/2026, 12:00:00 AM | 100% | 16 | 206ms |
| 9/15/2026, 12:00:00 AM | 100% | 15 | 315ms |
| 9/16/2026, 12:00:00 AM | 100% | 16 | 317ms |
| 9/17/2026, 12:00:00 AM | 93% | 15 | 311ms |
| 9/18/2026, 12:00:00 AM | 100% | 13 | 320ms |
| 9/19/2026, 12:00:00 AM | 100% | 13 | 314ms |
| 9/20/2026, 12:00:00 AM | 100% | 13 | 318ms |
| 9/21/2026, 12:00:00 AM | 100% | 13 | 316ms |
| 9/22/2026, 12:00:00 AM | 100% | 12 | 318ms |
| 9/23/2026, 12:00:00 AM | 100% | 13 | 315ms |
| 9/24/2026, 12:00:00 AM | 100% | 13 | 314ms |
| 9/25/2026, 12:00:00 AM | 100% | 14 | 319ms |
| 9/26/2026, 12:00:00 AM | 100% | 15 | 317ms |
| 9/27/2026, 12:00:00 AM | 100% | 14 | 310ms |
| 9/28/2026, 12:00:00 AM | 100% | 13 | 304ms |
| 9/29/2026, 12:00:00 AM | 100% | 13 | 300ms |
| 9/30/2026, 12:00:00 AM | 100% | 13 | 301ms |
| 10/1/2026, 12:00:00 AM | 100% | 13 | 299ms |
| 10/2/2026, 12:00:00 AM | 100% | 13 | 305ms |
| 10/3/2026, 12:00:00 AM | 100% | 14 | 302ms |
| 10/4/2026, 12:00:00 AM | 100% | 11 | 303ms |
| 10/5/2026, 12:00:00 AM | 86% | 7 | 299ms |
- Availability
- 100
- Latency
- 100
- Security
- 99
- Transparency
- 49
- Activity
- 11
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
- x402-express
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- Porkbun LLC
- Domain registered
- 2026-02-09
- Hosting network
- GOOGL-2
- 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/30/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 9/6/2026 | 4 | 0 | 3 |
| 9/8/2026 | 2 | 0 | 2 |
| 9/9/2026 | 2 | 0 | 2 |
| 9/11/2026 | 3 | 0 | 3 |
| 9/12/2026 | 2 | 0 | 2 |
| 9/13/2026 | 1 | 0 | 1 |
| 9/14/2026 | 5 | 0.01 | 3 |
| 9/15/2026 | 1 | 0 | 1 |
| 9/16/2026 | 6 | 0.01 | 3 |
| 9/17/2026 | 2 | 0 | 2 |
| 9/19/2026 | 1 | 0 | 1 |
| 9/20/2026 | 3 | 0 | 3 |
| 9/21/2026 | 3 | 0 | 3 |
| 9/22/2026 | 4 | 0 | 4 |
| 9/23/2026 | 4 | 0 | 3 |
| 9/24/2026 | 3 | 0 | 3 |
| 9/25/2026 | 3 | 0 | 2 |
| 9/26/2026 | 2 | 0 | 2 |
| 9/27/2026 | 1 | 0 | 1 |
| 9/28/2026 | 1 | 0 | 1 |
| 9/30/2026 | 3 | 0 | 3 |
Payout address changed 1 time, last on 8/8/2026
- 0xb730…9886 → 0x5a78…9cf9 (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.
This payout wallet is shared: figures cover all 7 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Response schema
{
"additionalProperties": true,
"properties": {
"error": {
"type": "string"
},
"execution_readiness": {
"additionalProperties": true,
"type": "object"
},
"instructions": {
"additionalProperties": true,
"type": "object"
},
"next_step": {
"additionalProperties": true,
"type": "object"
},
"quote": {
"additionalProperties": true,
"type": "object"
},
"success": {
"type": "boolean"
},
"wallet_onboarding_v1": {
"additionalProperties": true,
"type": "object"
}
},
"required": [
"success"
],
"type": "object"
}