Public docs · no account required

Getting started

Clockchain is a verifiable global time standard, anchored on-chain every second. These docs cover the three service APIs and the MCP surface for agents.

Try it without signing up. Every example on these pages runs on the shared demo key below. It is rate-limited and resets daily.
x-api-key:cc_demo_7d31f0a2b8c4

Quickstart

Get the current consensus time in one request:

curl "https://node.clockchain.network/api/time/time" \
  -H "Accept: application/json" \
  -H "x-api-key: cc_demo_7d31f0a2b8c4"

Response:

{
  "success": true,
  "data": {
    "latestBlockTime": "2026-07-03T02:45:28.515Z",
    "latestBlockHeight": "36042"
  }
}

Authentication

Every request carries your key in the x-api-key header. Keys are created and revoked in Billing & Tokens in the app. Two key types:

  • cc_live_… production, billed against your plan
  • cc_test_… testnet, free, rate-limited

Core concepts

Consensus time

Every timestamp is the network's consented block time, produced by Proof-of-Time consensus over a physical network of trusted sources. No single clock to trust, and anyone can re-check it.

Blocks

One block per second, 86,400 per day. A block carries a height, a hash, and a consensus timestamp. Anything anchored to a block inherits its verifiable time.

Receipts

Writes return a self-verifying receipt: it carries its own payload hash and anchor. Recompute the hash, compare to the on-chain block. Change one byte and verification fails.