Coord Workspace
by DataSieve in Onchain & crypto
One shared workspace for a fleet of agents: $0.25 for 7 days and 1000 ops, every op free after this one payment. BARRIER: N sub-agents each get an arrive URL; the last arrival fires ONE webhook carrying every result, a missed deadline names who never showed. LOCK: leases that expire, so a crash cannot deadlock the fleet. KEYS: checkpoints a dead run resumes from. MAILBOX: a post-only URL safe to publish — in a web form, or handed to one sub-agent — that can only append to that one mailbox.
https://api.datasieve.xyz/coord/workspace- Price
- $0.25
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 273 ms
- 334 ms slowest 5%
- Last check
- Passed
- 3 h ago, next any minute now
Reliability
How to call it
POST https://api.datasieve.xyz/coord/workspace
Each call costs $0.25 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://api.datasieve.xyz/coord/workspace
content-type: application/json
{}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
webhookUrl | string | No | optional default webhook for coordination events (barrier released/partial); omit to poll GET /coord/:id/events |
Example response
The provider's example. We can't check it without paying.
{
"expiresAt": "2026-07-18T00:00:00.000Z",
"id": "cw_01jzyx8k2mabcdefghjkmn",
"links": {
"events": "https://api.datasieve.xyz/coord/cw_01jzyx8k2mabcdefghjkmn/events",
"status": "https://api.datasieve.xyz/coord/cw_01jzyx8k2mabcdefghjkmn"
},
"opsCap": 1000,
"opsUsed": 0,
"secret": "whsec_...returned once: authorizes every barrier/lock op and signs your webhooks",
"state": "active"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.25.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.datasieve.xyz/coord/workspace' \
-H 'content-type: application/json' \
--data-raw '{}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://api.datasieve.xyz/coord/workspace' \
-H 'content-type: application/json' \
--data-raw '{}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.25 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.25" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.25 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.datasieve.xyz%2Fcoord%2Fworkspace&method=POST
const res = await pay("https://api.datasieve.xyz/coord/workspace", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.25 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.25"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://api.datasieve.xyz/coord/workspace",
json={},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Passed | 402 | 312 ms | $0.25 |
| 7 h ago | Passed | 402 | 298 ms | $0.25 |
| 11 h ago | Passed | 402 | 264 ms | $0.25 |
| 15 h ago | Passed | 402 | 332 ms | $0.25 |
| 20 h ago | Passed | 402 | 301 ms | $0.25 |
Show 10 older checks
| 24 h ago | Passed | 402 | 345 ms | $0.25 |
| 27 h ago | Passed | 402 | 317 ms | $0.25 |
| 31 h ago | Passed | 402 | 274 ms | $0.25 |
| 35 h ago | Passed | 402 | 254 ms | $0.25 |
| 39 h ago | Passed | 402 | 334 ms | $0.25 |
| 43 h ago | Passed | 402 | 382 ms | $0.25 |
| 47 h ago | Passed | 402 | 266 ms | $0.25 |
| 2 days ago | Passed | 402 | 267 ms | $0.25 |
| 2 days ago | Passed | 402 | 259 ms | $0.25 |
| 2 days ago | Passed | 402 | 239 ms | $0.25 |