clouatre.ca
https://clouatre.ca/v1/btc-regimeShares a payout wallet with 15 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
BTC spot regime check against a 7-day moving average gate (bull/bear, MA7, deviation pct, favor-entry/block-entry action).
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 20ms · p95 25msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 11/12/2026, 3:00:00 PM | 100% | 1 | 11ms |
| 11/15/2026, 2:00:00 AM | 100% | 1 | 26ms |
| 11/17/2026, 9:00:00 AM | 100% | 1 | 20ms |
- Availability
- 75
- Latency
- 100
- Security
- 100
- Transparency
- 61
- Activity
- 12
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 16% — 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
- Tucows.com Co.
- Domain registered
- 2008-10-02
- 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 11/18/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 10/25/2026 | 49 | 2.45 | 1 |
| 10/26/2026 | 4 | 0.2 | 2 |
| 10/27/2026 | 3 | 0.06 | 2 |
| 10/28/2026 | 4 | 0.16 | 1 |
| 10/29/2026 | 2 | 0.1 | 1 |
| 10/30/2026 | 6 | 0.16 | 1 |
| 10/31/2026 | 3 | 0.1 | 2 |
| 11/1/2026 | 8 | 0.06 | 5 |
| 11/2/2026 | 7 | 0.13 | 3 |
| 11/3/2026 | 9 | 0.11 | 1 |
| 11/4/2026 | 35 | 0.11 | 3 |
| 11/5/2026 | 41 | 0.46 | 4 |
| 11/6/2026 | 9 | 0.41 | 1 |
| 11/7/2026 | 3 | 0.02 | 3 |
| 11/8/2026 | 3 | 0.02 | 1 |
| 11/9/2026 | 2 | 0.01 | 2 |
| 11/11/2026 | 8 | 0.04 | 2 |
| 11/12/2026 | 1 | 0.01 | 1 |
| 11/15/2026 | 1 | 0 | 1 |
| 11/16/2026 | 2 | 0.01 | 1 |
| 11/17/2026 | 6 | 0.04 | 2 |
| 11/18/2026 | 12 | 0.09 | 5 |
Payout address changed 1 time, last on 11/4/2026
- 0x3025…cF73 → 0x1693…5671 (base) · 11/4/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 16 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Linked by wallet — likely same operator
On-chain agent identity and the x402 endpoint that shares its settlement wallet.
Response schema
{
"properties": {
"action": {
"enum": [
"favor-entry",
"block-entry"
],
"nullable": true,
"type": "string"
},
"availability": {
"enum": [
"available",
"unavailable"
],
"type": "string"
},
"closesSource": {
"enum": [
"client",
"kraken"
],
"type": "string"
},
"disclaimer": {
"type": "string"
},
"fetchedAt": {
"format": "date-time",
"type": "string"
},
"ma7": {
"nullable": true,
"type": "number"
},
"regime": {
"enum": [
"bull",
"bear",
"insufficient-data"
],
"type": "string"
},
"spotVsMa7Pct": {
"nullable": true,
"type": "number"
},
"unavailableReason": {
"enum": [
"not_reported",
"provider_error",
"stale"
],
"type": "string"
}
},
"required": [
"regime",
"closesSource",
"availability",
"disclaimer"
],
"type": "object"
}