sheaf
● Livegoldencalf.workers.dev
Self-contained verifiable Sheaf bundle for one event: full signed envelope + Merkle inclusion proof + on-chain anchor reference + issuer public key. Verify offline with npx @sheafhq/verify + any Base RPC. Only returned after the event's epoch is anchored; otherwise 409 'not yet anchored' with no payment taken.
Claim this service- Price
- $0.001
- Asked in its payment challenge
- Chain
- Base
- Paid in
- USDC
- Live
- 3 of 3 checks
Endpoint
$0.001 asked in its payment challenge on 14 Nov 2026
- chain_idpath, requiredsmoke-test-1Chain identifier the event lives in (same chain_id the recorder was writing to).
- seqpath, required0Sequence number of the event within its chain (non-negative integer, as a string in the URL).
curl -i 'https://sheaf-recorder.goldencalf.workers.dev/bundle/smoke-test-1/0'
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/sheaf-recorder.goldencalf.workers.dev
Recent checks
- Median response
- 804 ms
- Last checked
- 14 Nov, 15:25 UTC
Our probes look for a payment challenge. They don't test payment or delivery.
All 3 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 14 Nov, 15:25 UTC | Live | 402 | 804ms |
| 13 Nov, 03:20 UTC | Live | 402 | 1032ms |
| 11 Nov, 12:26 UTC | Live | 402 | 723ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 14 Nov, 15:25 UTC, it returned HTTP 402 or another detected payment-challenge signal.
What payment terms does sheaf advertise?
The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.
Something wrong on this page? Tell us.