Skip to main content

Documentation Index

Fetch the complete documentation index at: https://chronicle.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

​
What you can do

  • create a presentation from a template
  • generate a presentation from a prompt
  • fetch an existing presentation
  • update presentation metadata
  • list the templates available to a workspace
  • internal tools that generate decks on demand
  • automated workflows in Zapier, Make, or n8n
  • AI assistants that create presentations for users
  • product experiences that embed Chronicle-generated output
  • pipelines that turn structured business data into polished presentations
  • A sales tool sends account notes to Chronicle and gets back a shareable presentation.
  • A workflow automation creates a weekly business review from a spreadsheet.
  • An internal app lets teams choose a template and generate a deck from a form.
  • An AI agent creates a presentation for a user inside a chat interface.

​
API or MCP?

Use the API for:

  • building a product integration
  • direct HTTP access
  • wiring Chronicle into backend services or automations
  • predictable programmatic control

Use MCP for:

  • AI tools like Claude or ChatGPT to use Chronicle as a capability
  • agent-driven presentation creation
  • expose Chronicle as a tool than build directly against raw endpoints
MCP is the agent-friendly layer, while the API is the integration layer underneath it.

​
How it works

  1. Authenticate with a workspace-scoped API key
  2. Choose a template or generation flow
  3. Generate a presentation
  4. Receive a Chronicle presentation and URL
  5. Fetch, update, or pass that result into the next step of your workflow
Some endpoints respond immediately, while generation workflows may be asynchronous and require polling.

​
Core concepts

API access is scoped to a Chronicle workspace.Templates, presentations, and permissions are tied to that workspace.
Requests are authenticated with API keys created by a workspace admin.Keys should be stored securely and used from trusted backend environments.
Templates define the starting structure and design of a presentation.They’re often the fastest way to create consistent output through the API.
A presentation is the final Chronicle output your workflow creates or updates. API responses include a presentation id and a url your users can open directly in Chronicle.
Generation workflows process the request asynchronously. The API returns a generation_id that you can poll until the presentation is ready.

​
Design principles for the API

When building with Chronicle, it helps to think of the API as optimized for:
  • Fast time to first successful presentation
  • Template-based creation for consistency
  • Generation workflows for flexible input
  • Shareable output that fits into existing tools
  • Workspace-level security and access control

Quickstart

Make your first request

MCP Setup

Connect Chronicle to AI agents

API Reference

Endpoints and request formats

Troubleshooting

Resolve common issues