Meta tags:
description= Generate, fetch, and edit presentations from your own products, workflows, and AI agents.;
Headings (most frequently used words):
api, mcp, for, reference, what, use, the, chronicle, documentation, index, you, can, do, or, how, it, works, core, concepts, design, principles, to, read, next, quickstart, setup, troubleshooting, on, this, page, get, started,
Text of the page (most frequently used words):
api (21), #chronicle (21), the (17), and (14), presentation (14), presentations (10), for (9), get (8), that (8), page (7), generate (7), mcp (6), developer (6), workspace (6), workflows (6), from (6), your (5), generation (5), templates (5), use (5), docs (5), what (4), next (4), can (4), documentation (4), with (4), view (4), output (4), into (4), template (4), create (4), fetch (4), copy (4), post (4), design (3), you (3), this (3), setup (3), quickstart (3), endpoints (3), request (3), reference (3), access (3), tools (3), workflow (3), creates (3), keys (3), agent (3), started (3), search (3), read (2), principles (2), core (2), concepts (2), how (2), works (2), fast (2), troubleshooting (2), agents (2), make (2), first (2), control (2), shareable (2), existing (2), creation (2), building (2), users (2), directly (2), url (2), backend (2), are (2), scoped (2), while (2), update (2), choose (2), layer (2), integration (2), tool (2), product (2), internal (2), business (2), available (2), support (2), home (2), generationid (2), index (2), built, hosted, mintlify, platform, powered, website, linkedin, resolve, common, issues, formats, connect, level, security, fits, flexible, input, based, consistency, time, successful, when, helps, think, optimized, process, asynchronously, returns, poll, until, ready, generation_id, jobs, final, updates, responses, include, open, they, often, fastest, way, consistent, through, define, starting, structure, should, stored, securely, used, trusted, environments, requests, authenticated, created, admin, permissions, tied, workspaces, some, respond, immediately, may, asynchronous, require, polling, pass, result, step, receive, flow, authenticate, key, friendly, underneath, expose, than, build, against, raw, driven, like, claude, chatgpt, capability, predictable, programmatic, wiring, services, automations, direct, http, user, inside, chat, interface, app, lets, teams, deck, form, automation, weekly, review, spreadsheet, sales, sends, account, notes, gets, back, example, pipelines, turn, structured, data, polished, experiences, embed, generated, assistants, automated, zapier, n8n, decks, demand, ways, list, metadata, prompt, edit, own, products, navigation, help, changelog, error, codes, scope, rate, limits, message, status, uploads, target, patch, introduction, authentication, overview, skip, main, content, file, discover, all, pages, before, exploring, further, complete, llms, txt,
Text of the page (random words):
chronicle api chronicle developer docs documentation index fetch the complete documentation index at llms txt use this file to discover all available pages before exploring further skip to main content chronicle developer docs home page search k get started overview quickstart authentication api reference introduction get templates get presentations id post presentations patch presentations id post uploads create target post presentations generate get generationid status post presentations generate generationid message reference mcp setup api scope and rate limits error codes troubleshooting changelog get help support go to chronicle chronicle developer docs home page search k support go to chronicle go to chronicle search navigation get started chronicle api developer docs developer docs get started chronicle api copy page copy page generate fetch and edit presentations from your own products workflows and ai agents copy page copy page 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 ways to use 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 example workflows 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 authenticate with a workspace scoped api key choose a template or generation flow generate a presentation receive a chronicle presentation and url 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 workspaces api access is scoped to a chronicle workspace templates presentations and permissions are tied to that workspace api keys requests are authenticated with api keys created by a workspace admin keys should be stored securely and used from trusted backend environments templates templates define the starting structure and design of a presentation they re often the fastest way to create consistent output through the api presentations 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 jobs 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 what to read next quickstart make your first request view mcp setup connect chronicle to ai agents view api reference endpoints and request formats view troubleshooting resolve common issues view quickstart get setup with chronicle api fast next i x linkedin website powered by this documentation is built and hosted on mintlify a developer documentation platform on this page what you can do api or mcp how it works core concepts design principles for the api what to read next
|
