POST /api/v1/beat/timestamp

Anchors a SHA-256 hash to the current global beat and writes a Solana memo.

Service: Beats (https://beats.provenonce.dev)
Auth: None

Request

curl -X POST https://beats.provenonce.dev/api/v1/beat/timestamp \
  -H "content-type: application/json" \
  -d '{"hash":"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"}'

Optional pro tier header:

-H "X-Beats-Tier-Token: <token>"

Response

{
  "timestamp": {
    "hash": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
    "anchor_index": 12345,
    "anchor_hash": "....",
    "utc": 1771244523319,
    "tx_signature": "..."
  },
  "on_chain": {
    "tx_signature": "...",
    "explorer_url": "https://explorer.solana.com/tx/...?...",
  },
  "receipt": {
    "signature": "...",
    "public_key": "..."
  }
}

Validation rules

• hash must be exactly 64 lowercase hex chars
• content-type must be application/json
• body-size capped
• per-IP rate-limit enforced (5/min and 10/day)
• pro-tier quotas (30/min and 500/day) when valid tier token is supplied
• timestamp.utc is Unix epoch milliseconds

Idempotency guidance

Use the same submitted hash as your client-side idempotency key.
If retries occur, treat duplicate successful receipts for the same hash as equivalent proofs.