The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Mar 24, 2026 1:02am

PR Summary

Medium Risk
Introduces new API routes that accept user-provided files/URLs and proxy requests to an external service, which can impact security, reliability, and payload handling if validation/limits are off.

Overview
Adds a new QuiverAI integration end-to-end: a QuiverBlock with operation selection (text-to-SVG, image-to-SVG, list models), API-key auth, and file/reference inputs that normalize into tool params.

Implements new internal API routes for quiver_text_to_svg and quiver_image_to_svg that validate inputs with zod, resolve uploaded files via the existing storage pipeline, call Quiver’s external API, and return generated SVGs as base64-encoded file/files outputs with usage metadata.

Registers the new Quiver tools in the tool and block registries, adds a QuiverIcon plus icon mappings, and publishes new docs content (tools/quiver.mdx) and metadata updates so the integration appears in the docs and landing integrations list.

^{Written by Cursor Bugbot for commit da17505. Configure here.}

Greptile Summary

This PR adds a full QuiverAI integration with three operations — Text to SVG, Image to SVG, and List Models — following the established block/tool/route pattern used throughout the codebase. The two generative tools proxy through internal Next.js API routes (handling file download and base64 conversion server-side), while list_models calls the Quiver API directly, which is appropriate since no file handling is required.

Key changes:

• New tool configs (text_to_svg, image_to_svg, list_models) under apps/sim/tools/quiver/ with correct user-only visibility on apiKey params
• Internal proxy routes at /api/tools/quiver/text-to-svg and /api/tools/quiver/image-to-svg for server-side file handling
• Block definition with operation dropdown, conditional file-upload subBlocks, and advanced mode params
• Icon, registry, icon-mapping, and docs additions all consistent with existing patterns

One issue to address: The params transformer in quiver.ts uses JavaScript truthiness to gate numeric params (temperature, top_p, etc.). This works in the typical UI path where values are strings, but will silently drop a value of 0 if a numeric zero is passed in programmatically (e.g. from a connected block or LLM). The route handlers already use != null for these checks — the block params should align with that pattern.

Confidence Score: 4/5

• Safe to merge after addressing the numeric-zero silent-drop bug in the block params transformer.
• The integration is well-structured and follows all existing patterns. API key visibility is correctly set to user-only, file handling is properly server-side proxied, and the route handlers are solid. The one concrete issue — truthiness guards on numeric params that would silently drop a value of 0 — is a targeted, low-risk fix that doesn't affect the primary happy path from the UI.
• apps/sim/blocks/blocks/quiver.ts — the params transformer's truthiness checks for numeric values

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant UI as Quiver Block (UI)
    participant TR as Tool Runner
    participant TTS as /api/tools/quiver/text-to-svg
    participant ITS as /api/tools/quiver/image-to-svg
    participant Store as File Storage
    participant QAI as api.quiver.ai

    Note over UI,QAI: Text to SVG flow
    UI->>TR: quiver_text_to_svg(prompt, model, refs?)
    TR->>TTS: POST {apiKey, prompt, model, references?}
    TTS->>Store: downloadFileFromStorage(ref)
    Store-->>TTS: Buffer
    TTS->>QAI: POST /v1/svgs/generations {model, prompt, references[base64]}
    QAI-->>TTS: {data:[{svg}], id, usage}
    TTS-->>TR: {success, output:{file, files, svgContent, id, usage}}
    TR-->>UI: outputs

    Note over UI,QAI: Image to SVG flow
    UI->>TR: quiver_image_to_svg(model, image)
    TR->>ITS: POST {apiKey, model, image}
    ITS->>Store: downloadFileFromStorage(image)
    Store-->>ITS: Buffer
    ITS->>QAI: POST /v1/svgs/vectorizations {model, image:{base64}}
    QAI-->>ITS: {data:[{svg}], id, usage}
    ITS-->>TR: {success, output:{file, svgContent, id, usage}}
    TR-->>UI: outputs

    Note over UI,QAI: List Models flow
    UI->>TR: quiver_list_models(apiKey)
    TR->>QAI: GET /v1/models (Authorization: Bearer apiKey)
    QAI-->>TR: {data:[{id, name, ...}]}
    TR-->>UI: {success, output:{models}}

_{Reviews (3): Last reviewed commit: "fix(quiver): add files array to image-to..." | Re-trigger Greptile}

All three issues addressed in 9ab80e3:

1. n > 1 data loss: Route now returns all generated SVGs in a files array. file still returns the first for backward compat.
2. list_models error handling: response.ok is now checked before response.json(), with a try/catch for non-JSON error bodies.
3. Import consistency: Updated ./types to @/tools/quiver/types.

@greptile @cursor review

@cursor review

@cursor review

@greptile