{"schemaVersion":"drillso.agent.session.v1","scope":"node","resource":{"type":"shared-session","shareId":"B_Qh5EPwQq0l","title":"API Key 和 Bearer Token 是什么，有啥区别？","canonicalUrl":"https://drillso.com/en/share/sessions/B_Qh5EPwQq0l/api-key-%E5%92%8C-bearer-token-%E6%98%AF%E4%BB%80%E4%B9%88%EF%BC%8C%E6%9C%89%E5%95%A5%E5%8C%BA%E5%88%AB%EF%BC%9F-5af00ea5","agentUrl":"https://drillso.com/en/share/sessions/B_Qh5EPwQq0l/agent.json?node=api-key-%E5%92%8C-bearer-token-%E6%98%AF%E4%BB%80%E4%B9%88%EF%BC%8C%E6%9C%89%E5%95%A5%E5%8C%BA%E5%88%AB%EF%BC%9F-5af00ea5","ownerName":"pyth0nb3st","updatedAt":"2026-04-28T10:23:26.413Z"},"currentNode":{"id":"5af00ea5-abd9-4708-8efb-d4c3ff655b91","slug":"api-key-和-bearer-token-是什么，有啥区别？-5af00ea5","title":"API Key 和 Bearer Token 是什么，有啥区别？","type":"deck","url":"https://drillso.com/en/share/sessions/B_Qh5EPwQq0l/api-key-%E5%92%8C-bearer-token-%E6%98%AF%E4%BB%80%E4%B9%88%EF%BC%8C%E6%9C%89%E5%95%A5%E5%8C%BA%E5%88%AB%EF%BC%9F-5af00ea5","agentUrl":"https://drillso.com/en/share/sessions/B_Qh5EPwQq0l/agent.json?node=api-key-%E5%92%8C-bearer-token-%E6%98%AF%E4%BB%80%E4%B9%88%EF%BC%8C%E6%9C%89%E5%95%A5%E5%8C%BA%E5%88%AB%EF%BC%9F-5af00ea5","text":"{\n  \"style\": \"Neo-Retro Dev Deck / Pixel-Infographic Editorial\",\n  \"title\": \"API Key 和 Bearer Token 的区别\",\n  \"format\": \"presenter_slides\",\n  \"slides\": [\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"先别把它们都叫密钥\",\n      \"layout\": \"封面式构图，中央放两个像素风凭证卡片，一张写 API Key，一张写 Bearer Token，中间用不等号连接。标题大字置顶，副标语分散在卡片周围。\",\n      \"message\": \"API Key 和 Bearer Token 都是请求里的凭证，但表达的信息不同。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/dpxiybdctw7habj8vsuhky8g-6d315ad8341b9eff81970e5d8ed50baa.png\",\n      \"storageKey\": \"generated/drill/dpxiybdctw7habj8vsuhky8g-6d315ad8341b9eff81970e5d8ed50baa.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 1: 先别把它们都叫密钥\\nMain message: API Key 和 Bearer Token 都是请求里的凭证，但表达的信息不同。\\n\\nVisible text must be exactly these lines, with no extra words:\\n一个字符串\\n两种含义\\nAPI Key ≠ Bearer Token\\n\\nLayout:\\n封面式构图，中央放两个像素风凭证卡片，一张写 API Key，一张写 Bearer Token，中间用不等号连接。标题大字置顶，副标语分散在卡片周围。\\n\\nVisual style:\\n复古开发者手册感，网格纸背景，像素化接口元素，终端窗口边框，黑色主文字配少量高亮色。\\n\\nAdditional image direction:\\n制作一张技术讲解封面。画面中央是两个并排的像素风访问凭证卡片，左侧卡片标注 API Key，右侧卡片标注 Bearer Token，中间是醒目的不等号。背景是浅色工程网格纸，加入小型终端窗口、HTTP 请求碎片、像素箭头和微型锁图标。文字保持稀疏，突出“一个字符串，两种含义”。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 1,\n      \"visibleText\": [\n        \"一个字符串\",\n        \"两种含义\",\n        \"API Key ≠ Bearer Token\"\n      ],\n      \"visualStyle\": \"复古开发者手册感，网格纸背景，像素化接口元素，终端窗口边框，黑色主文字配少量高亮色。\",\n      \"speakerNotes\": \"开场先回应常见误解：很多初学者会觉得它们都是一个字符串，放进请求就行。但材料明确指出，它们在用途、设计目标、安全性和适用场景上都有明显区别。本页只建立核心悬念：不是看起来像不像，而是它们分别代表什么。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in the dominant art direction: Neo-Retro Dev Deck / Pixel-Infographic Editorial. Single slide only, finished presentation-ready composition.\\n\\nSlide topic: API Key 和 Bearer Token 的区别\\nCover-style composition. Light cream/off-white engineering notebook grid-paper background with subtle square grid lines. Retro developer-manual feel, slightly rebellious, playful, confident.\\n\\nVisible text must be EXACTLY these lines and nothing else:\\n一个字符串\\n两种含义\\nAPI Key ≠ Bearer Token\\n\\nTypography: huge bold geometric sans serif, black, slightly condensed. Make the first line largest, second line medium, third line as a strong headline statement. Keep all text readable and sparse. No extra words, no bullets, no captions, no watermarks.\\n\\nLayout: Title big at top. In the center, two side-by-side pixel-art credential cards with thick black borders and slight overlap / collage feel. Left card label: API Key. Right card label: Bearer Token. Between them, a large bold not-equal sign (= visually an inequality symbol) in black or hot pink. Surround with small spaced sub-phrase fragments from the visible text and tiny interface notes, but only the three required lines may be visible text; do not add any other readable text.\\n\\nVisual direction: technical explainer cover. Add small terminal-window frames, HTTP request fragments as abstract pixel shapes (not readable text), pixel arrows, micro lock icons, code-bracket motifs, browser/web execution hints, and subtle motion lines. Use strict palette: hot pink for agent/intelligence accents, bright yellow for code/tools, cyan/light blue for browser/execution, black for text/borders, cream background. Each main element should have one dominant color block. Thick black outlines, 8-bit / 16-bit inspired flat pixel art. Editorial composition with stacked modular blocks, intentional slight overlaps, horizontally aligned header bar feel. No gradients, no realistic photos, no soft shadows, no corporate clean minimalism.\\n\\nEnsure the slide feels like annotated engineering notes, not a generic infographic. Strong hierarchy, high contrast, high sensibility, coherent with NotebookLM / Kael style. No browser chrome, no extra logos, no signatures, no contact sheet, no multiple slides.\",\n      \"storageFileId\": \"dpxiybdctw7habj8vsuhky8g-6d315ad8341b9eff81970e5d8ed50baa\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"一句话理解\",\n      \"layout\": \"左右对照卡片。左侧是编号牌和应用图标，右侧是通行证和用户头像。中间用一条像素化分隔线区分。\",\n      \"message\": \"API Key 更像固定开发者编号，Bearer Token 更像登录后的临时通行证。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/i5ntrv4pbjdzsuhyc0eny2g6-f19ca1f0492caa7e7e153ad04d2e9a14.png\",\n      \"storageKey\": \"generated/drill/i5ntrv4pbjdzsuhyc0eny2g6-f19ca1f0492caa7e7e153ad04d2e9a14.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 2: 一句话理解\\nMain message: API Key 更像固定开发者编号，Bearer Token 更像登录后的临时通行证。\\n\\nVisible text must be exactly these lines, with no extra words:\\nAPI Key\\n固定开发者编号\\nBearer Token\\n临时通行证\\n\\nLayout:\\n左右对照卡片。左侧是编号牌和应用图标，右侧是通行证和用户头像。中间用一条像素化分隔线区分。\\n\\nVisual style:\\n像 90 年代软件说明书里的对照插图，平面像素图标，粗边框标签，少量荧光高亮。\\n\\nAdditional image direction:\\n制作左右对照式解释图。左侧显示一个应用窗口拿着固定编号牌，标签为 API Key 和 固定开发者编号；右侧显示一个用户头像拿着临时通行证，标签为 Bearer Token 和 临时通行证。中间用像素风竖线分隔，背景为浅色网格纸，加入小箭头和简洁标签，整体像开发者手册中的概念页。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 2,\n      \"visibleText\": [\n        \"API Key\",\n        \"固定开发者编号\",\n        \"Bearer Token\",\n        \"临时通行证\"\n      ],\n      \"visualStyle\": \"像 90 年代软件说明书里的对照插图，平面像素图标，粗边框标签，少量荧光高亮。\",\n      \"speakerNotes\": \"用材料中的生活类比帮助听众建立直觉：API Key 像系统发给你的固定开发者编号；Bearer Token 像用户登录后拿到的一张临时通行证。这里不要过度展开，只强调两者不是同一层面的东西：一个偏识别调用方，一个偏表示授权状态。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in the dominant style of a Neo-Retro Dev Deck / Pixel-Infographic Editorial. Single slide only. Background: light cream/off-white engineering notebook paper with subtle square grid lines, slightly off-register and hand-assembled feel. Strong black thick borders, flat colors, pixel-art illustration, 90s software manual vibe mixed with modern developer marketing, playful but clean and presentation-ready.\\n\\nSlide topic: compare API Key and Bearer Token in a simple visual analogy. Layout: left-right comparison with two large boxed panels. A pixelated vertical divider line in the center. Left panel: a small application window icon holding a fixed numbered badge/ID card, with a developer/app motif. Right panel: a user avatar icon holding a temporary pass/ticket, with a login/session motif. Use slight overlaps, arrows, and tiny pixel sparks for emphasis. Each panel should have one dominant color block: left panel with bright yellow accents for code/tool identity; right panel with hot pink accents for auth/session identity; use cyan for the central divider or supporting accents. Thick black outlines, flat shading only, no gradients, no soft shadows, no realistic rendering.\\n\\nTypography: huge bold geometric sans serif for the labels, black text, slightly condensed. Keep text minimal and readable. The only visible text in the entire slide must be exactly these four lines, and nothing else: \\nAPI Key\\n固定开发者编号\\nBearer Token\\n临时通行证\\nPlace the English title above the Chinese line inside each card, with clean hierarchy. No extra captions, no extra labels, no numbers, no watermarks, no logos, no UI browser chrome.\\n\\nComposition: editorial and balanced, like a polished developer manual page. Left side should feel like a fixed developer credential card; right side should feel like a temporary access pass after login. Add simple pixel icons and bold framed labels. Ensure the overall slide feels finished, confident, and cohesive with the template.\",\n      \"storageFileId\": \"i5ntrv4pbjdzsuhyc0eny2g6-f19ca1f0492caa7e7e153ad04d2e9a14\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"API Key 识别谁在调用\",\n      \"layout\": \"流程卡片：客户端带 X-API-Key 请求 API，服务端检查 Key 是否存在、有效、未禁用、未超配额，然后返回资源。\",\n      \"message\": \"API Key 主要用于识别应用、控制配额、限流和统计调用量。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/dd0geekizk0eoiy45zj1o4q0-8dfceea8addb5739e5507c19900b838b.png\",\n      \"storageKey\": \"generated/drill/dd0geekizk0eoiy45zj1o4q0-8dfceea8addb5739e5507c19900b838b.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 3: API Key 识别谁在调用\\nMain message: API Key 主要用于识别应用、控制配额、限流和统计调用量。\\n\\nVisible text must be exactly these lines, with no extra words:\\n识别应用\\n配额\\n限流\\n调用统计\\n\\nLayout:\\n流程卡片：客户端带 X-API-Key 请求 API，服务端检查 Key 是否存在、有效、未禁用、未超配额，然后返回资源。\\n\\nVisual style:\\n像素流程图，使用终端代码块样式展示 X-API-Key，服务端校验项以小型检测清单呈现。\\n\\nAdditional image direction:\\n制作一张 API Key 工作方式流程图。左侧是客户端小电脑图标，中间是一段简化请求卡片显示 X-API-Key，右侧是服务器机柜图标。服务器旁有四个小检测项：存在、有效、未禁用、未超配额。下方用小图标表示配额、限流、调用统计。布局清晰，像复古技术手册中的流程示意。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 3,\n      \"visibleText\": [\n        \"识别应用\",\n        \"配额\",\n        \"限流\",\n        \"调用统计\"\n      ],\n      \"visualStyle\": \"像素流程图，使用终端代码块样式展示 X-API-Key，服务端校验项以小型检测清单呈现。\",\n      \"speakerNotes\": \"解释 API Key 的定义：它是服务端分配给客户端的一串唯一字符串，用来识别谁在调用 API。材料列出的常见作用包括标识调用者身份、配额控制和限流、统计调用量、提供基础访问控制。也提醒它的局限：通常权限较粗粒度，泄露后容易被直接盗用，不能很好表达某个具体用户已经授权。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, landscape 1536x864, in the Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Off-white light cream engineering notebook background with subtle square grid lines. Thick black borders, stacked modular blocks, slight collage overlap, retro-futuristic developer manual feel, pixel-art icons, bold editorial hierarchy. Strict palette: hot pink, bright yellow, cyan/light blue, black, cream. No gradients, no photos, no soft shadows, no corporate minimalism.\\n\\nSlide topic in Chinese: API Key 识别谁在调用.\\n\\nThis is Slide 3 of a deck about API Key and Bearer Token differences, but only generate this single slide.\\n\\nVisible text must be exactly these four lines and nothing else anywhere on the slide:\\n识别应用\\n配额\\n限流\\n调用统计\\n\\nLayout:\\n- Main composition is a clear workflow flowchart like a retro technical manual.\\n- Left: a small pixel-art client computer icon in a box labeled only with the required visible text line? No extra labels outside the exact four lines. Use the icon and request flow visually, but do not add any extra readable words.\\n- Center: a simplified terminal-code style request card with bold monospaced text X-API-Key, presented inside a black-bordered rectangular code block. This is part of the visual; no other words are allowed.\\n- Right: a pixel-art server rack / server cabinet icon in a box.\\n- Between client and server: arrows showing request and response flow, with small motion chevrons and pixel sparks.\\n- Next to the server: a compact checklist panel with four tiny check items represented visually only, corresponding to existence, validity, not disabled, not over quota. Use small check icons and stamped squares; do not add extra readable words beyond the required four visible lines.\\n- Bottom row: four small icon tiles using pixel-art symbols to represent quota, rate limiting, and call statistics. These tiles should be colorful and editorial. The only text visible in the entire slide must be the exact four Chinese lines listed above, placed as the bottom captions under the tiles, one line per tile, in that exact order.\\n\\nTypography and placement:\\n- Make the four required Chinese lines large enough to be readable at presentation distance, but keep the rest of the slide mostly diagrammatic.\\n- Use bold black geometric sans for the Chinese lines, with slight condensed styling.\\n- Use a terminal/code block style for X-API-Key in monospaced black text on a pale yellow card.\\n- No extra titles, subtitles, legends, bullets, paragraph text, footer, source notes, or watermarks.\\n\\nIcon style:\\n- Pixel-art, 8-bit/16-bit inspired, flat colors, black outline.\\n- Client computer in cyan, server cabinet in hot pink, request card in yellow, flow arrows in black and cyan.\\n- Small utility icons for quota, rate limit, statistics: gauge, clock/stopwatch, bar chart, counter dots, etc.\\n\\nOverall composition should look like a polished retro developer slide: clean, balanced, dense enough to feel finished, but with intentional modular blocks and editorial rhythm.\\n\\nEnsure the slide looks like a single finished presentation slide, not a wireframe, not multiple slides, not a contact sheet.\",\n      \"storageFileId\": \"dd0geekizk0eoiy45zj1o4q0-8dfceea8addb5739e5507c19900b838b\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"Bearer Token 表示被授权做什么\",\n      \"layout\": \"登录授权时序图：用户登录，服务端返回 access token，之后请求带 Authorization: Bearer，服务端判断资源访问权限。\",\n      \"message\": \"Bearer Token 通常用于登录授权，能表达用户、过期时间和访问范围。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/rsmy7bq1hua9913upvslp5wq-83feb8006bb975d7015e611a61442cf3.png\",\n      \"storageKey\": \"generated/drill/rsmy7bq1hua9913upvslp5wq-83feb8006bb975d7015e611a61442cf3.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 4: Bearer Token 表示被授权做什么\\nMain message: Bearer Token 通常用于登录授权，能表达用户、过期时间和访问范围。\\n\\nVisible text must be exactly these lines, with no extra words:\\n登录后获得\\nAuthorization: Bearer\\n过期时间\\nscope\\n\\nLayout:\\n登录授权时序图：用户登录，服务端返回 access token，之后请求带 Authorization: Bearer，服务端判断资源访问权限。\\n\\nVisual style:\\n横向时序图，像素人物、认证服务器、资源服务器三列，使用发光令牌作为视觉中心。\\n\\nAdditional image direction:\\n制作一张 Bearer Token 登录授权时序图。左侧是用户和 App，中间是认证服务器，右侧是 API 资源服务器。箭头依次表示登录、返回 access token、携带 Authorization: Bearer 请求资源、校验权限后返回资源。令牌以发光像素卡片呈现，旁边标注过期时间和 scope。背景保持浅色网格与复古终端元素。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 4,\n      \"visibleText\": [\n        \"登录后获得\",\n        \"Authorization: Bearer\",\n        \"过期时间\",\n        \"scope\"\n      ],\n      \"visualStyle\": \"横向时序图，像素人物、认证服务器、资源服务器三列，使用发光令牌作为视觉中心。\",\n      \"speakerNotes\": \"解释 Bearer Token：它是持有即有效的访问令牌，谁拿着它谁就能用。材料指出它常出现在 OAuth 2.0、OpenID Connect、登录授权系统中。重点不只是识别调用方，而是表示某个用户或客户端已经完成认证，并获得某些资源访问权限。它通常支持过期时间和访问范围 scope，但也需要处理过期、刷新、撤销等机制。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Single slide only, not a contact sheet.\\n\\nTopic: Bearer Token 表示被授权做什么\\nDeck slide 4 of a Chinese-language presentation about API Key 和 Bearer Token 的区别.\\n\\nDominant art direction:\\n- Light cream/off-white background with subtle engineering notebook grid.\\n- Retro-futuristic developer editorial infographic, pixel-art meets startup deck.\\n- Thick black borders, modular boxes, slight overlaps, collage-like assembly.\\n- Strict palette: hot pink, bright yellow, cyan/light blue, black, cream/white.\\n- No gradients, no photos, no soft shadows, no corporate look.\\n- Strong typography hierarchy, bold geometric sans serif headline blocks.\\n- Pixel art icons and terminal/dev-tool motifs.\\n\\nLayout:\\n- Horizontal authorization sequence diagram across the slide, reading left to right.\\n- Left column: 用户 and App, pixel人物 + app icon, in a hot pink framed box.\\n- Middle column: 认证服务器, bright yellow framed box, with a glowing access token card as the visual center.\\n- Right column: API 资源服务器, cyan framed box, with a resource/database icon.\\n- Arrows show: 登录 -> 返回 access token -> 携带 Authorization: Bearer 请求资源 -> 校验权限后返回资源.\\n- The token should be a glowing pixel card, centered between auth server and API server, with small labels nearby for 过期时间 and scope.\\n- Add small retro terminal elements, chevrons, pixel sparks, and motion lines.\\n- Make it feel like annotated engineering notes, not clean corporate PowerPoint.\\n\\nVisible text must be exactly these lines, with no extra words anywhere on the slide:\\n登录后获得\\nAuthorization: Bearer\\n过期时间\\nscope\\n\\nImportant text placement:\\n- Put 登录后获得 as a bold caption near the left/middle login flow.\\n- Put Authorization: Bearer on or near the request arrow or token card, large and readable.\\n- Put 过期时间 and scope as small labels next to the glowing token card.\\n- Do not include any other visible text, titles, subtitles, or labels.\\n\\nVisual specifics:\\n- Use pixel-art style people and server boxes.\\n- The access token card should be the brightest element, with a cyan/pink glow effect but still flat pixel-art style.\\n- The sequence should clearly imply authorization scope and expiry, with security-check marks or lock-like pixels near the server.\\n- Maintain large open margins and strong composition balance.\\n- Presentation-ready, polished, and coherent with the style template.\",\n      \"storageFileId\": \"rsmy7bq1hua9913upvslp5wq-83feb8006bb975d7015e611a61442cf3\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"核心区别不是高级与简单\",\n      \"layout\": \"双栏对比矩阵。左栏 API Key，右栏 Bearer Token。每栏只放三行：表达信息、生命周期、权限粒度。\",\n      \"message\": \"更本质的区别是：API Key 标识应用，Bearer Token 表示授权会话。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/qx9czu0ipozxzsqprxr0dh9v-0f4847ea3deb507fd7259711a7e00440.png\",\n      \"storageKey\": \"generated/drill/qx9czu0ipozxzsqprxr0dh9v-0f4847ea3deb507fd7259711a7e00440.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 5: 核心区别不是高级与简单\\nMain message: 更本质的区别是：API Key 标识应用，Bearer Token 表示授权会话。\\n\\nVisible text must be exactly these lines, with no extra words:\\nAPI Key\\n你是谁的应用\\nBearer Token\\n你现在能做什么\\n\\nLayout:\\n双栏对比矩阵。左栏 API Key，右栏 Bearer Token。每栏只放三行：表达信息、生命周期、权限粒度。\\n\\nVisual style:\\n硬边像素表格，黑色粗线框，关键短语用高亮块标出，整体像技术杂志里的速查表。\\n\\nAdditional image direction:\\n制作一张双栏对比矩阵。左栏标题 API Key，包含“应用身份”“长期凭证”“权限较粗”；右栏标题 Bearer Token，包含“授权状态”“短期令牌”“scope 更细”。中间有醒目的分隔线，顶部放一句“表达的信息不同”。背景是浅色网格纸，表格像复古软件手册中的速查卡。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 5,\n      \"visibleText\": [\n        \"API Key\",\n        \"你是谁的应用\",\n        \"Bearer Token\",\n        \"你现在能做什么\"\n      ],\n      \"visualStyle\": \"硬边像素表格，黑色粗线框，关键短语用高亮块标出，整体像技术杂志里的速查表。\",\n      \"speakerNotes\": \"材料强调，很多文章只说一个简单、一个高级，但更本质的区别在于它们表达的信息不一样。API Key 更偏向你是谁的应用，常用于识别开发者、项目或客户端。Bearer Token 更偏向你现在被授权做什么，常用于表示登录用户或被授权会话。还可以补充生命周期差异：API Key 往往长期有效，Bearer Token 往往短期有效，所以泄露后的风险窗口通常更短。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in the dominant art direction of a Neo-Retro Dev Deck / Pixel-Infographic Editorial. Light cream off-white background with subtle square engineering grid. Thick black borders, hard-edged pixel-infographic style, retro software manual mood, modern developer editorial composition, slight controlled collage overlaps, but polished and presentation-ready.\\n\\nContent must be a double-column comparison matrix with a strong vertical divider. Left column is API Key, right column is Bearer Token. Each column should feel like a technical magazine quick-reference card with chunky black-outlined rectangles and highlighted blocks. Use the palette strictly: hot pink accents for auth/identity, bright yellow for code/tools, cyan/light blue for browser/session/execution, black text and borders, cream background. Add small pixel-art icons and decorative chevrons/gears/arrows, but no extra words anywhere.\\n\\nVISIBLE TEXT MUST BE EXACTLY AND ONLY THESE FOUR LINES, with no other text anywhere on the slide:\\nAPI Key\\n你是谁的应用\\nBearer Token\\n你现在能做什么\\n\\nTypography: bold geometric sans serif for the English titles, clean readable Chinese sans for the Chinese lines, large and legible. Arrange the text as the main content of the two-column matrix. No top headline, no captions, no labels, no footer, no watermark, no logos, no browser chrome, no extra annotations. Make the slide look finished and editorial, with the matrix clearly communicating contrast using color blocks and icons rather than additional text.\",\n      \"storageFileId\": \"qx9czu0ipozxzsqprxr0dh9v-0f4847ea3deb507fd7259711a7e00440\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"Bearer Token 不一定是 JWT\",\n      \"layout\": \"两个相交集合图。左圆是 Bearer Token，右圆是 JWT，相交区域写“JWT 可作为 Bearer Token”。旁边放一条简化请求头。\",\n      \"message\": \"Bearer Token 是令牌的使用方式，JWT 是令牌的数据格式。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/pbp7unsm79seqq8jufzzdlpk-3875265bcbc6e3247387351b3f3ba7f7.png\",\n      \"storageKey\": \"generated/drill/pbp7unsm79seqq8jufzzdlpk-3875265bcbc6e3247387351b3f3ba7f7.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 6: Bearer Token 不一定是 JWT\\nMain message: Bearer Token 是令牌的使用方式，JWT 是令牌的数据格式。\\n\\nVisible text must be exactly these lines, with no extra words:\\nBearer Token\\n使用方式\\nJWT\\n数据格式\\n可以重叠\\n\\nLayout:\\n两个相交集合图。左圆是 Bearer Token，右圆是 JWT，相交区域写“JWT 可作为 Bearer Token”。旁边放一条简化请求头。\\n\\nVisual style:\\n像素化维恩图，带代码标签贴纸，适合开发者快速记忆。\\n\\nAdditional image direction:\\n制作一张概念关系图。画两个相交的像素风圆形集合，左侧为 Bearer Token 并标注 使用方式，右侧为 JWT 并标注 数据格式，相交区域写 可以重叠。右下角放一张小型终端请求头贴纸，显示 Authorization: Bearer。背景为浅色网格纸，使用简洁开发者信息图风格。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 6,\n      \"visibleText\": [\n        \"Bearer Token\",\n        \"使用方式\",\n        \"JWT\",\n        \"数据格式\",\n        \"可以重叠\"\n      ],\n      \"visualStyle\": \"像素化维恩图，带代码标签贴纸，适合开发者快速记忆。\",\n      \"speakerNotes\": \"澄清材料中的常见误区：很多人看到 Bearer Token 就想到 JWT，但两者是不同概念。Bearer Token 表示令牌放在 Authorization: Bearer 中，是一种使用方式。JWT 是一种令牌格式。Bearer Token 可以是 JWT，也可以是普通随机字符串；JWT 也常被用作 Bearer Token。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, landscape 1536x864, in the dominant art direction of Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nOverall look: retro-futuristic developer infographic on a light cream off-white engineering notebook grid background, subtle square grid lines, thick black borders, modular collage composition, pixel-art icons, bold editorial typography, hot pink + bright yellow + cyan as the main accents, black text and outlines, no gradients, no photos, no soft shadows, no corporate styling.\\n\\nSlide topic: Bearer Token 不一定是 JWT.\\nMain visual: a large pixel-art Venn diagram with two overlapping circles.\\n- Left circle: hot pink dominant block, labeled exactly “Bearer Token” with smaller label “使用方式”.\\n- Right circle: cyan/light blue dominant block, labeled exactly “JWT” with smaller label “数据格式”.\\n- Overlap area: yellow highlight and the exact text “可以重叠”.\\nInclude a small code-sticker style terminal/request-header card in the lower right, simplified and developer-like, but DO NOT include any readable extra words or symbols beyond the required visible text. Keep it abstract if needed.\\n\\nVisible text must be exactly these lines and nothing else:\\nBearer Token\\n使用方式\\nJWT\\n数据格式\\n可以重叠\\n\\nComposition: strong hierarchy, slightly overlapping boxes, thick black outlines, playful pixel sparks/chevrons, editorial rhythm, presentation-ready, high sensibility, coherent, not sparse.\\nNo other text anywhere.\",\n      \"storageFileId\": \"pbp7unsm79seqq8jufzzdlpk-3875265bcbc6e3247387351b3f3ba7f7\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"怎么选\",\n      \"layout\": \"决策分叉图。入口是“你的系统目标是什么”，分到 API Key、Bearer Token、两者结合三条路径。底部放安全警示条。\",\n      \"message\": \"简单开放接口常用 API Key；用户登录、权限控制和第三方授权更适合 Bearer Token。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/jahoo88y18w0gzfaqzzh5ie6-222ddfda80c04dc520c349bc64a4179a.png\",\n      \"storageKey\": \"generated/drill/jahoo88y18w0gzfaqzzh5ie6-222ddfda80c04dc520c349bc64a4179a.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 7: 怎么选\\nMain message: 简单开放接口常用 API Key；用户登录、权限控制和第三方授权更适合 Bearer Token。\\n\\nVisible text must be exactly these lines, with no extra words:\\n应用调用应用\\nAPI Key\\n用户授权访问\\nBearer Token\\n很多系统会一起用\\n\\nLayout:\\n决策分叉图。入口是“你的系统目标是什么”，分到 API Key、Bearer Token、两者结合三条路径。底部放安全警示条。\\n\\nVisual style:\\n像素决策树，带小型路牌图标和红色警示条，结尾页有明确行动感。\\n\\nAdditional image direction:\\n制作一张选型决策树。顶部入口写“系统目标”。左分支是“简单开发者 API、应用调用应用、基础识别限流”指向 API Key；右分支是“用户登录、权限控制、OAuth 或 OIDC”指向 Bearer Token；中间下方有“也可以一起用：应用识别加用户授权”。底部放安全警示条，包含 HTTPS、环境变量、定期轮换、最小权限。背景保持复古开发者网格纸和像素路牌元素。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 7,\n      \"visibleText\": [\n        \"应用调用应用\",\n        \"API Key\",\n        \"用户授权访问\",\n        \"Bearer Token\",\n        \"很多系统会一起用\"\n      ],\n      \"visualStyle\": \"像素决策树，带小型路牌图标和红色警示条，结尾页有明确行动感。\",\n      \"speakerNotes\": \"收束到选型。材料给出的判断是：如果要开放简单开发者 API，主要是应用调用应用，只需要基础识别、计费、限流，不涉及复杂用户授权，API Key 往往够用。如果有用户登录系统，需要基于用户身份访问资源，需要细粒度权限控制，或打算使用 OAuth 2.0、OIDC，Bearer Token 通常更合适。现实中很多平台会同时使用：API Key 识别应用，Bearer Token 识别用户授权。最后提醒，两者本质上都是敏感凭证，需要 HTTPS、不要写死在前端、不要提交到 Git、使用环境变量、定期轮换、最小权限和监控异常调用。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Off-white cream engineering notebook background with subtle square grid lines. Thick black borders, modular collage layout, slightly offset assembled feel, pixel-art icons, bold geometric sans headline style. Slide topic: choosing between API Key and Bearer Token.\\n\\nComposition: a decision tree diagram with strong editorial hierarchy. Top center entry label in a boxed signpost: \\\"系统目标\\\". From it, three clear pixel-decision branches flow downward and outward with black arrows and small pixel road-sign icons.\\n\\nLeft branch box: dominant yellow block, titled exactly \\\"API Key\\\" with small supporting text exactly: \\\"应用调用应用\\\" and under that small text exactly: \\\"简单开发者 API\\\" and exactly: \\\"基础识别限流\\\". Visual cue: small pixel code brackets and a key icon. This branch should imply application-to-application access.\\n\\nRight branch box: dominant cyan/light blue block, titled exactly \\\"Bearer Token\\\" with small supporting text exactly: \\\"用户授权访问\\\" and under that small text exactly: \\\"用户登录\\\" and exactly: \\\"权限控制\\\" and exactly: \\\"OAuth 或 OIDC\\\". Visual cue: small pixel browser window and user/lock icon. This branch should imply user-authenticated access.\\n\\nMiddle lower combined box: hot pink accent block, title text exactly: \\\"很多系统会一起用\\\". Under it, small supporting line exactly: \\\"也可以一起用：应用识别加用户授权\\\". This box should connect from both branches, showing a combined strategy. Use pink as the dominant accent for intelligence/agent concept, but the main decision paths use yellow and cyan.\\n\\nBottom safety warning strip: full-width red warning bar with thick black border, pixel alert icon, and four short safety notes in small readable text, exactly including these terms: \\\"HTTPS\\\", \\\"环境变量\\\", \\\"定期轮换\\\", \\\"最小权限\\\". The bar must feel like a strong caution strip, not a UI banner.\\n\\nAdd small pixel roadside sign motifs, chevrons, motion lines, and tiny gears around the branches. Keep everything readable at presentation distance, high contrast black text on colored blocks. Retro developer manual vibe mixed with modern AI dev-tool marketing, playful but opinionated, not corporate.\\n\\nVisible text must be exactly these lines and no extra words beyond labels/necessary diagram text:\\n系统目标\\nAPI Key\\n应用调用应用\\n简单开发者 API\\n基础识别限流\\nBearer Token\\n用户授权访问\\n用户登录\\n权限控制\\nOAuth 或 OIDC\\n很多系统会一起用\\n也可以一起用：应用识别加用户授权\\nHTTPS\\n环境变量\\n定期轮换\\n最小权限\\n\\nNo additional captions, no watermarks, no browser chrome, no logos, no extra paragraphs. Make it look like a finished slide, not a wireframe. Ensure the text is legible and balanced within the 16:9 canvas.\",\n      \"storageFileId\": \"jahoo88y18w0gzfaqzzh5ie6-222ddfda80c04dc520c349bc64a4179a\"\n    }\n  ],\n  \"styleId\": \"neo_retro_dev\",\n  \"summary\": \"面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\",\n  \"audience\": \"正在学习 Web API、登录授权、第三方接口调用的初学开发者和产品技术协作人员\",\n  \"imageSize\": \"1536x864\",\n  \"imageModel\": \"gpt-image-2\",\n  \"plannerModel\": \"gpt-5.5\"\n}","markdown":"# API Key 和 Bearer Token 是什么，有啥区别？\n\n{\n  \"style\": \"Neo-Retro Dev Deck / Pixel-Infographic Editorial\",\n  \"title\": \"API Key 和 Bearer Token 的区别\",\n  \"format\": \"presenter_slides\",\n  \"slides\": [\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"先别把它们都叫密钥\",\n      \"layout\": \"封面式构图，中央放两个像素风凭证卡片，一张写 API Key，一张写 Bearer Token，中间用不等号连接。标题大字置顶，副标语分散在卡片周围。\",\n      \"message\": \"API Key 和 Bearer Token 都是请求里的凭证，但表达的信息不同。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/dpxiybdctw7habj8vsuhky8g-6d315ad8341b9eff81970e5d8ed50baa.png\",\n      \"storageKey\": \"generated/drill/dpxiybdctw7habj8vsuhky8g-6d315ad8341b9eff81970e5d8ed50baa.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 1: 先别把它们都叫密钥\\nMain message: API Key 和 Bearer Token 都是请求里的凭证，但表达的信息不同。\\n\\nVisible text must be exactly these lines, with no extra words:\\n一个字符串\\n两种含义\\nAPI Key ≠ Bearer Token\\n\\nLayout:\\n封面式构图，中央放两个像素风凭证卡片，一张写 API Key，一张写 Bearer Token，中间用不等号连接。标题大字置顶，副标语分散在卡片周围。\\n\\nVisual style:\\n复古开发者手册感，网格纸背景，像素化接口元素，终端窗口边框，黑色主文字配少量高亮色。\\n\\nAdditional image direction:\\n制作一张技术讲解封面。画面中央是两个并排的像素风访问凭证卡片，左侧卡片标注 API Key，右侧卡片标注 Bearer Token，中间是醒目的不等号。背景是浅色工程网格纸，加入小型终端窗口、HTTP 请求碎片、像素箭头和微型锁图标。文字保持稀疏，突出“一个字符串，两种含义”。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 1,\n      \"visibleText\": [\n        \"一个字符串\",\n        \"两种含义\",\n        \"API Key ≠ Bearer Token\"\n      ],\n      \"visualStyle\": \"复古开发者手册感，网格纸背景，像素化接口元素，终端窗口边框，黑色主文字配少量高亮色。\",\n      \"speakerNotes\": \"开场先回应常见误解：很多初学者会觉得它们都是一个字符串，放进请求就行。但材料明确指出，它们在用途、设计目标、安全性和适用场景上都有明显区别。本页只建立核心悬念：不是看起来像不像，而是它们分别代表什么。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in the dominant art direction: Neo-Retro Dev Deck / Pixel-Infographic Editorial. Single slide only, finished presentation-ready composition.\\n\\nSlide topic: API Key 和 Bearer Token 的区别\\nCover-style composition. Light cream/off-white engineering notebook grid-paper background with subtle square grid lines. Retro developer-manual feel, slightly rebellious, playful, confident.\\n\\nVisible text must be EXACTLY these lines and nothing else:\\n一个字符串\\n两种含义\\nAPI Key ≠ Bearer Token\\n\\nTypography: huge bold geometric sans serif, black, slightly condensed. Make the first line largest, second line medium, third line as a strong headline statement. Keep all text readable and sparse. No extra words, no bullets, no captions, no watermarks.\\n\\nLayout: Title big at top. In the center, two side-by-side pixel-art credential cards with thick black borders and slight overlap / collage feel. Left card label: API Key. Right card label: Bearer Token. Between them, a large bold not-equal sign (= visually an inequality symbol) in black or hot pink. Surround with small spaced sub-phrase fragments from the visible text and tiny interface notes, but only the three required lines may be visible text; do not add any other readable text.\\n\\nVisual direction: technical explainer cover. Add small terminal-window frames, HTTP request fragments as abstract pixel shapes (not readable text), pixel arrows, micro lock icons, code-bracket motifs, browser/web execution hints, and subtle motion lines. Use strict palette: hot pink for agent/intelligence accents, bright yellow for code/tools, cyan/light blue for browser/execution, black for text/borders, cream background. Each main element should have one dominant color block. Thick black outlines, 8-bit / 16-bit inspired flat pixel art. Editorial composition with stacked modular blocks, intentional slight overlaps, horizontally aligned header bar feel. No gradients, no realistic photos, no soft shadows, no corporate clean minimalism.\\n\\nEnsure the slide feels like annotated engineering notes, not a generic infographic. Strong hierarchy, high contrast, high sensibility, coherent with NotebookLM / Kael style. No browser chrome, no extra logos, no signatures, no contact sheet, no multiple slides.\",\n      \"storageFileId\": \"dpxiybdctw7habj8vsuhky8g-6d315ad8341b9eff81970e5d8ed50baa\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"一句话理解\",\n      \"layout\": \"左右对照卡片。左侧是编号牌和应用图标，右侧是通行证和用户头像。中间用一条像素化分隔线区分。\",\n      \"message\": \"API Key 更像固定开发者编号，Bearer Token 更像登录后的临时通行证。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/i5ntrv4pbjdzsuhyc0eny2g6-f19ca1f0492caa7e7e153ad04d2e9a14.png\",\n      \"storageKey\": \"generated/drill/i5ntrv4pbjdzsuhyc0eny2g6-f19ca1f0492caa7e7e153ad04d2e9a14.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 2: 一句话理解\\nMain message: API Key 更像固定开发者编号，Bearer Token 更像登录后的临时通行证。\\n\\nVisible text must be exactly these lines, with no extra words:\\nAPI Key\\n固定开发者编号\\nBearer Token\\n临时通行证\\n\\nLayout:\\n左右对照卡片。左侧是编号牌和应用图标，右侧是通行证和用户头像。中间用一条像素化分隔线区分。\\n\\nVisual style:\\n像 90 年代软件说明书里的对照插图，平面像素图标，粗边框标签，少量荧光高亮。\\n\\nAdditional image direction:\\n制作左右对照式解释图。左侧显示一个应用窗口拿着固定编号牌，标签为 API Key 和 固定开发者编号；右侧显示一个用户头像拿着临时通行证，标签为 Bearer Token 和 临时通行证。中间用像素风竖线分隔，背景为浅色网格纸，加入小箭头和简洁标签，整体像开发者手册中的概念页。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 2,\n      \"visibleText\": [\n        \"API Key\",\n        \"固定开发者编号\",\n        \"Bearer Token\",\n        \"临时通行证\"\n      ],\n      \"visualStyle\": \"像 90 年代软件说明书里的对照插图，平面像素图标，粗边框标签，少量荧光高亮。\",\n      \"speakerNotes\": \"用材料中的生活类比帮助听众建立直觉：API Key 像系统发给你的固定开发者编号；Bearer Token 像用户登录后拿到的一张临时通行证。这里不要过度展开，只强调两者不是同一层面的东西：一个偏识别调用方，一个偏表示授权状态。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in the dominant style of a Neo-Retro Dev Deck / Pixel-Infographic Editorial. Single slide only. Background: light cream/off-white engineering notebook paper with subtle square grid lines, slightly off-register and hand-assembled feel. Strong black thick borders, flat colors, pixel-art illustration, 90s software manual vibe mixed with modern developer marketing, playful but clean and presentation-ready.\\n\\nSlide topic: compare API Key and Bearer Token in a simple visual analogy. Layout: left-right comparison with two large boxed panels. A pixelated vertical divider line in the center. Left panel: a small application window icon holding a fixed numbered badge/ID card, with a developer/app motif. Right panel: a user avatar icon holding a temporary pass/ticket, with a login/session motif. Use slight overlaps, arrows, and tiny pixel sparks for emphasis. Each panel should have one dominant color block: left panel with bright yellow accents for code/tool identity; right panel with hot pink accents for auth/session identity; use cyan for the central divider or supporting accents. Thick black outlines, flat shading only, no gradients, no soft shadows, no realistic rendering.\\n\\nTypography: huge bold geometric sans serif for the labels, black text, slightly condensed. Keep text minimal and readable. The only visible text in the entire slide must be exactly these four lines, and nothing else: \\nAPI Key\\n固定开发者编号\\nBearer Token\\n临时通行证\\nPlace the English title above the Chinese line inside each card, with clean hierarchy. No extra captions, no extra labels, no numbers, no watermarks, no logos, no UI browser chrome.\\n\\nComposition: editorial and balanced, like a polished developer manual page. Left side should feel like a fixed developer credential card; right side should feel like a temporary access pass after login. Add simple pixel icons and bold framed labels. Ensure the overall slide feels finished, confident, and cohesive with the template.\",\n      \"storageFileId\": \"i5ntrv4pbjdzsuhyc0eny2g6-f19ca1f0492caa7e7e153ad04d2e9a14\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"API Key 识别谁在调用\",\n      \"layout\": \"流程卡片：客户端带 X-API-Key 请求 API，服务端检查 Key 是否存在、有效、未禁用、未超配额，然后返回资源。\",\n      \"message\": \"API Key 主要用于识别应用、控制配额、限流和统计调用量。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/dd0geekizk0eoiy45zj1o4q0-8dfceea8addb5739e5507c19900b838b.png\",\n      \"storageKey\": \"generated/drill/dd0geekizk0eoiy45zj1o4q0-8dfceea8addb5739e5507c19900b838b.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 3: API Key 识别谁在调用\\nMain message: API Key 主要用于识别应用、控制配额、限流和统计调用量。\\n\\nVisible text must be exactly these lines, with no extra words:\\n识别应用\\n配额\\n限流\\n调用统计\\n\\nLayout:\\n流程卡片：客户端带 X-API-Key 请求 API，服务端检查 Key 是否存在、有效、未禁用、未超配额，然后返回资源。\\n\\nVisual style:\\n像素流程图，使用终端代码块样式展示 X-API-Key，服务端校验项以小型检测清单呈现。\\n\\nAdditional image direction:\\n制作一张 API Key 工作方式流程图。左侧是客户端小电脑图标，中间是一段简化请求卡片显示 X-API-Key，右侧是服务器机柜图标。服务器旁有四个小检测项：存在、有效、未禁用、未超配额。下方用小图标表示配额、限流、调用统计。布局清晰，像复古技术手册中的流程示意。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 3,\n      \"visibleText\": [\n        \"识别应用\",\n        \"配额\",\n        \"限流\",\n        \"调用统计\"\n      ],\n      \"visualStyle\": \"像素流程图，使用终端代码块样式展示 X-API-Key，服务端校验项以小型检测清单呈现。\",\n      \"speakerNotes\": \"解释 API Key 的定义：它是服务端分配给客户端的一串唯一字符串，用来识别谁在调用 API。材料列出的常见作用包括标识调用者身份、配额控制和限流、统计调用量、提供基础访问控制。也提醒它的局限：通常权限较粗粒度，泄露后容易被直接盗用，不能很好表达某个具体用户已经授权。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, landscape 1536x864, in the Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Off-white light cream engineering notebook background with subtle square grid lines. Thick black borders, stacked modular blocks, slight collage overlap, retro-futuristic developer manual feel, pixel-art icons, bold editorial hierarchy. Strict palette: hot pink, bright yellow, cyan/light blue, black, cream. No gradients, no photos, no soft shadows, no corporate minimalism.\\n\\nSlide topic in Chinese: API Key 识别谁在调用.\\n\\nThis is Slide 3 of a deck about API Key and Bearer Token differences, but only generate this single slide.\\n\\nVisible text must be exactly these four lines and nothing else anywhere on the slide:\\n识别应用\\n配额\\n限流\\n调用统计\\n\\nLayout:\\n- Main composition is a clear workflow flowchart like a retro technical manual.\\n- Left: a small pixel-art client computer icon in a box labeled only with the required visible text line? No extra labels outside the exact four lines. Use the icon and request flow visually, but do not add any extra readable words.\\n- Center: a simplified terminal-code style request card with bold monospaced text X-API-Key, presented inside a black-bordered rectangular code block. This is part of the visual; no other words are allowed.\\n- Right: a pixel-art server rack / server cabinet icon in a box.\\n- Between client and server: arrows showing request and response flow, with small motion chevrons and pixel sparks.\\n- Next to the server: a compact checklist panel with four tiny check items represented visually only, corresponding to existence, validity, not disabled, not over quota. Use small check icons and stamped squares; do not add extra readable words beyond the required four visible lines.\\n- Bottom row: four small icon tiles using pixel-art symbols to represent quota, rate limiting, and call statistics. These tiles should be colorful and editorial. The only text visible in the entire slide must be the exact four Chinese lines listed above, placed as the bottom captions under the tiles, one line per tile, in that exact order.\\n\\nTypography and placement:\\n- Make the four required Chinese lines large enough to be readable at presentation distance, but keep the rest of the slide mostly diagrammatic.\\n- Use bold black geometric sans for the Chinese lines, with slight condensed styling.\\n- Use a terminal/code block style for X-API-Key in monospaced black text on a pale yellow card.\\n- No extra titles, subtitles, legends, bullets, paragraph text, footer, source notes, or watermarks.\\n\\nIcon style:\\n- Pixel-art, 8-bit/16-bit inspired, flat colors, black outline.\\n- Client computer in cyan, server cabinet in hot pink, request card in yellow, flow arrows in black and cyan.\\n- Small utility icons for quota, rate limit, statistics: gauge, clock/stopwatch, bar chart, counter dots, etc.\\n\\nOverall composition should look like a polished retro developer slide: clean, balanced, dense enough to feel finished, but with intentional modular blocks and editorial rhythm.\\n\\nEnsure the slide looks like a single finished presentation slide, not a wireframe, not multiple slides, not a contact sheet.\",\n      \"storageFileId\": \"dd0geekizk0eoiy45zj1o4q0-8dfceea8addb5739e5507c19900b838b\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"Bearer Token 表示被授权做什么\",\n      \"layout\": \"登录授权时序图：用户登录，服务端返回 access token，之后请求带 Authorization: Bearer，服务端判断资源访问权限。\",\n      \"message\": \"Bearer Token 通常用于登录授权，能表达用户、过期时间和访问范围。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/rsmy7bq1hua9913upvslp5wq-83feb8006bb975d7015e611a61442cf3.png\",\n      \"storageKey\": \"generated/drill/rsmy7bq1hua9913upvslp5wq-83feb8006bb975d7015e611a61442cf3.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 4: Bearer Token 表示被授权做什么\\nMain message: Bearer Token 通常用于登录授权，能表达用户、过期时间和访问范围。\\n\\nVisible text must be exactly these lines, with no extra words:\\n登录后获得\\nAuthorization: Bearer\\n过期时间\\nscope\\n\\nLayout:\\n登录授权时序图：用户登录，服务端返回 access token，之后请求带 Authorization: Bearer，服务端判断资源访问权限。\\n\\nVisual style:\\n横向时序图，像素人物、认证服务器、资源服务器三列，使用发光令牌作为视觉中心。\\n\\nAdditional image direction:\\n制作一张 Bearer Token 登录授权时序图。左侧是用户和 App，中间是认证服务器，右侧是 API 资源服务器。箭头依次表示登录、返回 access token、携带 Authorization: Bearer 请求资源、校验权限后返回资源。令牌以发光像素卡片呈现，旁边标注过期时间和 scope。背景保持浅色网格与复古终端元素。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 4,\n      \"visibleText\": [\n        \"登录后获得\",\n        \"Authorization: Bearer\",\n        \"过期时间\",\n        \"scope\"\n      ],\n      \"visualStyle\": \"横向时序图，像素人物、认证服务器、资源服务器三列，使用发光令牌作为视觉中心。\",\n      \"speakerNotes\": \"解释 Bearer Token：它是持有即有效的访问令牌，谁拿着它谁就能用。材料指出它常出现在 OAuth 2.0、OpenID Connect、登录授权系统中。重点不只是识别调用方，而是表示某个用户或客户端已经完成认证，并获得某些资源访问权限。它通常支持过期时间和访问范围 scope，但也需要处理过期、刷新、撤销等机制。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Single slide only, not a contact sheet.\\n\\nTopic: Bearer Token 表示被授权做什么\\nDeck slide 4 of a Chinese-language presentation about API Key 和 Bearer Token 的区别.\\n\\nDominant art direction:\\n- Light cream/off-white background with subtle engineering notebook grid.\\n- Retro-futuristic developer editorial infographic, pixel-art meets startup deck.\\n- Thick black borders, modular boxes, slight overlaps, collage-like assembly.\\n- Strict palette: hot pink, bright yellow, cyan/light blue, black, cream/white.\\n- No gradients, no photos, no soft shadows, no corporate look.\\n- Strong typography hierarchy, bold geometric sans serif headline blocks.\\n- Pixel art icons and terminal/dev-tool motifs.\\n\\nLayout:\\n- Horizontal authorization sequence diagram across the slide, reading left to right.\\n- Left column: 用户 and App, pixel人物 + app icon, in a hot pink framed box.\\n- Middle column: 认证服务器, bright yellow framed box, with a glowing access token card as the visual center.\\n- Right column: API 资源服务器, cyan framed box, with a resource/database icon.\\n- Arrows show: 登录 -> 返回 access token -> 携带 Authorization: Bearer 请求资源 -> 校验权限后返回资源.\\n- The token should be a glowing pixel card, centered between auth server and API server, with small labels nearby for 过期时间 and scope.\\n- Add small retro terminal elements, chevrons, pixel sparks, and motion lines.\\n- Make it feel like annotated engineering notes, not clean corporate PowerPoint.\\n\\nVisible text must be exactly these lines, with no extra words anywhere on the slide:\\n登录后获得\\nAuthorization: Bearer\\n过期时间\\nscope\\n\\nImportant text placement:\\n- Put 登录后获得 as a bold caption near the left/middle login flow.\\n- Put Authorization: Bearer on or near the request arrow or token card, large and readable.\\n- Put 过期时间 and scope as small labels next to the glowing token card.\\n- Do not include any other visible text, titles, subtitles, or labels.\\n\\nVisual specifics:\\n- Use pixel-art style people and server boxes.\\n- The access token card should be the brightest element, with a cyan/pink glow effect but still flat pixel-art style.\\n- The sequence should clearly imply authorization scope and expiry, with security-check marks or lock-like pixels near the server.\\n- Maintain large open margins and strong composition balance.\\n- Presentation-ready, polished, and coherent with the style template.\",\n      \"storageFileId\": \"rsmy7bq1hua9913upvslp5wq-83feb8006bb975d7015e611a61442cf3\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"核心区别不是高级与简单\",\n      \"layout\": \"双栏对比矩阵。左栏 API Key，右栏 Bearer Token。每栏只放三行：表达信息、生命周期、权限粒度。\",\n      \"message\": \"更本质的区别是：API Key 标识应用，Bearer Token 表示授权会话。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/qx9czu0ipozxzsqprxr0dh9v-0f4847ea3deb507fd7259711a7e00440.png\",\n      \"storageKey\": \"generated/drill/qx9czu0ipozxzsqprxr0dh9v-0f4847ea3deb507fd7259711a7e00440.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 5: 核心区别不是高级与简单\\nMain message: 更本质的区别是：API Key 标识应用，Bearer Token 表示授权会话。\\n\\nVisible text must be exactly these lines, with no extra words:\\nAPI Key\\n你是谁的应用\\nBearer Token\\n你现在能做什么\\n\\nLayout:\\n双栏对比矩阵。左栏 API Key，右栏 Bearer Token。每栏只放三行：表达信息、生命周期、权限粒度。\\n\\nVisual style:\\n硬边像素表格，黑色粗线框，关键短语用高亮块标出，整体像技术杂志里的速查表。\\n\\nAdditional image direction:\\n制作一张双栏对比矩阵。左栏标题 API Key，包含“应用身份”“长期凭证”“权限较粗”；右栏标题 Bearer Token，包含“授权状态”“短期令牌”“scope 更细”。中间有醒目的分隔线，顶部放一句“表达的信息不同”。背景是浅色网格纸，表格像复古软件手册中的速查卡。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 5,\n      \"visibleText\": [\n        \"API Key\",\n        \"你是谁的应用\",\n        \"Bearer Token\",\n        \"你现在能做什么\"\n      ],\n      \"visualStyle\": \"硬边像素表格，黑色粗线框，关键短语用高亮块标出，整体像技术杂志里的速查表。\",\n      \"speakerNotes\": \"材料强调，很多文章只说一个简单、一个高级，但更本质的区别在于它们表达的信息不一样。API Key 更偏向你是谁的应用，常用于识别开发者、项目或客户端。Bearer Token 更偏向你现在被授权做什么，常用于表示登录用户或被授权会话。还可以补充生命周期差异：API Key 往往长期有效，Bearer Token 往往短期有效，所以泄露后的风险窗口通常更短。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in the dominant art direction of a Neo-Retro Dev Deck / Pixel-Infographic Editorial. Light cream off-white background with subtle square engineering grid. Thick black borders, hard-edged pixel-infographic style, retro software manual mood, modern developer editorial composition, slight controlled collage overlaps, but polished and presentation-ready.\\n\\nContent must be a double-column comparison matrix with a strong vertical divider. Left column is API Key, right column is Bearer Token. Each column should feel like a technical magazine quick-reference card with chunky black-outlined rectangles and highlighted blocks. Use the palette strictly: hot pink accents for auth/identity, bright yellow for code/tools, cyan/light blue for browser/session/execution, black text and borders, cream background. Add small pixel-art icons and decorative chevrons/gears/arrows, but no extra words anywhere.\\n\\nVISIBLE TEXT MUST BE EXACTLY AND ONLY THESE FOUR LINES, with no other text anywhere on the slide:\\nAPI Key\\n你是谁的应用\\nBearer Token\\n你现在能做什么\\n\\nTypography: bold geometric sans serif for the English titles, clean readable Chinese sans for the Chinese lines, large and legible. Arrange the text as the main content of the two-column matrix. No top headline, no captions, no labels, no footer, no watermark, no logos, no browser chrome, no extra annotations. Make the slide look finished and editorial, with the matrix clearly communicating contrast using color blocks and icons rather than additional text.\",\n      \"storageFileId\": \"qx9czu0ipozxzsqprxr0dh9v-0f4847ea3deb507fd7259711a7e00440\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"Bearer Token 不一定是 JWT\",\n      \"layout\": \"两个相交集合图。左圆是 Bearer Token，右圆是 JWT，相交区域写“JWT 可作为 Bearer Token”。旁边放一条简化请求头。\",\n      \"message\": \"Bearer Token 是令牌的使用方式，JWT 是令牌的数据格式。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/pbp7unsm79seqq8jufzzdlpk-3875265bcbc6e3247387351b3f3ba7f7.png\",\n      \"storageKey\": \"generated/drill/pbp7unsm79seqq8jufzzdlpk-3875265bcbc6e3247387351b3f3ba7f7.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 6: Bearer Token 不一定是 JWT\\nMain message: Bearer Token 是令牌的使用方式，JWT 是令牌的数据格式。\\n\\nVisible text must be exactly these lines, with no extra words:\\nBearer Token\\n使用方式\\nJWT\\n数据格式\\n可以重叠\\n\\nLayout:\\n两个相交集合图。左圆是 Bearer Token，右圆是 JWT，相交区域写“JWT 可作为 Bearer Token”。旁边放一条简化请求头。\\n\\nVisual style:\\n像素化维恩图，带代码标签贴纸，适合开发者快速记忆。\\n\\nAdditional image direction:\\n制作一张概念关系图。画两个相交的像素风圆形集合，左侧为 Bearer Token 并标注 使用方式，右侧为 JWT 并标注 数据格式，相交区域写 可以重叠。右下角放一张小型终端请求头贴纸，显示 Authorization: Bearer。背景为浅色网格纸，使用简洁开发者信息图风格。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 6,\n      \"visibleText\": [\n        \"Bearer Token\",\n        \"使用方式\",\n        \"JWT\",\n        \"数据格式\",\n        \"可以重叠\"\n      ],\n      \"visualStyle\": \"像素化维恩图，带代码标签贴纸，适合开发者快速记忆。\",\n      \"speakerNotes\": \"澄清材料中的常见误区：很多人看到 Bearer Token 就想到 JWT，但两者是不同概念。Bearer Token 表示令牌放在 Authorization: Bearer 中，是一种使用方式。JWT 是一种令牌格式。Bearer Token 可以是 JWT，也可以是普通随机字符串；JWT 也常被用作 Bearer Token。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, landscape 1536x864, in the dominant art direction of Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nOverall look: retro-futuristic developer infographic on a light cream off-white engineering notebook grid background, subtle square grid lines, thick black borders, modular collage composition, pixel-art icons, bold editorial typography, hot pink + bright yellow + cyan as the main accents, black text and outlines, no gradients, no photos, no soft shadows, no corporate styling.\\n\\nSlide topic: Bearer Token 不一定是 JWT.\\nMain visual: a large pixel-art Venn diagram with two overlapping circles.\\n- Left circle: hot pink dominant block, labeled exactly “Bearer Token” with smaller label “使用方式”.\\n- Right circle: cyan/light blue dominant block, labeled exactly “JWT” with smaller label “数据格式”.\\n- Overlap area: yellow highlight and the exact text “可以重叠”.\\nInclude a small code-sticker style terminal/request-header card in the lower right, simplified and developer-like, but DO NOT include any readable extra words or symbols beyond the required visible text. Keep it abstract if needed.\\n\\nVisible text must be exactly these lines and nothing else:\\nBearer Token\\n使用方式\\nJWT\\n数据格式\\n可以重叠\\n\\nComposition: strong hierarchy, slightly overlapping boxes, thick black outlines, playful pixel sparks/chevrons, editorial rhythm, presentation-ready, high sensibility, coherent, not sparse.\\nNo other text anywhere.\",\n      \"storageFileId\": \"pbp7unsm79seqq8jufzzdlpk-3875265bcbc6e3247387351b3f3ba7f7\"\n    },\n    {\n      \"size\": \"1536x864\",\n      \"model\": \"gpt-image-2\",\n      \"title\": \"怎么选\",\n      \"layout\": \"决策分叉图。入口是“你的系统目标是什么”，分到 API Key、Bearer Token、两者结合三条路径。底部放安全警示条。\",\n      \"message\": \"简单开放接口常用 API Key；用户登录、权限控制和第三方授权更适合 Bearer Token。\",\n      \"imageUrl\": \"https://cdn.drillso.com/generated/drill/jahoo88y18w0gzfaqzzh5ie6-222ddfda80c04dc520c349bc64a4179a.png\",\n      \"storageKey\": \"generated/drill/jahoo88y18w0gzfaqzzh5ie6-222ddfda80c04dc520c349bc64a4179a.png\",\n      \"imagePrompt\": \"Create exactly one complete presentation slide image.\\n\\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\\n\\nSTYLE TEMPLATE START\\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\\n\\nCore visual identity:\\n- Retro-futuristic, developer-centric, editorial infographic style.\\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\\n- Pixel art meets startup slide deck.\\n- Mood: confident, playful, opinionated, slightly rebellious.\\n- Builders explaining the future, not selling fluff.\\n\\nCanvas and background:\\n- Use a light cream or off-white grid paper background.\\n- Add subtle square grid lines like an engineering notebook.\\n- Slides should feel like annotated engineering notes, not corporate PPTs.\\n\\nTypography:\\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\\n- Headlines may mix the requested language and English.\\n- English sub-labels sit under requested-language titles in small clean type.\\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\\n\\nStrict color palette:\\n- Hot pink for agent, brain, intelligence concepts.\\n- Bright yellow for editor, code, and tools.\\n- Cyan or light blue for browser, web, and execution.\\n- Black for text and borders.\\n- White or cream for background.\\n- Each section should have one dominant color block.\\n\\nLayout language:\\n- Stacked modular blocks.\\n- Rectangles with thick black borders.\\n- Slight intentional overlaps and collage-like assembly.\\n- Horizontal section header bars.\\n- Card structures for steps, evolution, layers.\\n- Controlled imperfection: assembled, not perfectly sterile.\\n\\nIconography and graphics:\\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\\n\\nContent patterns:\\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\\n\\nTone:\\n- Short, declarative, slightly opinionated.\\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\\n- Bad: Empowering users with cutting-edge solutions.\\n\\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\\nSTYLE TEMPLATE END\\n\\nDeck title: API Key 和 Bearer Token 的区别\\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\\nDeck format: presenter_slides\\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\\n\\nSlide 7: 怎么选\\nMain message: 简单开放接口常用 API Key；用户登录、权限控制和第三方授权更适合 Bearer Token。\\n\\nVisible text must be exactly these lines, with no extra words:\\n应用调用应用\\nAPI Key\\n用户授权访问\\nBearer Token\\n很多系统会一起用\\n\\nLayout:\\n决策分叉图。入口是“你的系统目标是什么”，分到 API Key、Bearer Token、两者结合三条路径。底部放安全警示条。\\n\\nVisual style:\\n像素决策树，带小型路牌图标和红色警示条，结尾页有明确行动感。\\n\\nAdditional image direction:\\n制作一张选型决策树。顶部入口写“系统目标”。左分支是“简单开发者 API、应用调用应用、基础识别限流”指向 API Key；右分支是“用户登录、权限控制、OAuth 或 OIDC”指向 Bearer Token；中间下方有“也可以一起用：应用识别加用户授权”。底部放安全警示条，包含 HTTPS、环境变量、定期轮换、最小权限。背景保持复古开发者网格纸和像素路牌元素。\\n\\nRequirements:\\n- Canvas: 1536x864 landscape presentation slide.\\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\\n- Keep all visible text readable at presentation distance.\\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.\",\n      \"slideNumber\": 7,\n      \"visibleText\": [\n        \"应用调用应用\",\n        \"API Key\",\n        \"用户授权访问\",\n        \"Bearer Token\",\n        \"很多系统会一起用\"\n      ],\n      \"visualStyle\": \"像素决策树，带小型路牌图标和红色警示条，结尾页有明确行动感。\",\n      \"speakerNotes\": \"收束到选型。材料给出的判断是：如果要开放简单开发者 API，主要是应用调用应用，只需要基础识别、计费、限流，不涉及复杂用户授权，API Key 往往够用。如果有用户登录系统，需要基于用户身份访问资源，需要细粒度权限控制，或打算使用 OAuth 2.0、OIDC，Bearer Token 通常更合适。现实中很多平台会同时使用：API Key 识别应用，Bearer Token 识别用户授权。最后提醒，两者本质上都是敏感凭证，需要 HTTPS、不要写死在前端、不要提交到 Git、使用环境变量、定期轮换、最小权限和监控异常调用。\",\n      \"revisedPrompt\": \"Create exactly one complete presentation slide image, 1536x864 landscape, in Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Off-white cream engineering notebook background with subtle square grid lines. Thick black borders, modular collage layout, slightly offset assembled feel, pixel-art icons, bold geometric sans headline style. Slide topic: choosing between API Key and Bearer Token.\\n\\nComposition: a decision tree diagram with strong editorial hierarchy. Top center entry label in a boxed signpost: \\\"系统目标\\\". From it, three clear pixel-decision branches flow downward and outward with black arrows and small pixel road-sign icons.\\n\\nLeft branch box: dominant yellow block, titled exactly \\\"API Key\\\" with small supporting text exactly: \\\"应用调用应用\\\" and under that small text exactly: \\\"简单开发者 API\\\" and exactly: \\\"基础识别限流\\\". Visual cue: small pixel code brackets and a key icon. This branch should imply application-to-application access.\\n\\nRight branch box: dominant cyan/light blue block, titled exactly \\\"Bearer Token\\\" with small supporting text exactly: \\\"用户授权访问\\\" and under that small text exactly: \\\"用户登录\\\" and exactly: \\\"权限控制\\\" and exactly: \\\"OAuth 或 OIDC\\\". Visual cue: small pixel browser window and user/lock icon. This branch should imply user-authenticated access.\\n\\nMiddle lower combined box: hot pink accent block, title text exactly: \\\"很多系统会一起用\\\". Under it, small supporting line exactly: \\\"也可以一起用：应用识别加用户授权\\\". This box should connect from both branches, showing a combined strategy. Use pink as the dominant accent for intelligence/agent concept, but the main decision paths use yellow and cyan.\\n\\nBottom safety warning strip: full-width red warning bar with thick black border, pixel alert icon, and four short safety notes in small readable text, exactly including these terms: \\\"HTTPS\\\", \\\"环境变量\\\", \\\"定期轮换\\\", \\\"最小权限\\\". The bar must feel like a strong caution strip, not a UI banner.\\n\\nAdd small pixel roadside sign motifs, chevrons, motion lines, and tiny gears around the branches. Keep everything readable at presentation distance, high contrast black text on colored blocks. Retro developer manual vibe mixed with modern AI dev-tool marketing, playful but opinionated, not corporate.\\n\\nVisible text must be exactly these lines and no extra words beyond labels/necessary diagram text:\\n系统目标\\nAPI Key\\n应用调用应用\\n简单开发者 API\\n基础识别限流\\nBearer Token\\n用户授权访问\\n用户登录\\n权限控制\\nOAuth 或 OIDC\\n很多系统会一起用\\n也可以一起用：应用识别加用户授权\\nHTTPS\\n环境变量\\n定期轮换\\n最小权限\\n\\nNo additional captions, no watermarks, no browser chrome, no logos, no extra paragraphs. Make it look like a finished slide, not a wireframe. Ensure the text is legible and balanced within the 16:9 canvas.\",\n      \"storageFileId\": \"jahoo88y18w0gzfaqzzh5ie6-222ddfda80c04dc520c349bc64a4179a\"\n    }\n  ],\n  \"styleId\": \"neo_retro_dev\",\n  \"summary\": \"面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\",\n  \"audience\": \"正在学习 Web API、登录授权、第三方接口调用的初学开发者和产品技术协作人员\",\n  \"imageSize\": \"1536x864\",\n  \"imageModel\": \"gpt-image-2\",\n  \"plannerModel\": \"gpt-5.5\"\n}","structured":{"style":"Neo-Retro Dev Deck / Pixel-Infographic Editorial","title":"API Key 和 Bearer Token 的区别","format":"presenter_slides","slides":[{"size":"1536x864","model":"gpt-image-2","title":"先别把它们都叫密钥","layout":"封面式构图，中央放两个像素风凭证卡片，一张写 API Key，一张写 Bearer Token，中间用不等号连接。标题大字置顶，副标语分散在卡片周围。","message":"API Key 和 Bearer Token 都是请求里的凭证，但表达的信息不同。","imageUrl":"https://cdn.drillso.com/generated/drill/dpxiybdctw7habj8vsuhky8g-6d315ad8341b9eff81970e5d8ed50baa.png","storageKey":"generated/drill/dpxiybdctw7habj8vsuhky8g-6d315ad8341b9eff81970e5d8ed50baa.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: API Key 和 Bearer Token 的区别\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 1: 先别把它们都叫密钥\nMain message: API Key 和 Bearer Token 都是请求里的凭证，但表达的信息不同。\n\nVisible text must be exactly these lines, with no extra words:\n一个字符串\n两种含义\nAPI Key ≠ Bearer Token\n\nLayout:\n封面式构图，中央放两个像素风凭证卡片，一张写 API Key，一张写 Bearer Token，中间用不等号连接。标题大字置顶，副标语分散在卡片周围。\n\nVisual style:\n复古开发者手册感，网格纸背景，像素化接口元素，终端窗口边框，黑色主文字配少量高亮色。\n\nAdditional image direction:\n制作一张技术讲解封面。画面中央是两个并排的像素风访问凭证卡片，左侧卡片标注 API Key，右侧卡片标注 Bearer Token，中间是醒目的不等号。背景是浅色工程网格纸，加入小型终端窗口、HTTP 请求碎片、像素箭头和微型锁图标。文字保持稀疏，突出“一个字符串，两种含义”。\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":1,"visibleText":["一个字符串","两种含义","API Key ≠ Bearer Token"],"visualStyle":"复古开发者手册感，网格纸背景，像素化接口元素，终端窗口边框，黑色主文字配少量高亮色。","speakerNotes":"开场先回应常见误解：很多初学者会觉得它们都是一个字符串，放进请求就行。但材料明确指出，它们在用途、设计目标、安全性和适用场景上都有明显区别。本页只建立核心悬念：不是看起来像不像，而是它们分别代表什么。","revisedPrompt":"Create exactly one complete presentation slide image, 1536x864 landscape, in the dominant art direction: Neo-Retro Dev Deck / Pixel-Infographic Editorial. Single slide only, finished presentation-ready composition.\n\nSlide topic: API Key 和 Bearer Token 的区别\nCover-style composition. Light cream/off-white engineering notebook grid-paper background with subtle square grid lines. Retro developer-manual feel, slightly rebellious, playful, confident.\n\nVisible text must be EXACTLY these lines and nothing else:\n一个字符串\n两种含义\nAPI Key ≠ Bearer Token\n\nTypography: huge bold geometric sans serif, black, slightly condensed. Make the first line largest, second line medium, third line as a strong headline statement. Keep all text readable and sparse. No extra words, no bullets, no captions, no watermarks.\n\nLayout: Title big at top. In the center, two side-by-side pixel-art credential cards with thick black borders and slight overlap / collage feel. Left card label: API Key. Right card label: Bearer Token. Between them, a large bold not-equal sign (= visually an inequality symbol) in black or hot pink. Surround with small spaced sub-phrase fragments from the visible text and tiny interface notes, but only the three required lines may be visible text; do not add any other readable text.\n\nVisual direction: technical explainer cover. Add small terminal-window frames, HTTP request fragments as abstract pixel shapes (not readable text), pixel arrows, micro lock icons, code-bracket motifs, browser/web execution hints, and subtle motion lines. Use strict palette: hot pink for agent/intelligence accents, bright yellow for code/tools, cyan/light blue for browser/execution, black for text/borders, cream background. Each main element should have one dominant color block. Thick black outlines, 8-bit / 16-bit inspired flat pixel art. Editorial composition with stacked modular blocks, intentional slight overlaps, horizontally aligned header bar feel. No gradients, no realistic photos, no soft shadows, no corporate clean minimalism.\n\nEnsure the slide feels like annotated engineering notes, not a generic infographic. Strong hierarchy, high contrast, high sensibility, coherent with NotebookLM / Kael style. No browser chrome, no extra logos, no signatures, no contact sheet, no multiple slides.","storageFileId":"dpxiybdctw7habj8vsuhky8g-6d315ad8341b9eff81970e5d8ed50baa"},{"size":"1536x864","model":"gpt-image-2","title":"一句话理解","layout":"左右对照卡片。左侧是编号牌和应用图标，右侧是通行证和用户头像。中间用一条像素化分隔线区分。","message":"API Key 更像固定开发者编号，Bearer Token 更像登录后的临时通行证。","imageUrl":"https://cdn.drillso.com/generated/drill/i5ntrv4pbjdzsuhyc0eny2g6-f19ca1f0492caa7e7e153ad04d2e9a14.png","storageKey":"generated/drill/i5ntrv4pbjdzsuhyc0eny2g6-f19ca1f0492caa7e7e153ad04d2e9a14.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: API Key 和 Bearer Token 的区别\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 2: 一句话理解\nMain message: API Key 更像固定开发者编号，Bearer Token 更像登录后的临时通行证。\n\nVisible text must be exactly these lines, with no extra words:\nAPI Key\n固定开发者编号\nBearer Token\n临时通行证\n\nLayout:\n左右对照卡片。左侧是编号牌和应用图标，右侧是通行证和用户头像。中间用一条像素化分隔线区分。\n\nVisual style:\n像 90 年代软件说明书里的对照插图，平面像素图标，粗边框标签，少量荧光高亮。\n\nAdditional image direction:\n制作左右对照式解释图。左侧显示一个应用窗口拿着固定编号牌，标签为 API Key 和 固定开发者编号；右侧显示一个用户头像拿着临时通行证，标签为 Bearer Token 和 临时通行证。中间用像素风竖线分隔，背景为浅色网格纸，加入小箭头和简洁标签，整体像开发者手册中的概念页。\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":2,"visibleText":["API Key","固定开发者编号","Bearer Token","临时通行证"],"visualStyle":"像 90 年代软件说明书里的对照插图，平面像素图标，粗边框标签，少量荧光高亮。","speakerNotes":"用材料中的生活类比帮助听众建立直觉：API Key 像系统发给你的固定开发者编号；Bearer Token 像用户登录后拿到的一张临时通行证。这里不要过度展开，只强调两者不是同一层面的东西：一个偏识别调用方，一个偏表示授权状态。","revisedPrompt":"Create exactly one complete presentation slide image, 1536x864 landscape, in the dominant style of a Neo-Retro Dev Deck / Pixel-Infographic Editorial. Single slide only. Background: light cream/off-white engineering notebook paper with subtle square grid lines, slightly off-register and hand-assembled feel. Strong black thick borders, flat colors, pixel-art illustration, 90s software manual vibe mixed with modern developer marketing, playful but clean and presentation-ready.\n\nSlide topic: compare API Key and Bearer Token in a simple visual analogy. Layout: left-right comparison with two large boxed panels. A pixelated vertical divider line in the center. Left panel: a small application window icon holding a fixed numbered badge/ID card, with a developer/app motif. Right panel: a user avatar icon holding a temporary pass/ticket, with a login/session motif. Use slight overlaps, arrows, and tiny pixel sparks for emphasis. Each panel should have one dominant color block: left panel with bright yellow accents for code/tool identity; right panel with hot pink accents for auth/session identity; use cyan for the central divider or supporting accents. Thick black outlines, flat shading only, no gradients, no soft shadows, no realistic rendering.\n\nTypography: huge bold geometric sans serif for the labels, black text, slightly condensed. Keep text minimal and readable. The only visible text in the entire slide must be exactly these four lines, and nothing else: \nAPI Key\n固定开发者编号\nBearer Token\n临时通行证\nPlace the English title above the Chinese line inside each card, with clean hierarchy. No extra captions, no extra labels, no numbers, no watermarks, no logos, no UI browser chrome.\n\nComposition: editorial and balanced, like a polished developer manual page. Left side should feel like a fixed developer credential card; right side should feel like a temporary access pass after login. Add simple pixel icons and bold framed labels. Ensure the overall slide feels finished, confident, and cohesive with the template.","storageFileId":"i5ntrv4pbjdzsuhyc0eny2g6-f19ca1f0492caa7e7e153ad04d2e9a14"},{"size":"1536x864","model":"gpt-image-2","title":"API Key 识别谁在调用","layout":"流程卡片：客户端带 X-API-Key 请求 API，服务端检查 Key 是否存在、有效、未禁用、未超配额，然后返回资源。","message":"API Key 主要用于识别应用、控制配额、限流和统计调用量。","imageUrl":"https://cdn.drillso.com/generated/drill/dd0geekizk0eoiy45zj1o4q0-8dfceea8addb5739e5507c19900b838b.png","storageKey":"generated/drill/dd0geekizk0eoiy45zj1o4q0-8dfceea8addb5739e5507c19900b838b.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: API Key 和 Bearer Token 的区别\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 3: API Key 识别谁在调用\nMain message: API Key 主要用于识别应用、控制配额、限流和统计调用量。\n\nVisible text must be exactly these lines, with no extra words:\n识别应用\n配额\n限流\n调用统计\n\nLayout:\n流程卡片：客户端带 X-API-Key 请求 API，服务端检查 Key 是否存在、有效、未禁用、未超配额，然后返回资源。\n\nVisual style:\n像素流程图，使用终端代码块样式展示 X-API-Key，服务端校验项以小型检测清单呈现。\n\nAdditional image direction:\n制作一张 API Key 工作方式流程图。左侧是客户端小电脑图标，中间是一段简化请求卡片显示 X-API-Key，右侧是服务器机柜图标。服务器旁有四个小检测项：存在、有效、未禁用、未超配额。下方用小图标表示配额、限流、调用统计。布局清晰，像复古技术手册中的流程示意。\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":3,"visibleText":["识别应用","配额","限流","调用统计"],"visualStyle":"像素流程图，使用终端代码块样式展示 X-API-Key，服务端校验项以小型检测清单呈现。","speakerNotes":"解释 API Key 的定义：它是服务端分配给客户端的一串唯一字符串，用来识别谁在调用 API。材料列出的常见作用包括标识调用者身份、配额控制和限流、统计调用量、提供基础访问控制。也提醒它的局限：通常权限较粗粒度，泄露后容易被直接盗用，不能很好表达某个具体用户已经授权。","revisedPrompt":"Create exactly one complete presentation slide image, landscape 1536x864, in the Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Off-white light cream engineering notebook background with subtle square grid lines. Thick black borders, stacked modular blocks, slight collage overlap, retro-futuristic developer manual feel, pixel-art icons, bold editorial hierarchy. Strict palette: hot pink, bright yellow, cyan/light blue, black, cream. No gradients, no photos, no soft shadows, no corporate minimalism.\n\nSlide topic in Chinese: API Key 识别谁在调用.\n\nThis is Slide 3 of a deck about API Key and Bearer Token differences, but only generate this single slide.\n\nVisible text must be exactly these four lines and nothing else anywhere on the slide:\n识别应用\n配额\n限流\n调用统计\n\nLayout:\n- Main composition is a clear workflow flowchart like a retro technical manual.\n- Left: a small pixel-art client computer icon in a box labeled only with the required visible text line? No extra labels outside the exact four lines. Use the icon and request flow visually, but do not add any extra readable words.\n- Center: a simplified terminal-code style request card with bold monospaced text X-API-Key, presented inside a black-bordered rectangular code block. This is part of the visual; no other words are allowed.\n- Right: a pixel-art server rack / server cabinet icon in a box.\n- Between client and server: arrows showing request and response flow, with small motion chevrons and pixel sparks.\n- Next to the server: a compact checklist panel with four tiny check items represented visually only, corresponding to existence, validity, not disabled, not over quota. Use small check icons and stamped squares; do not add extra readable words beyond the required four visible lines.\n- Bottom row: four small icon tiles using pixel-art symbols to represent quota, rate limiting, and call statistics. These tiles should be colorful and editorial. The only text visible in the entire slide must be the exact four Chinese lines listed above, placed as the bottom captions under the tiles, one line per tile, in that exact order.\n\nTypography and placement:\n- Make the four required Chinese lines large enough to be readable at presentation distance, but keep the rest of the slide mostly diagrammatic.\n- Use bold black geometric sans for the Chinese lines, with slight condensed styling.\n- Use a terminal/code block style for X-API-Key in monospaced black text on a pale yellow card.\n- No extra titles, subtitles, legends, bullets, paragraph text, footer, source notes, or watermarks.\n\nIcon style:\n- Pixel-art, 8-bit/16-bit inspired, flat colors, black outline.\n- Client computer in cyan, server cabinet in hot pink, request card in yellow, flow arrows in black and cyan.\n- Small utility icons for quota, rate limit, statistics: gauge, clock/stopwatch, bar chart, counter dots, etc.\n\nOverall composition should look like a polished retro developer slide: clean, balanced, dense enough to feel finished, but with intentional modular blocks and editorial rhythm.\n\nEnsure the slide looks like a single finished presentation slide, not a wireframe, not multiple slides, not a contact sheet.","storageFileId":"dd0geekizk0eoiy45zj1o4q0-8dfceea8addb5739e5507c19900b838b"},{"size":"1536x864","model":"gpt-image-2","title":"Bearer Token 表示被授权做什么","layout":"登录授权时序图：用户登录，服务端返回 access token，之后请求带 Authorization: Bearer，服务端判断资源访问权限。","message":"Bearer Token 通常用于登录授权，能表达用户、过期时间和访问范围。","imageUrl":"https://cdn.drillso.com/generated/drill/rsmy7bq1hua9913upvslp5wq-83feb8006bb975d7015e611a61442cf3.png","storageKey":"generated/drill/rsmy7bq1hua9913upvslp5wq-83feb8006bb975d7015e611a61442cf3.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: API Key 和 Bearer Token 的区别\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 4: Bearer Token 表示被授权做什么\nMain message: Bearer Token 通常用于登录授权，能表达用户、过期时间和访问范围。\n\nVisible text must be exactly these lines, with no extra words:\n登录后获得\nAuthorization: Bearer\n过期时间\nscope\n\nLayout:\n登录授权时序图：用户登录，服务端返回 access token，之后请求带 Authorization: Bearer，服务端判断资源访问权限。\n\nVisual style:\n横向时序图，像素人物、认证服务器、资源服务器三列，使用发光令牌作为视觉中心。\n\nAdditional image direction:\n制作一张 Bearer Token 登录授权时序图。左侧是用户和 App，中间是认证服务器，右侧是 API 资源服务器。箭头依次表示登录、返回 access token、携带 Authorization: Bearer 请求资源、校验权限后返回资源。令牌以发光像素卡片呈现，旁边标注过期时间和 scope。背景保持浅色网格与复古终端元素。\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":4,"visibleText":["登录后获得","Authorization: Bearer","过期时间","scope"],"visualStyle":"横向时序图，像素人物、认证服务器、资源服务器三列，使用发光令牌作为视觉中心。","speakerNotes":"解释 Bearer Token：它是持有即有效的访问令牌，谁拿着它谁就能用。材料指出它常出现在 OAuth 2.0、OpenID Connect、登录授权系统中。重点不只是识别调用方，而是表示某个用户或客户端已经完成认证，并获得某些资源访问权限。它通常支持过期时间和访问范围 scope，但也需要处理过期、刷新、撤销等机制。","revisedPrompt":"Create exactly one complete presentation slide image, 1536x864 landscape, in Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Single slide only, not a contact sheet.\n\nTopic: Bearer Token 表示被授权做什么\nDeck slide 4 of a Chinese-language presentation about API Key 和 Bearer Token 的区别.\n\nDominant art direction:\n- Light cream/off-white background with subtle engineering notebook grid.\n- Retro-futuristic developer editorial infographic, pixel-art meets startup deck.\n- Thick black borders, modular boxes, slight overlaps, collage-like assembly.\n- Strict palette: hot pink, bright yellow, cyan/light blue, black, cream/white.\n- No gradients, no photos, no soft shadows, no corporate look.\n- Strong typography hierarchy, bold geometric sans serif headline blocks.\n- Pixel art icons and terminal/dev-tool motifs.\n\nLayout:\n- Horizontal authorization sequence diagram across the slide, reading left to right.\n- Left column: 用户 and App, pixel人物 + app icon, in a hot pink framed box.\n- Middle column: 认证服务器, bright yellow framed box, with a glowing access token card as the visual center.\n- Right column: API 资源服务器, cyan framed box, with a resource/database icon.\n- Arrows show: 登录 -> 返回 access token -> 携带 Authorization: Bearer 请求资源 -> 校验权限后返回资源.\n- The token should be a glowing pixel card, centered between auth server and API server, with small labels nearby for 过期时间 and scope.\n- Add small retro terminal elements, chevrons, pixel sparks, and motion lines.\n- Make it feel like annotated engineering notes, not clean corporate PowerPoint.\n\nVisible text must be exactly these lines, with no extra words anywhere on the slide:\n登录后获得\nAuthorization: Bearer\n过期时间\nscope\n\nImportant text placement:\n- Put 登录后获得 as a bold caption near the left/middle login flow.\n- Put Authorization: Bearer on or near the request arrow or token card, large and readable.\n- Put 过期时间 and scope as small labels next to the glowing token card.\n- Do not include any other visible text, titles, subtitles, or labels.\n\nVisual specifics:\n- Use pixel-art style people and server boxes.\n- The access token card should be the brightest element, with a cyan/pink glow effect but still flat pixel-art style.\n- The sequence should clearly imply authorization scope and expiry, with security-check marks or lock-like pixels near the server.\n- Maintain large open margins and strong composition balance.\n- Presentation-ready, polished, and coherent with the style template.","storageFileId":"rsmy7bq1hua9913upvslp5wq-83feb8006bb975d7015e611a61442cf3"},{"size":"1536x864","model":"gpt-image-2","title":"核心区别不是高级与简单","layout":"双栏对比矩阵。左栏 API Key，右栏 Bearer Token。每栏只放三行：表达信息、生命周期、权限粒度。","message":"更本质的区别是：API Key 标识应用，Bearer Token 表示授权会话。","imageUrl":"https://cdn.drillso.com/generated/drill/qx9czu0ipozxzsqprxr0dh9v-0f4847ea3deb507fd7259711a7e00440.png","storageKey":"generated/drill/qx9czu0ipozxzsqprxr0dh9v-0f4847ea3deb507fd7259711a7e00440.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: API Key 和 Bearer Token 的区别\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 5: 核心区别不是高级与简单\nMain message: 更本质的区别是：API Key 标识应用，Bearer Token 表示授权会话。\n\nVisible text must be exactly these lines, with no extra words:\nAPI Key\n你是谁的应用\nBearer Token\n你现在能做什么\n\nLayout:\n双栏对比矩阵。左栏 API Key，右栏 Bearer Token。每栏只放三行：表达信息、生命周期、权限粒度。\n\nVisual style:\n硬边像素表格，黑色粗线框，关键短语用高亮块标出，整体像技术杂志里的速查表。\n\nAdditional image direction:\n制作一张双栏对比矩阵。左栏标题 API Key，包含“应用身份”“长期凭证”“权限较粗”；右栏标题 Bearer Token，包含“授权状态”“短期令牌”“scope 更细”。中间有醒目的分隔线，顶部放一句“表达的信息不同”。背景是浅色网格纸，表格像复古软件手册中的速查卡。\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":5,"visibleText":["API Key","你是谁的应用","Bearer Token","你现在能做什么"],"visualStyle":"硬边像素表格，黑色粗线框，关键短语用高亮块标出，整体像技术杂志里的速查表。","speakerNotes":"材料强调，很多文章只说一个简单、一个高级，但更本质的区别在于它们表达的信息不一样。API Key 更偏向你是谁的应用，常用于识别开发者、项目或客户端。Bearer Token 更偏向你现在被授权做什么，常用于表示登录用户或被授权会话。还可以补充生命周期差异：API Key 往往长期有效，Bearer Token 往往短期有效，所以泄露后的风险窗口通常更短。","revisedPrompt":"Create exactly one complete presentation slide image, 1536x864 landscape, in the dominant art direction of a Neo-Retro Dev Deck / Pixel-Infographic Editorial. Light cream off-white background with subtle square engineering grid. Thick black borders, hard-edged pixel-infographic style, retro software manual mood, modern developer editorial composition, slight controlled collage overlaps, but polished and presentation-ready.\n\nContent must be a double-column comparison matrix with a strong vertical divider. Left column is API Key, right column is Bearer Token. Each column should feel like a technical magazine quick-reference card with chunky black-outlined rectangles and highlighted blocks. Use the palette strictly: hot pink accents for auth/identity, bright yellow for code/tools, cyan/light blue for browser/session/execution, black text and borders, cream background. Add small pixel-art icons and decorative chevrons/gears/arrows, but no extra words anywhere.\n\nVISIBLE TEXT MUST BE EXACTLY AND ONLY THESE FOUR LINES, with no other text anywhere on the slide:\nAPI Key\n你是谁的应用\nBearer Token\n你现在能做什么\n\nTypography: bold geometric sans serif for the English titles, clean readable Chinese sans for the Chinese lines, large and legible. Arrange the text as the main content of the two-column matrix. No top headline, no captions, no labels, no footer, no watermark, no logos, no browser chrome, no extra annotations. Make the slide look finished and editorial, with the matrix clearly communicating contrast using color blocks and icons rather than additional text.","storageFileId":"qx9czu0ipozxzsqprxr0dh9v-0f4847ea3deb507fd7259711a7e00440"},{"size":"1536x864","model":"gpt-image-2","title":"Bearer Token 不一定是 JWT","layout":"两个相交集合图。左圆是 Bearer Token，右圆是 JWT，相交区域写“JWT 可作为 Bearer Token”。旁边放一条简化请求头。","message":"Bearer Token 是令牌的使用方式，JWT 是令牌的数据格式。","imageUrl":"https://cdn.drillso.com/generated/drill/pbp7unsm79seqq8jufzzdlpk-3875265bcbc6e3247387351b3f3ba7f7.png","storageKey":"generated/drill/pbp7unsm79seqq8jufzzdlpk-3875265bcbc6e3247387351b3f3ba7f7.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: API Key 和 Bearer Token 的区别\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 6: Bearer Token 不一定是 JWT\nMain message: Bearer Token 是令牌的使用方式，JWT 是令牌的数据格式。\n\nVisible text must be exactly these lines, with no extra words:\nBearer Token\n使用方式\nJWT\n数据格式\n可以重叠\n\nLayout:\n两个相交集合图。左圆是 Bearer Token，右圆是 JWT，相交区域写“JWT 可作为 Bearer Token”。旁边放一条简化请求头。\n\nVisual style:\n像素化维恩图，带代码标签贴纸，适合开发者快速记忆。\n\nAdditional image direction:\n制作一张概念关系图。画两个相交的像素风圆形集合，左侧为 Bearer Token 并标注 使用方式，右侧为 JWT 并标注 数据格式，相交区域写 可以重叠。右下角放一张小型终端请求头贴纸，显示 Authorization: Bearer。背景为浅色网格纸，使用简洁开发者信息图风格。\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":6,"visibleText":["Bearer Token","使用方式","JWT","数据格式","可以重叠"],"visualStyle":"像素化维恩图，带代码标签贴纸，适合开发者快速记忆。","speakerNotes":"澄清材料中的常见误区：很多人看到 Bearer Token 就想到 JWT，但两者是不同概念。Bearer Token 表示令牌放在 Authorization: Bearer 中，是一种使用方式。JWT 是一种令牌格式。Bearer Token 可以是 JWT，也可以是普通随机字符串；JWT 也常被用作 Bearer Token。","revisedPrompt":"Create exactly one complete presentation slide image, landscape 1536x864, in the dominant art direction of Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nOverall look: retro-futuristic developer infographic on a light cream off-white engineering notebook grid background, subtle square grid lines, thick black borders, modular collage composition, pixel-art icons, bold editorial typography, hot pink + bright yellow + cyan as the main accents, black text and outlines, no gradients, no photos, no soft shadows, no corporate styling.\n\nSlide topic: Bearer Token 不一定是 JWT.\nMain visual: a large pixel-art Venn diagram with two overlapping circles.\n- Left circle: hot pink dominant block, labeled exactly “Bearer Token” with smaller label “使用方式”.\n- Right circle: cyan/light blue dominant block, labeled exactly “JWT” with smaller label “数据格式”.\n- Overlap area: yellow highlight and the exact text “可以重叠”.\nInclude a small code-sticker style terminal/request-header card in the lower right, simplified and developer-like, but DO NOT include any readable extra words or symbols beyond the required visible text. Keep it abstract if needed.\n\nVisible text must be exactly these lines and nothing else:\nBearer Token\n使用方式\nJWT\n数据格式\n可以重叠\n\nComposition: strong hierarchy, slightly overlapping boxes, thick black outlines, playful pixel sparks/chevrons, editorial rhythm, presentation-ready, high sensibility, coherent, not sparse.\nNo other text anywhere.","storageFileId":"pbp7unsm79seqq8jufzzdlpk-3875265bcbc6e3247387351b3f3ba7f7"},{"size":"1536x864","model":"gpt-image-2","title":"怎么选","layout":"决策分叉图。入口是“你的系统目标是什么”，分到 API Key、Bearer Token、两者结合三条路径。底部放安全警示条。","message":"简单开放接口常用 API Key；用户登录、权限控制和第三方授权更适合 Bearer Token。","imageUrl":"https://cdn.drillso.com/generated/drill/jahoo88y18w0gzfaqzzh5ie6-222ddfda80c04dc520c349bc64a4179a.png","storageKey":"generated/drill/jahoo88y18w0gzfaqzzh5ie6-222ddfda80c04dc520c349bc64a4179a.png","imagePrompt":"Create exactly one complete presentation slide image.\n\nUse the following NotebookLM / Kael style prompt as the dominant art direction. Follow it closely.\n\nSTYLE TEMPLATE START\nOverall style name: Neo-Retro Dev Deck / Pixel-Infographic Editorial.\n\nCore visual identity:\n- Retro-futuristic, developer-centric, editorial infographic style.\n- Feels like 90s computer manuals mixed with modern AI dev tools marketing.\n- Pixel art meets startup slide deck.\n- Mood: confident, playful, opinionated, slightly rebellious.\n- Builders explaining the future, not selling fluff.\n\nCanvas and background:\n- Use a light cream or off-white grid paper background.\n- Add subtle square grid lines like an engineering notebook.\n- Slides should feel like annotated engineering notes, not corporate PPTs.\n\nTypography:\n- Primary headline: bold, heavy geometric sans serif, black text, slightly condensed.\n- Headlines may mix the requested language and English.\n- English sub-labels sit under requested-language titles in small clean type.\n- Use huge bold headline blocks, medium subtitles, and small explanatory captions below icons or boxes.\n\nStrict color palette:\n- Hot pink for agent, brain, intelligence concepts.\n- Bright yellow for editor, code, and tools.\n- Cyan or light blue for browser, web, and execution.\n- Black for text and borders.\n- White or cream for background.\n- Each section should have one dominant color block.\n\nLayout language:\n- Stacked modular blocks.\n- Rectangles with thick black borders.\n- Slight intentional overlaps and collage-like assembly.\n- Horizontal section header bars.\n- Card structures for steps, evolution, layers.\n- Controlled imperfection: assembled, not perfectly sterile.\n\nIconography and graphics:\n- Pixel-art style icons: rocket, robot, agent, gear, code brackets, browser window, chat bubbles.\n- Icons should look low-resolution, 8-bit or 16-bit inspired, flat colors, black outline.\n- Decorative elements: small gears, arrows, chevrons, pixel sparks, motion lines.\n\nContent patterns:\n- System architecture slides: stacked layers, each with one color, one icon, one bold title, one short line.\n- Evolution slides: left-to-right progression, each step in its own box; final step is larger and more colorful.\n- Manifesto slides: one huge headline in a boxed frame, minimal text, playful icons around it.\n\nTone:\n- Short, declarative, slightly opinionated.\n- Good: Agents execute tasks autonomously. Coding enters the agent era.\n- Bad: Empowering users with cutting-edge solutions.\n\nAvoid gradients, realistic photos, soft shadows, corporate templates, and quiet minimalism.\nGenerate cohesive multi-slide visuals with consistent grid background, color usage, icon style, and typography hierarchy.\nSTYLE TEMPLATE END\n\nDeck title: API Key 和 Bearer Token 的区别\nDeck summary: 面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。\nDeck format: presenter_slides\nChosen style: Neo-Retro Dev Deck / Pixel-Infographic Editorial\n\nSlide 7: 怎么选\nMain message: 简单开放接口常用 API Key；用户登录、权限控制和第三方授权更适合 Bearer Token。\n\nVisible text must be exactly these lines, with no extra words:\n应用调用应用\nAPI Key\n用户授权访问\nBearer Token\n很多系统会一起用\n\nLayout:\n决策分叉图。入口是“你的系统目标是什么”，分到 API Key、Bearer Token、两者结合三条路径。底部放安全警示条。\n\nVisual style:\n像素决策树，带小型路牌图标和红色警示条，结尾页有明确行动感。\n\nAdditional image direction:\n制作一张选型决策树。顶部入口写“系统目标”。左分支是“简单开发者 API、应用调用应用、基础识别限流”指向 API Key；右分支是“用户登录、权限控制、OAuth 或 OIDC”指向 Bearer Token；中间下方有“也可以一起用：应用识别加用户授权”。底部放安全警示条，包含 HTTPS、环境变量、定期轮换、最小权限。背景保持复古开发者网格纸和像素路牌元素。\n\nRequirements:\n- Canvas: 1536x864 landscape presentation slide.\n- Generate one slide only, not a contact sheet and not multiple slide candidates.\n- Make it presentation-ready, high-sensibility, and coherent with the chosen style template.\n- Make it visually finished, not a sparse wireframe or placeholder diagram.\n- Use the strongest signature elements of the style template: palette, typography, composition language, icon/illustration treatment, and editorial rhythm.\n- Keep all visible text readable at presentation distance.\n- Use low text density, strong hierarchy, and source-grounded diagrams, editorial composition, or template-specific visuals.\n- Do not add markdown symbols, fake logos, watermarks, signatures, UI browser chrome, or extra captions.\n- Match the source/user instruction language for all visible slide text and speaker-facing copy.","slideNumber":7,"visibleText":["应用调用应用","API Key","用户授权访问","Bearer Token","很多系统会一起用"],"visualStyle":"像素决策树，带小型路牌图标和红色警示条，结尾页有明确行动感。","speakerNotes":"收束到选型。材料给出的判断是：如果要开放简单开发者 API，主要是应用调用应用，只需要基础识别、计费、限流，不涉及复杂用户授权，API Key 往往够用。如果有用户登录系统，需要基于用户身份访问资源，需要细粒度权限控制，或打算使用 OAuth 2.0、OIDC，Bearer Token 通常更合适。现实中很多平台会同时使用：API Key 识别应用，Bearer Token 识别用户授权。最后提醒，两者本质上都是敏感凭证，需要 HTTPS、不要写死在前端、不要提交到 Git、使用环境变量、定期轮换、最小权限和监控异常调用。","revisedPrompt":"Create exactly one complete presentation slide image, 1536x864 landscape, in Neo-Retro Dev Deck / Pixel-Infographic Editorial style. Off-white cream engineering notebook background with subtle square grid lines. Thick black borders, modular collage layout, slightly offset assembled feel, pixel-art icons, bold geometric sans headline style. Slide topic: choosing between API Key and Bearer Token.\n\nComposition: a decision tree diagram with strong editorial hierarchy. Top center entry label in a boxed signpost: \"系统目标\". From it, three clear pixel-decision branches flow downward and outward with black arrows and small pixel road-sign icons.\n\nLeft branch box: dominant yellow block, titled exactly \"API Key\" with small supporting text exactly: \"应用调用应用\" and under that small text exactly: \"简单开发者 API\" and exactly: \"基础识别限流\". Visual cue: small pixel code brackets and a key icon. This branch should imply application-to-application access.\n\nRight branch box: dominant cyan/light blue block, titled exactly \"Bearer Token\" with small supporting text exactly: \"用户授权访问\" and under that small text exactly: \"用户登录\" and exactly: \"权限控制\" and exactly: \"OAuth 或 OIDC\". Visual cue: small pixel browser window and user/lock icon. This branch should imply user-authenticated access.\n\nMiddle lower combined box: hot pink accent block, title text exactly: \"很多系统会一起用\". Under it, small supporting line exactly: \"也可以一起用：应用识别加用户授权\". This box should connect from both branches, showing a combined strategy. Use pink as the dominant accent for intelligence/agent concept, but the main decision paths use yellow and cyan.\n\nBottom safety warning strip: full-width red warning bar with thick black border, pixel alert icon, and four short safety notes in small readable text, exactly including these terms: \"HTTPS\", \"环境变量\", \"定期轮换\", \"最小权限\". The bar must feel like a strong caution strip, not a UI banner.\n\nAdd small pixel roadside sign motifs, chevrons, motion lines, and tiny gears around the branches. Keep everything readable at presentation distance, high contrast black text on colored blocks. Retro developer manual vibe mixed with modern AI dev-tool marketing, playful but opinionated, not corporate.\n\nVisible text must be exactly these lines and no extra words beyond labels/necessary diagram text:\n系统目标\nAPI Key\n应用调用应用\n简单开发者 API\n基础识别限流\nBearer Token\n用户授权访问\n用户登录\n权限控制\nOAuth 或 OIDC\n很多系统会一起用\n也可以一起用：应用识别加用户授权\nHTTPS\n环境变量\n定期轮换\n最小权限\n\nNo additional captions, no watermarks, no browser chrome, no logos, no extra paragraphs. Make it look like a finished slide, not a wireframe. Ensure the text is legible and balanced within the 16:9 canvas.","storageFileId":"jahoo88y18w0gzfaqzzh5ie6-222ddfda80c04dc520c349bc64a4179a"}],"styleId":"neo_retro_dev","summary":"面向初学开发者的 7 页讲解型演示：先用生活类比建立直觉，再拆解 API Key 与 Bearer Token 的定义、流程、核心差异、JWT 关系、安全建议和选型方法。","audience":"正在学习 Web API、登录授权、第三方接口调用的初学开发者和产品技术协作人员","imageSize":"1536x864","imageModel":"gpt-image-2","plannerModel":"gpt-5.5"},"children":[]},"breadcrumbs":[{"id":"37cc254f-9d7d-4893-a45a-b72b31f0d63c","slug":"api-key-和-bearer-token-是什么，有啥区别？-37cc254f","title":"API Key 和 Bearer Token 是什么，有啥区别？","type":"page","url":"https://drillso.com/en/share/sessions/B_Qh5EPwQq0l/api-key-%E5%92%8C-bearer-token-%E6%98%AF%E4%BB%80%E4%B9%88%EF%BC%8C%E6%9C%89%E5%95%A5%E5%8C%BA%E5%88%AB%EF%BC%9F-37cc254f","agentUrl":"https://drillso.com/en/share/sessions/B_Qh5EPwQq0l/agent.json?node=api-key-%E5%92%8C-bearer-token-%E6%98%AF%E4%BB%80%E4%B9%88%EF%BC%8C%E6%9C%89%E5%95%A5%E5%8C%BA%E5%88%AB%EF%BC%9F-37cc254f"}],"parent":{"id":"37cc254f-9d7d-4893-a45a-b72b31f0d63c","slug":"api-key-和-bearer-token-是什么，有啥区别？-37cc254f","title":"API Key 和 Bearer Token 是什么，有啥区别？","type":"page","url":"https://drillso.com/en/share/sessions/B_Qh5EPwQq0l/api-key-%E5%92%8C-bearer-token-%E6%98%AF%E4%BB%80%E4%B9%88%EF%BC%8C%E6%9C%89%E5%95%A5%E5%8C%BA%E5%88%AB%EF%BC%9F-37cc254f","agentUrl":"https://drillso.com/en/share/sessions/B_Qh5EPwQq0l/agent.json?node=api-key-%E5%92%8C-bearer-token-%E6%98%AF%E4%BB%80%E4%B9%88%EF%BC%8C%E6%9C%89%E5%95%A5%E5%8C%BA%E5%88%AB%EF%BC%9F-37cc254f"},"children":[],"fullTree":null,"warnings":[],"truncated":false}