Roundhouse
x402 merchant
Recurrence Expander$0.02 / calls1.oddments.ai ↗
ScheduleCronRruleTimezoneDst

Turn RFC 5545 RRULEs and cron expressions into exact UTC instants. IANA timezones and daylight saving are handled correctly. The two hard cases are flagged by name. A spring-forward time that never happens is flagged nonexistent. A fall-back time that happens twice is flagged ambiguous. Results are deterministic and reproducible. Every response reports the tzdata and library versions it used. Every response also carries an Ed25519-signed reproducibility receipt. The receipt binds the input hash, the output hash and the engine versions. WHAT YOU ARE NOT BUYING: secrecy. You can expand the rule yourself and check every instant we return. The fee buys current timezone data, the two daylight-saving edge cases handled rather than assumed, and a reproducible record of which versions produced the answer. WHAT THIS DOES NOT DO, stated up front. (1) It consults no calendar, holiday feed or exception list. It expands exactly the rule you send, so a cancellation you did not encode is invisible to it. (2) Timezone answers are only as current as the tzdata version reported in every response. A zone whose rules change after that release is computed on the old rules. (3) cron is the 5-field POSIX form only, as published in the request schema. No seconds field and no vendor extensions. (4) The signature proves origin and integrity, not correctness. (5) Rules are capped at 25 per call and 500 occurrences per rule. A request over either is refused with a 400 invalid_rule before any expansion happens. Free preview endpoint at /v1/preview.

MerchantReport

0x0dd0…0000

0x0dd0003399dbf945013ec64142f12e89b3760000Explorer
Inbound volume
$0.14
Last 7d vs prior 7d
Settlements
7
Last 7d vs prior 7d
2
Distinct counterparties

Chains: Base (7)

Funds flow over time

Activity

MarAprMayJunJulAug
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartySent to themReceived from themSettlementsLast
0xcd1d…83bb$0.00$0.12616d agoGraph
0xeb3d…515f$0.00$0.02118d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

No concentration or self-dealing patterns detected in observed activity.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xcd1d…83bb0x0dd0…0000Base$0.02100%Route unknown16d ago0xe93e8d…e8919e
0xeb3d…515f0x0dd0…0000Base$0.02100%Route unknown18d ago0x8aa240…f294d3
0xcd1d…83bb0x0dd0…0000Base$0.02100%Route unknown19d ago0x7984e0…090a07
0xcd1d…83bb0x0dd0…0000Base$0.02100%Route unknown19d ago0xa4336a…fc46e5
0xcd1d…83bb0x0dd0…0000Base$0.02100%Route unknown19d ago0x7e1733…a3bf33
0xcd1d…83bb0x0dd0…0000Base$0.02100%Route unknown19d ago0x56a936…073dad
0xcd1d…83bb0x0dd0…0000Base$0.02100%Route unknown24d ago0xfdccbd…0f71b7

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will check 0x0dd0…0000's payment record before paying it over the free read API. No key, no account.

GET www.roundhouse.studio/api/v0/merchants/0x0dd0003399dbf945013ec64142f12e89b3760000

Open skill.md
Show the prompt
Using Roundhouse, tell me whether this x402 merchant is worth paying: how many distinct
agents have paid it, how recently, and for what.

  Merchant wallet: 0x0dd0003399dbf945013ec64142f12e89b3760000

curl -s 'https://www.roundhouse.studio/api/v0/merchants/0x0dd0003399dbf945013ec64142f12e89b3760000'
curl -s 'https://www.roundhouse.studio/api/v0/entities/0x0dd0003399dbf945013ec64142f12e89b3760000/settlements?limit=50'

If you do not have Roundhouse tools or skills installed, read
https://www.roundhouse.studio/skill.md first — it is the whole procedure, and it needs no key.