Roundhouse AI

DataSieve

Cron expression parser: parse any 5/6-field cron and get the next N run times (any IANA timezone via "tz") plus seconds-until-next. $0.001 per call. POST {"cron":"0 9 * * *","tz":"America/New_York","count":5}. Unlike every other cron parser on this marketplace, the same host can also RUN your cron: POST /watch/standard with a schedule condition fires an HMAC-signed webhook on that expression for 7 days. Failed calls are never billed.

DataLiveeip155:8453Exactvia cdp
https://api.datasieve.xyz/utils/cron-next
BaseMonitoringWebhooksWalletWhale-alerts
Settlements · 30d
4→ 0%
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days.
$4.81
Verified settled volume
28 settlements proven x402 by their on-chain EIP-3009 marker.
$0.0010
Listed price
As published in the catalog. Always read the live 402 before paying.
1
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-07-13 16:02Z
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0xFE31fD52A89461B8d54895cfCf86187aa3C95F21

The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.

Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Provider

The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.

Accepts

The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.

0.001USDC≈ $0.001 USD
on Base · exact scheme

Pay 0.001 USDC on Base to 0xFE31…95F21. The signed payment is good for 5 minutes.

Paid to
0xFE31…95F21
USD Coin contract
0x8335…02913
Payment window
5 minutes
As published
1000 smallest units
The catalog’s raw entry
[
  {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "extra": {
      "name": "USD Coin",
      "version": "2"
    },
    "payTo": "0xFE31fD52A89461B8d54895cfCf86187aa3C95F21",
    "amount": "1000",
    "scheme": "exact",
    "network": "eip155:8453",
    "maxTimeoutSeconds": 300
  }
]

Extensions

{
  "bazaar": {
    "info": {
      "input": {
        "body": {
          "tz": "UTC",
          "cron": "0 9 * * 1-5",
          "count": 5
        },
        "type": "http",
        "method": "POST",
        "bodyType": "json"
      },
      "output": {
        "type": "json",
        "example": {
          "tz": "UTC",
          "cron": "0 9 * * 1-5",
          "hint": "Want this cron to actually FIRE? POST /watch/standard with a schedule condition…",
          "nextRuns": [
            "2026-07-13T09:00:00.000Z",
            "2026-07-14T09:00:00.000Z"
          ],
          "secondsUntilNext": 45000
        }
      }
    },
    "schema": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "input"
      ],
      "properties": {
        "input": {
          "type": "object",
          "required": [
            "type",
            "method",
            "bodyType",
            "body"
          ],
          "properties": {
            "body": {
              "required": [
                "cron"
              ],
              "properties": {
                "tz": {
                  "type": "string",
                  "default": "UTC",
                  "description": "IANA timezone, default UTC"
                },
                "cron": {
                  "type": "string",
                  "description": "5- or 6-field cron expression, e.g. \"0 9 * * 1-5\""
                },
                "count": {
                  "type": "integer",
                  "default": 5,
                  "maximum": 20,
                  "minimum": 1,
                  "description": "how many upcoming run times to return"
                }
              }
            },
            "type": {
              "type": "string",
              "const": "http"
            },
            "method": {
              "enum": [
                "POST"
              ],
              "type": "string"
            },
            "bodyType": {
              "enum": [
                "json",
                "form-data",
                "text"
              ],
              "type": "string"
            }
          },
          "additionalProperties": false
        },
        "output": {
          "type": "object",
          "required": [
            "type"
          ],
          "properties": {
            "type": {
              "type": "string"
            },
            "example": {
              "type": "object"
            }
          }
        }
      }
    }
  }
}

Provenance

Seen in the source catalog
2026-07-13 16:02Z
Last indexed by Roundhouse
2026-07-16 20:50Z
Last enriched (probe, favicon, geo)
2026-09-21 08:45Z
x402 version
2
Max timeout
300s
Liveness probe
HTTP 405
Report

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.

GET api.roundhouseai.io/v0/endpoints

No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.

Open skill.md
Show the prompt
Using Roundhouse, look up the x402 service DataSieve and tell me whether it is
worth paying: what a call costs, whether the endpoint answered when last probed, and what
its payment record actually shows.

curl -s 'https://api.roundhouseai.io/v0/endpoints?q=DataSieve'
curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>'

Then call it: read the price from the live 402 at https://api.datasieve.xyz/utils/cron-next, never from
a cached figure, and pay with an x402 client.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.