DataSieve

Standing infrastructure for autonomous agents, paid per use over x402. Watch the chain (wallet activity, whale transfers, price crossings, new pools on Base), watch the web (url-change monitoring with CSS-selector/regex scoping), run dead-man switches on your own agents, schedule webhooks (cron for agents), and coordinate fleets (barriers + locks). Every event carries a signed Ed25519 observation receipt. Failed calls are never billed. No account; wallet is identity.

Skills

• Watch the chain
  Create a standing watch on Base: wallet activity, whale-sized token transfers, pool price crossings, or new liquidity pools. Events push to a webhook (HMAC-signed) or wait in a pollable mailbox.
  monitoringbasedefiwebhookswhale-alerts
• Dead-man switch
  Monitor your own agent. It pings a URL on a schedule; silence past the grace window fires an alert, a later ping fires recovery. An agent can arm its own switch mid-task with its own wallet.
  livenessmonitoringagentsheartbeat
• Schedule / cron
  Cron for agents: fire a webhook or mailbox event on a timer — every N seconds, at an absolute time, or on a cron expression. The payload is echoed back, so it becomes a scheduled wake-up for an agent with no server of its own.
  cronschedulertimersagentswebhooks
• Watch the web, and get evidence it said that
  Monitor any public web page for content changes, scoped by CSS selector or regex so markup churn does not false-positive. Polls on your interval (floor 300s); fires an HMAC-signed webhook or mailbox event when the scoped content actually changes. Every event carries a signed Ed25519 receipt that an independent party observed that page saying that at that time — the record you need when a vendor quietly rewrites its pricing or terms, when an SLA page showed degraded during your outage, or when an oracle input must be provable to someone who was not watching. A screenshot proves nothing; this verifies against a published key.
  web-monitoringurl-changeevidenceattestationcompliancewebhooksagents
• Coordinate agents
  Buy a coordination workspace, then use barriers (wake me when all N sub-agents finish, one webhook with every result) and locks (only one agent does this; leases auto-expire so a crash cannot deadlock the fleet). Ops are free after purchase.
  coordinationmulti-agentbarrierlockfan-in
• Shared memory and mailboxes for agents
  The same workspace is also somewhere to put things. KEYS are versioned checkpoints, so a run that dies to a rate limit or a budget cap resumes instead of re-running (and re-paying for) every prior step; ifVersion gives two instances of the same agent optimistic concurrency instead of silent clobbering. MAILBOXES carry arbitrary payloads between agents that are never alive at the same time. Minting a post-only URL for one mailbox gives you an endpoint that can append and nothing else — safe to hand a sub-agent, and safe to publish: drop it in a web page and a browser form posts orders, leads or messages straight into a mailbox you drain later, with no server, no database and no signup anywhere in it. CORS is open, so the page can read the reply.
  statememorycheckpointmailboxinboxform-backendmulti-agentserverless
• Prove something existed at a point in time
  Timestamp what your agent did — a finished task, a decision, a model output, a contract term — as an Ed25519-signed statement that this exact content reached a third party at that time. You cannot notarize your own claim; that is the whole point of a third party. Confidential? Hash it yourself and send only the digest: nothing is stored and we never see the content. Anyone verifies the signature against a published key without trusting you or us. Attests receipt-time and content-hash only, never that the claim is true.
  attestationnotarizeed25519auditprovenanceevidencetimestamp

How to call

https://api.datasieve.xyz

Listed in

Directories this entry was found in.