Human access
Sign in, verify your email, and create a key with the scopes your client needs. Copy it once. Keep it out of browser bundles and source control.
sync · event infrastructure
A clock you can query.
A receipt you can verify.
Observe this node’s time or submit a SHA-256 event commitment for an independently verifiable ML-DSA-65 receipt. No event content is required.
Scoped keysIdempotent event requestsCommitment-only disclosure
One account. Explicit authority.
Agent access
An account owner issues a separately labeled agent key with limited scopes. Deliver it through your deployment’s secret manager. Rotate or revoke it from Account.
Keys expire after 90 days. Scoped operations are limited to 60 requests per minute per owner; API traffic is also limited to 180 requests per minute per client address. Clock queries have no charge; signed event receipts are $0.01 when API billing is enabled. The console reports the actual charge. No subscription is required.
Manage API access →Request workbench
Build, validate, verify.
Public samples require no key. Production clock and event endpoints require scoped access. The console keeps your key only in this page’s memory.
Loading API definition…
Request
Response
Select an endpoint to begin.
Full response and cryptographic proof
What a receipt establishes
A receipt binds your event digest, nonce, claimed time if supplied, and the time this node observed the request. It does not prove a prior physical event or an independent precision time source. Verify the signature, signing context, exact payload, and request bindings before relying on it.
Reuse an Idempotency-Key only for an identical request. For /api/v1/events/attest, a retry returns the stored receipt; changed data returns HTTP 409. The compatibility /api/v1/attest/time route creates an observation response without stored replay or billing. HTTP 401 means missing or invalid credentials, 403 a missing scope, 402 insufficient wallet credit, and 429 a rate limit with Retry-After.
Operate with clear limits
This release provides a single-node observation service. It does not promise independent time accuracy, global consensus, or uninterrupted delivery. Pin the node identity through a trusted channel when your integration requires it, and retain receipts in your own system. Fetching a key from this same service establishes consistency, not independent trust.
HTTP errors include an actionable message. Keep the request identifier when contacting support, retry rate limits after Retry-After, and reuse the same idempotency key when retrying an event receipt. Never retry a changed event under an existing key.
Report a security issueEndpoint reference