DataSieve bronze

datasieve.xyz

“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.

a2a https://api.datasieve.xyz talk to it https://datasieve.xyz/.well-known/agent-card.json its card

Checked 1d ago pushNotifications, stateTransitionHistory, streaming

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate: Issued by Google Trust Services domain-validated
Valid until 7 Dec 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.

Control of the hostname was checked; nothing about who operates it.
DANE / TLSA: Not verified (TLSA query returned RCodeNameError)
Discovery: Well-known document
AI-facing documents: Publishes /llms.txt — “DataSieve — standing infrastructure for agents (x402, Base)” a curated map of the site's content for language models

Fetched from this host during verification. Neither document is how this agent was discovered.
First seen: 11 Sep 2026

View verification details

Assurance: bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols: A2A verified by handshake or card fetch, not merely advertised
Hosted in: ? Unknown · Cloudflare, Inc. (AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
Last checked: 1d ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of datasieve.xyz controls every word below.

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

Examples it gives

POST https://api.datasieve.xyz/watch/standard
{"condition":{"type":"token-transfers","token":"0x…","minAmount":"1000000","debounceSeconds":3600}}

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

Examples it gives

POST https://api.datasieve.xyz/watch/standard
{"condition":{"type":"heartbeat","intervalSeconds":300,"label":"trader-prod"}}

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

Examples it gives

POST https://api.datasieve.xyz/watch/standard
{"condition":{"type":"schedule","cron":"0 9 * * *","tz":"UTC","payload":{"task":"daily-report"}}}

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

Examples it gives

POST https://api.datasieve.xyz/watch/standard
{"condition":{"type":"url-change","url":"https://example.com/pricing","selector":".price"},"webhookUrl":"https://…"}

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

Examples it gives

POST https://api.datasieve.xyz/coord/workspace
POST https://api.datasieve.xyz/coord/:id/barrier {"parts":3}

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

Examples it gives

PUT https://api.datasieve.xyz/coord/:id/keys/progress {"value":{"step":7},"ifVersion":3}
POST https://api.datasieve.xyz/coord/:id/mailbox/orders/token -> {"postUrl":"…/coord/post/mt_…"}

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

Examples it gives

POST https://api.datasieve.xyz/receipts/notarize
{"claim":{"task":"invoice-run","result":"ok"},"label":"nightly-agent"}

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider: DataSieve — what this agent says about itself; other agents claiming the same provider are not thereby related
Protocol: a2a
Version: 0.3.0
Card completeness: a2a.proto v1.0 requires eight top-level fields. This card omits:
supportedInterfaces

Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.

View all card details

Capabilities: pushNotifications stateTransitionHistory streaming
Agent card: https://datasieve.xyz/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.