ChainRecorder API

Name: ChainRecorder API API
Brand: ChainRecorder API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecurityComplianceapiKey2 EndpointsREST

For Agents

Anchor a file's cryptographic hash on chain to produce a timestamped tamper-evident record, and list previously recorded hash chains.

Quickstart

Get started with ChainRecorder API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"record a file hash on the blockchain"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with ChainRecorder API API.

Submit a file to be hashed and recorded on chain via ChainRecorder

Chain a new entry to an existing hash chain to maintain a verifiable sequence

Read every hash chain previously recorded against the account

Generate audit-ready proof-of-existence records without running blockchain infrastructure

Use Cases

GET STARTED

Start building with ChainRecorder API API

Explore with Jentic

View OpenAPI Document

Use for: I need to timestamp a contract PDF on the blockchain, Record a file hash so I can prove later that it existed today, Retrieve all hash chains my account has recorded, Chain a new daily report to an existing hash chain

Not supported: Does not store or retrieve the underlying file contents, run smart-contract execution, or sign documents — use for hash-anchoring and chain-listing operations only.

Jentic publishes the only available OpenAPI document for ChainRecorder API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for ChainRecorder API, keeping it validated and agent-ready. ChainRecorder is a blockchain timestamping service that records the hash of a file on chain, producing a tamper-evident proof that the document existed at a specific time. The two-endpoint API lets a client submit a file or hash to be chained and read back the full list of previously recorded hash chains.

★ Document Proof of Existence

Record a tamper-evident proof that a contract, report, or design document existed at a particular time without disclosing its contents. POST /files submits the file (or its precomputed hash) and ChainRecorder anchors it on chain, returning the chain reference. Used by legal, compliance, and IP teams who need an external timestamp authority that doesn't depend on a single internal clock.

Call POST /files with the document hash and label, then store the returned chain identifier alongside the document record

Append-Only Audit Log

Maintain an append-only log of internal events by chaining each new event hash on top of the previous one. POST /files extends an existing chain so any later tampering with intermediate entries breaks the chain, and GET /hashes returns the full chain for offline verification. Useful for regulated workflows that need an externally-verifiable audit trail.

Each night call POST /files with the day's events bundle hash to extend the audit chain, then call GET /hashes to verify the chain length matches expectations

Compliance Evidence Pack

Produce evidence packs for an external auditor that include cryptographic proof a record was created on a particular date. GET /hashes returns every chain ChainRecorder has recorded for the account so the audit pack can include the chain identifiers, timestamps, and the corresponding file hashes. Auditors verify the proof out of band against the public chain.

Call GET /hashes for the period under review and export the result as the timestamping section of the evidence pack

AI Agent Document Anchoring via Jentic

An agent finalising a contract draft is asked to 'anchor this version on chain so the counterparty can verify the timestamp'. Through Jentic, the agent searches for a record-file-hash operation, loads the input schema, and calls /files with credentials drawn from the Jentic vault. The agent returns the chain reference without the developer wiring custom X-ThirdParty-Token handling.

Use Jentic to search 'record a file hash on the blockchain', load the operation backed by POST /files, and execute it with the document SHA-256

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for chainrecorder api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/files

Chain a file or hash to the blockchain

GET

/hashes

List all recorded hash chains for the account

POST

/files

Chain a file or hash to the blockchain

GET

/hashes

List all recorded hash chains for the account

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ChainRecorder X-ThirdParty-Token values are stored encrypted in the Jentic vault and added to the request header at execution time. Agents receive scoped access only — the raw token never enters the agent's context window or prompt history.

Intent-based discovery

Agents search Jentic by intent (e.g., 'record a file hash on the blockchain' or 'list my recorded hash chains') and Jentic returns the matching ChainRecorder operation with its input schema, so the agent calls the right endpoint without scraping the docs.

Time to first call

Direct ChainRecorder integration: 1-2 hours for token handling, multipart upload, and result parsing. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Alchemy API

EVM blockchain infrastructure for verifying ChainRecorder anchors against the underlying chain

Use Alchemy alongside ChainRecorder when an agent needs to independently confirm an anchor by reading the underlying chain transaction

Alternative

Tatum API

Multi-chain blockchain API that can record arbitrary data, including hashes, across many chains

Choose Tatum when the integration needs cross-chain anchoring or self-managed chain selection; choose ChainRecorder for the simplest hosted timestamping flow

Complementary

MISP API

Threat-intel platform that can store and share indicator hashes alongside ChainRecorder anchors

Pair MISP with ChainRecorder when an agent needs both a private threat-intel record and a public on-chain timestamp for the same hash

FAQs

Specific to using ChainRecorder API API through Jentic.

Why is there no official OpenAPI spec for ChainRecorder API?

ChainRecorder does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ChainRecorder API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the ChainRecorder API use?

The API uses an API token passed in the X-ThirdParty-Token request header. Through Jentic, the token lives in the Jentic vault and is added to outgoing requests at execution time so it never enters the agent's prompt or context window.

Can I anchor a file on the blockchain through the ChainRecorder API?

Yes. POST /files accepts the file (or its precomputed hash) and label and returns the chain reference once the hash is anchored. Pair it with GET /hashes to confirm later that the chain still contains the entry exactly as recorded.

What are the rate limits for the ChainRecorder API?

Limits are tied to the ChainRecorder plan attached to your token rather than published as a single number in the spec. Watch for 429 responses with Retry-After headers, especially when timestamping a backlog of historical files in one batch.

How do I record a document hash on chain through Jentic?

Search Jentic for 'record a file hash on chain', load the operation backed by POST /files, and execute it with the file (or its SHA-256) and an identifying label. Jentic injects the X-ThirdParty-Token so the agent receives the typed chain reference back.

How do I retrieve every hash chain my account has recorded?

Call GET /hashes. It returns every chain previously recorded against the authenticated token, including each chain's identifier, timestamp, and entries, so audit and evidence-pack tooling can pull the data without scraping the ChainRecorder web UI.