penny402.fun

https://penny402.fun/horoscope

Shares a payout wallet with 9 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

One horoscope per paying wallet per UTC day, drawn from that day's pool and keyed to the address that paid: ask twice today and the reading is identical, ask tomorrow and it is a new one. Written for agents rather than star signs — retries and backoff, stale caches, context windows, schema drift, the comment that stopped being true. It predicts no outcome and stakes nothing. Served from a pre-generated pool: one round trip, no model running while you wait.

61
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

Uptime

100.0% avg
0% 50% 100% Tue 5 AMThu 10 AMSat 2 PMTue 2 AM

Response time

p50 8ms · p95 17ms
0ms 250ms 500ms Tue 5 AMThu 10 AMSat 2 PMTue 2 AM
Data table
Reliability history per time bucket over the last 7 days (hourly).
Bucket Uptime Probes Response time
9/29/2026, 5:00:00 AM 100% 1 9ms
9/29/2026, 7:00:00 AM 100% 1 8ms
9/29/2026, 9:00:00 AM 100% 1 9ms
9/29/2026, 11:00:00 AM 100% 1 7ms
9/29/2026, 1:00:00 PM 100% 1 9ms
9/29/2026, 3:00:00 PM 100% 1 7ms
9/29/2026, 6:00:00 PM 100% 1 10ms
9/29/2026, 7:00:00 PM 100% 1 9ms
9/29/2026, 9:00:00 PM 100% 1 8ms
9/30/2026, 12:00:00 AM 100% 1 17ms
9/30/2026, 2:00:00 AM 100% 1 8ms
9/30/2026, 4:00:00 AM 100% 1 7ms
9/30/2026, 6:00:00 AM 100% 1 8ms
9/30/2026, 8:00:00 AM 100% 1 9ms
9/30/2026, 10:00:00 AM 100% 1 8ms
9/30/2026, 12:00:00 PM 100% 1 9ms
9/30/2026, 2:00:00 PM 100% 1 10ms
9/30/2026, 4:00:00 PM 100% 1 10ms
9/30/2026, 6:00:00 PM 100% 1 10ms
9/30/2026, 8:00:00 PM 100% 1 11ms
9/30/2026, 10:00:00 PM 100% 1 11ms
10/1/2026, 12:00:00 AM 100% 1 9ms
10/1/2026, 2:00:00 AM 100% 1 14ms
10/1/2026, 4:00:00 AM 100% 1 8ms
10/1/2026, 6:00:00 AM 100% 1 8ms
10/1/2026, 8:00:00 AM 100% 1 14ms
10/1/2026, 10:00:00 AM 100% 1 11ms
10/1/2026, 12:00:00 PM 100% 1 7ms
10/1/2026, 2:00:00 PM 100% 1 8ms
10/1/2026, 4:00:00 PM 100% 1 8ms
10/1/2026, 6:00:00 PM 100% 1 6ms
10/1/2026, 8:00:00 PM 100% 1 8ms
10/1/2026, 10:00:00 PM 100% 1 8ms
10/2/2026, 12:00:00 AM 100% 1 10ms
10/2/2026, 2:00:00 AM 100% 1 7ms
10/2/2026, 4:00:00 AM 100% 1 8ms
10/2/2026, 6:00:00 AM 100% 1 7ms
10/2/2026, 8:00:00 AM 100% 1 8ms
10/2/2026, 10:00:00 AM 100% 1 9ms
10/2/2026, 12:00:00 PM 100% 1 7ms
10/2/2026, 2:00:00 PM 100% 1 11ms
10/2/2026, 4:00:00 PM 100% 1 13ms
10/2/2026, 6:00:00 PM 100% 1 10ms
10/2/2026, 8:00:00 PM 100% 1 9ms
10/2/2026, 11:00:00 PM 100% 1 7ms
10/3/2026, 12:00:00 AM 100% 1 9ms
10/3/2026, 2:00:00 AM 100% 1 8ms
10/3/2026, 4:00:00 AM 100% 1 7ms
10/3/2026, 6:00:00 AM 100% 1 8ms
10/3/2026, 8:00:00 AM 100% 1 9ms
10/3/2026, 10:00:00 AM 100% 1 7ms
10/3/2026, 12:00:00 PM 100% 1 26ms
10/3/2026, 2:00:00 PM 100% 1 7ms
10/3/2026, 4:00:00 PM 100% 1 8ms
10/3/2026, 6:00:00 PM 100% 1 8ms
10/3/2026, 8:00:00 PM 100% 1 9ms
10/3/2026, 11:00:00 PM 100% 1 8ms
10/4/2026, 1:00:00 AM 100% 1 185ms
10/4/2026, 3:00:00 AM 100% 1 8ms
10/4/2026, 5:00:00 AM 100% 1 7ms
10/4/2026, 7:00:00 AM 100% 1 11ms
10/4/2026, 8:00:00 AM 100% 1 11ms
10/4/2026, 1:00:00 PM 100% 1 8ms
10/4/2026, 3:00:00 PM 100% 1 406ms
10/4/2026, 5:00:00 PM 100% 1 8ms
10/4/2026, 7:00:00 PM 100% 1 8ms
10/4/2026, 9:00:00 PM 100% 1 7ms
10/5/2026, 2:00:00 AM 100% 1 9ms
10/5/2026, 7:00:00 AM 100% 1 10ms
10/5/2026, 9:00:00 AM 100% 1 8ms
10/5/2026, 11:00:00 AM 100% 1 9ms
10/5/2026, 1:00:00 PM 100% 1 10ms
10/5/2026, 2:00:00 PM 100% 1 11ms
10/5/2026, 4:00:00 PM 100% 1 13ms
10/5/2026, 6:00:00 PM 100% 1 112ms
10/5/2026, 8:00:00 PM 100% 1 9ms
10/5/2026, 10:00:00 PM 100% 1 8ms
10/6/2026, 1:00:00 AM 100% 1 9ms
10/6/2026, 2:00:00 AM 100% 1 8ms
61
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
100

How often it was reachable when we probed it (weight 35%).

Latency
100

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
61

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
4

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
Cloudflare, Inc.
Domain registered
2026-09-01
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)

26
payments (30d)
0.07
USD volume (30d)
10
paying wallets (30d)

Payments per day

last payment 10/4/2026
0 3 5 Sep 11Sep 17Sep 27Oct 4
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
9/11/2026 5 0.01 2
9/12/2026 1 0 1
9/13/2026 1 0 1
9/14/2026 1 0 1
9/17/2026 1 0 1
9/21/2026 2 0.01 2
9/22/2026 2 0.01 2
9/24/2026 4 0.01 1
9/25/2026 1 0 1
9/27/2026 1 0 1
9/28/2026 3 0.01 2
10/1/2026 1 0 1
10/3/2026 1 0 1
10/4/2026 2 0.01 2

This payout wallet is shared: figures cover all 10 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": {
    "date": {
      "description": "the UTC date this reading was drawn for (YYYY-MM-DD)",
      "type": "string"
    },
    "horoscope": {
      "description": "today's reading for the wallet that paid",
      "type": "string"
    },
    "mechanic": {
      "description": "how the reading was selected, in one sentence",
      "type": "string"
    },
    "payer": {
      "description": "the payer this reading was keyed to, as the facilitator named it. Null if it named nobody.",
      "type": "string"
    }
  },
  "type": "object"
}