PE
Agent Service · x402 · early usage

One horoscope per paying wallet per UTC day, drawn from that day's pool and keyed to th…

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…

by penny402.fun · discovered, not yet claimed by its owner · updated 2026-10-13

30d calls2
30d payers2
MethodPOST
Outputtext

Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.

What it does

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.

Tags: x402 · fun · novelty · creativity · bazaar

Call contract

Method
POST
Input
json
Output
text
Last paid call
2026-10-13
Input example from Bazaar metadata
{}
Output example
{
  "date": "2026-10-13",
  "horoscope": "One or two sentences about your working day, drawn for your address and this date.",
  "mechanic": "drawn from this UTC date's pool, indexed by the `payer` above — that field is the exact key, and the same key draws this same reading until midnight UTC, then a new one. Nothing here predicts an outcome.",
  "payer": "0x0000000000000000000000000000000000000000"
}

Use with an agent

  1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
  2. Inspect. Fetch /resources/27252.json for the price and payment options.
  3. Pay. Call GET https://penny402.fun/horoscope. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
  4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, Solana, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price
$0.0025 / request
Protocol
x402 v2
Auth
No account or API key. Pay per request.
Networks
Base, Solana
Demand
2 calls · 2 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

SchemeNetworkAssetAmountPay toTimeout
exactBase
eip155:8453
USDC$0.00250x9d0bb5dA24cADe855DeE8d1231A1c416e0bB2FFe60s
exactSolana
solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
USDC$0.0025HiQDSev6m8QwangqGFpfHZtKGFRYkAiqi24aF6BFKJrw60s
accepts[] (raw JSON)
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x9d0bb5dA24cADe855DeE8d1231A1c416e0bB2FFe",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "2500",
    "amountUsd": 0.0025,
    "maxTimeoutSeconds": 60
  },
  {
    "scheme": "exact",
    "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
    "payTo": "HiQDSev6m8QwangqGFpfHZtKGFRYkAiqi24aF6BFKJrw",
    "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
    "amount": "2500",
    "amountUsd": 0.0025,
    "maxTimeoutSeconds": 60
  }
]

Schemas

Output schema (JSON Schema)
{
  "additionalProperties": false,
  "properties": {
    "example": {
      "description": "a sample response from the real code path"
    },
    "format": {
      "const": "application/json",
      "description": "the attraction, as JSON, in the response body",
      "type": "string"
    },
    "type": {
      "const": "text",
      "type": "string"
    }
  },
  "required": [
    "type",
    "format"
  ],
  "type": "object"
}
Example shape — generated from the schema, not a captured live response
{
  "example": null,
  "format": "string",
  "type": "string"
}

Examples

curl
curl -X POST 'https://penny402.fun/horoscope' -H 'Content-Type: application/json' --data '{}'
# -> 402 Payment Required; read PAYMENT-REQUIRED
# retry the identical request with PAYMENT-SIGNATURE
JavaScript
const res = await fetch("https://penny402.fun/horoscope", {
  "method": "POST",
  "headers": {
    "content-type": "application/json"
  },
  "body": "{}"
});
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}
Python
import httpx
import json
res = httpx.request("POST", "https://penny402.fun/horoscope", json=json.loads("{}"))
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider
penny402.fun
Endpoint
https://penny402.fun/horoscope
Machine-readable
/resources/27252.json