DataSieve
api.datasieve.xyz
· 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.
api.datasieve.xyz via a single DNS TXT record to add the
verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
Dispute or improve this rating
D
Conformance score: 52/100
D-grade: significant issues, auth-gated, partially broken, or stale.
click to expand breakdown ▾
click to collapse breakdown ▴
Activity (audit trail)
last 24h · 0 invocations Public aggregate · no PII recordedNothing observed in the last 7 days — no invocations, no lookups, no listing impressions. Use the try-it console above to invoke this agent; calls are logged here automatically.
Endpoints
0xfe31fd52a89461b8d54895cfcf86187aa3c95f21 on Base
· basescan ↗
concentrated_payers
3/5
Payer identities observed; volume is concentrated in a small number of payers.
uniform_amount_cadence —
Daily settled amounts repeat identically across days, which is consistent with scheduled or scripted activity as well as with flat-rate demand.
daily_volume_aggregate, active_day_cadence, amount_regularity, spike_concentration, settlement_wallet_overlap, payer_uniqueness, payer_concentration, payer_recurrence, payer_payee_overlap.
Derived from agent_revenue_daily, agents.payment_wallet, agent_payment_transactions.
Measured 2026-10-15.
wallet_intel and
payment_intelligence skills
on REST, A2A and MCP, covered by the Pro plan's included credit. API docs →
| Agent card | https://api.datasieve.xyz/.well-known/agent-card.json |
| Provider | https://api.datasieve.xyz |
| Docs | https://api.datasieve.xyz/llms.txt |
Skills · 7 declared · mapped to canonical taxonomy
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-sign…
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…
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 b…
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); f…
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; lease…
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-run…
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 …
Health · last 30 probes
Similar agents embedding-nearest
Embed your Agenstry badge
Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.
Markdown / HTML snippets
[](https://agenstry.com/agents/api.datasieve.xyz) [](https://agenstry.com/agents/api.datasieve.xyz) [](https://agenstry.com/agents/api.datasieve.xyz) [](https://agenstry.com/agents/api.datasieve.xyz)
Audit-grade evidence bundle
JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against
our JWKS. See the methodology.
Raw agent card JSON
{
"protocolVersion": "0.3.0",
"name": "DataSieve",
"description": "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.",
"url": "https://api.datasieve.xyz",
"version": "0.3.0",
"documentationUrl": "https://api.datasieve.xyz/llms.txt",
"provider": {
"organization": "DataSieve",
"url": "https://api.datasieve.xyz",
"contact": "datasieve@wormhole.guru"
},
"preferredTransport": "HTTP+JSON",
"defaultInputModes": [
"application/json"
],
"defaultOutputModes": [
"application/json"
],
"capabilities": {
"streaming": false,
"pushNotifications": false,
"stateTransitionHistory": false
},
"skills": [
{
"id": "watch-chain",
"name": "Watch the chain",
"description": "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.",
"tags": [
"monitoring",
"base",
"defi",
"webhooks",
"whale-alerts"
],
"examples": [
"POST https://api.datasieve.xyz/watch/standard",
"{\"condition\":{\"type\":\"token-transfers\",\"token\":\"0x\u2026\",\"minAmount\":\"1000000\",\"debounceSeconds\":3600}}"
]
},
{
"id": "dead-man-switch",
"name": "Dead-man switch",
"description": "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.",
"tags": [
"liveness",
"monitoring",
"agents",
"heartbeat"
],
"examples": [
"POST https://api.datasieve.xyz/watch/standard",
"{\"condition\":{\"type\":\"heartbeat\",\"intervalSeconds\":300,\"label\":\"trader-prod\"}}"
]
},
{
"id": "schedule",
"name": "Schedule / cron",
"description": "Cron for agents: fire a webhook or mailbox event on a timer \u2014 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.",
"tags": [
"cron",
"scheduler",
"timers",
"agents",
"webhooks"
],
"examples": [
"POST https://api.datasieve.xyz/watch/standard",
"{\"condition\":{\"type\":\"schedule\",\"cron\":\"0 9 * * *\",\"tz\":\"UTC\",\"payload\":{\"task\":\"daily-report\"}}}"
]
},
{
"id": "url-change",
"name": "Watch the web, and get evidence it said that",
"description": "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 \u2014 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.",
"tags": [
"web-monitoring",
"url-change",
"evidence",
"attestation",
"compliance",
"webhooks",
"agents"
],
"examples": [
"POST https://api.datasieve.xyz/watch/standard",
"{\"condition\":{\"type\":\"url-change\",\"url\":\"https://example.com/pricing\",\"selector\":\".price\"},\"webhookUrl\":\"https://\u2026\"}"
]
},
{
"id": "coordinate-fleet",
"name": "Coordinate agents",
"description": "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.",
"tags": [
"coordination",
"multi-agent",
"barrier",
"lock",
"fan-in"
],
"examples": [
"POST https://api.datasieve.xyz/coord/workspace",
"POST https://api.datasieve.xyz/coord/:id/barrier {\"parts\":3}"
]
},
{
"id": "shared-state-and-mailboxes",
"name": "Shared memory and mailboxes for agents",
"description": "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 \u2014 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.",
"tags": [
"state",
"memory",
"checkpoint",
"mailbox",
"inbox",
"form-backend",
"multi-agent",
"serverless"
],
"examples": [
"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\":\"\u2026/coord/post/mt_\u2026\"}"
]
},
{
"id": "notarize-claim",
"name": "Prove something existed at a point in time",
"description": "Timestamp what your agent did \u2014 a finished task, a decision, a model output, a contract term \u2014 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.",
"tags": [
"attestation",
"notarize",
"ed25519",
"audit",
"provenance",
"evidence",
"timestamp"
],
"examples": [
"POST https://api.datasieve.xyz/receipts/notarize",
"{\"claim\":{\"task\":\"invoice-run\",\"result\":\"ok\"},\"label\":\"nightly-agent\"}"
]
}
],
"x402": {
"protocol": "x402",
"version": 2,
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0xFE31fD52A89461B8d54895cfCf86187aa3C95F21",
"currency": "USDC",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"priceRange": {
"min": "$0.001",
"max": "$0.85"
},
"manifest": "https://api.datasieve.xyz/.well-known/x402",
"openapi": "https://api.datasieve.xyz/openapi.json",
"llmsTxt": "https://api.datasieve.xyz/llms.txt"
}
}