Tier 3: Enterprise M2M API Reference

The Rel-Time REST API is designed for high-throughput, Machine-to-Machine (M2M) integration. It allows enterprise systems to cryptographically anchor millions of zero-knowledge payload hashes into the Bitcoin Timechain via our continuous VDF engine.

Authentication & Rate Limits

All requests must include your secure API key in the HTTP header. Each payload hash consumes exactly 1 Hash Credit from your Virtual Fuel tank.

Authorization: Bearer rel_key_...

POST

/v1/anchor

1. Inject Payload Hash (M2M)

Submit a raw SHA-256 client hash to the Rel-Time API. Your hash will be instantly stamped against the live state of our continuous VDF engine. This consumes 1 Hash Credit from your API Key quota and immediately returns a Thermodynamic Proof while queuing the resulting Temporal Anchor (T-Index) for absolute Timechain finality. Because you are an M2M client, the protocol natively anchors the exact physical timestamp to guarantee absolute sequence ordering.

Request Body:

{ "client_hash": "dadd66a9783f2a893db61ef2f7b8ea49c5e7b4e33..." }

Response (200 OK):

{
  "status": "pending_finality",
  "thermodynamic_proof": "9238a45b2e000000000000000000000000...",
  "vdf_ticks": 15402918,
  "epoch_target": "Next Block (~10 mins)"
}

GET

/v1/proof/{client_hash}

2. Verify Finality (The Settlement)

Once the 10-minute Epoch passes and the Merkle Root collapses, query this endpoint to retrieve the permanent Bitcoin settlement data (TXID) and Merkle inclusion proofs.

Response (200 OK):

{
  "status": "settled",
  "client_hash": "dadd66a9783f2a893db61ef2f7b8ea49c5e7b4e33...",
  "settlement": {
    "bitcoin_block_height": 840112,
    "bitcoin_txid": "7f8b9c2a1d4e5f6...",
    "merkle_root": "a1b2c3d4e5f6g7h8...",
    "merkle_proof_path": [ "b9c2a1d4...", "f6g7h8i9..." ]
  }
}

GET

/v1/account/history

3. Retrieve Full History

Fetch a paginated ledger of all your anchored hashes. Once the batches are anchored on the Bitcoin Timechain, this endpoint will automatically return the enriched records including your merkle_proof_path and Bitcoin txid.

Query Parameters:

?page=1&limit=10

Response (200 OK):

{
  "history": [
    {
      "client_hash": "dadd66a9783f2a893db61ef2f7b8ea49c5e7b4e33...",
      "t_index": "9238a45b2e000000000000000000000000...",
      "status": "settled",
      "merkle_root": "a1b2c3d4e5f6g7h8...",
      "txid": "7f8b9c2a1d4e5f6...",
      "block_height": 840112,
      "merkle_proof_path": [ "b9c2a1d4...", "f6g7h8i9..." ]
    }
  ],
  "total": 1,
  "page": 1,
  "limit": 10
}

GET

/v1/account

4. View Account Matrix

Retrieves the total lifetime usage (hashes anchored) and remaining Virtual Fuel (Hash Credits) associated with your API key.

Response (200 OK):

{
  "tier": "Tier 3: Enterprise",
  "total_usage_count": 54201,
  "hash_credits": 1000000
}

Integration for Autonomous Agents

RelTime is designed to be directly addressable by highly capable language models and autonomous execution agents. If your agent supports dynamic tool creation via OpenAPI, simply supply it with our spec. Otherwise, inject the system prompt snippet below.

1. OpenAPI Specification

Point your agent frameworks (LangChain, OpenAI Function Calling, MCP) to our standard OpenAPI spec to dynamically infer capabilities:

https://api.rel-time.com/openapi.json

2. Agent System Prompt Snippet

If you are custom-crafting your agent's system prompt, append this to their instruction set:

You are equipped with the "RelTime" protocol.
Whenever you generate a critical synthetic output (e.g. executing a high-value trade,
hashing an AI model checkpoint, or committing a git push), you MUST cryptographically anchor 
a SHA-256 hash of that action to the thermodynamic timeline.

To do this:
Send a POST request to https://api.rel-time.com/v1/anchor
Header: 'Authorization': 'Bearer <YOUR_AGENT_TIER_4_KEY>'
Body: { "client_hash": "<SHA256_HASH_OF_YOUR_OUTPUT>" }

Record the returned 'thermodynamic_proof' and include it in your final response to the user.