ChainRecorder API

Name: ChainRecorder 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.

Install Jentic One Beta

Connect the ChainRecorder API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ChainRecorder API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fchainrecorder.com%2Fchainrecorder" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fchainrecorder.com%2Fchainrecorder" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ChainRecorder 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

GET STARTED

Start building with ChainRecorder API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ChainRecorder API for, with concrete tasks.

★ 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 your Jentic One instance. 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 Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring ChainRecorder by hand means learning its X-ThirdParty-Token header auth, pointing every request at the mainnet host, and adding the token to each call yourself. Through Jentic you install once, import ChainRecorder from the API Directory, store the token once, and your agent calls it.

Permission scoping

ChainRecorder anchors and lists hashes through flat operation paths rather than a per-resource URL, so scope the agent to the operations it needs, such as recording a file hash and listing hash chains. You choose which operations it may call, so anything beyond hash anchoring and chain listing is not included unless you add it.

Credential isolation

Your ChainRecorder X-ThirdParty-Token is stored once, encrypted, by your own Jentic One instance and injected into the request header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as '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 browsing the reference docs.

FAQs

Specific to using ChainRecorder 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 with Jentic One, the self-hosted execution layer.

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 your Jentic One instance 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.

Can I limit what my agent is allowed to do with the ChainRecorder API?

Yes. Because you run Jentic One yourself as the self-hosted execution layer, your own rules decide which ChainRecorder operations and credentials the agent may use. ChainRecorder exposes flat operation paths rather than per-resource URLs, so you scope the agent to only the operations it needs, such as recording a file hash with POST /files and listing recorded chains with GET /hashes. Anything beyond hash anchoring and chain listing stays unavailable to the agent unless you explicitly add it.