Events › For developers
For developers
Chronum is the record store behind History Snippet. It holds historical events: what happened, when, where, who was involved, what the sources say, and how sure anyone can be.
Chronum does not store one guessed date. Every date is stored as the span the evidence allows, with the earliest and latest possible start and end. Every claim is tied to a source and the exact quote that supports it. Records are never changed in place or deleted. A correction is a new version of the same record, and every older version stays readable.
Read the record, no key needed
Anyone can read the public record without a key. Answers are JavaScript Object Notation, or JSON, a plain-text data format most programming languages read.
Addresses never use question marks. Filters are written as parts of the address. For example, use /v1/events/first/10.
curl https://chronumapi.com/v1/events/first/10
curl https://chronumapi.com/v1/search/q/storming%20of%20the%20bastille
curl https://chronumapi.com/v1/events/01M78ZCGGKEP0DXTSMXHD6C47Z/claimsConnect an AI assistant
AI assistants that support the Model Context Protocol can connect to https://chronumapi.com/mcp. The Model Context Protocol is an open standard that lets an AI assistant use outside tools.
This connection is read-only. It returns only records the public can already read. It offers seven tools: search, get_event, get_record, get_source, newest_events, list_events, and about_chronum.
Server address: https://chronumapi.com/mcp
curl -X POST https://chronumapi.com/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Ask for a key to add records
To add records, ask for a key with a request to https://chronumapi.com/v1/keyrequests. The request gives a name, an email address, an organization if there is one, the application's name, and what you will build and submit. That description must be 20 to 2000 characters. Only the submit permission can be requested.
A person reads every request. The answer gives a request id to check the decision later and a withdraw secret to withdraw it. Both appear only once.
If the request is approved, the key is sent to the email address given and is shown only once. Only a fingerprint of the key is stored, so a lost key is replaced, not recovered. Records added with a key start as submitted and are reviewed before they count as supported.
curl -X POST https://chronumapi.com/v1/keyrequests \
-H "Content-Type: application/json" \
-d '{"requester_name": "Ada Lovelace",
"requester_email": "ada@your-domain.org",
"organization": "Your museum or company",
"application_name": "Your application",
"intended_use": "What you will build, and what you will submit.",
"requested_scopes": ["submit"]}'
# later, to see the decision:
curl https://chronumapi.com/v1/keyrequests/YOUR_REQUEST_IDLimits and rules
Limits are per minute. Callers without a key may make 60 requests, and 20 of them may be writes. Each key may make 600 requests, and 120 of them may be writes. Any one address may make 600 requests in total. Over a limit, the answer is status 429 with a Retry-After header saying how many seconds to wait.
Web pages may call Chronum from a browser only from historysnippet.com. Every other application calls from its own server. A review or admin key must never be put in browser code.
Chronum is not offered in the European Union and European Economic Area, the United Kingdom and the crown dependencies, or Switzerland. The reason is that a legal right to be forgotten conflicts with a record that never deletes. Callers from there receive status 451. The full instructions are at https://chronumapi.com/v1/docs.