Introduction

Most image models hand you a finished raster and wish you luck in Photoshop. QuiverAI is betting the other way: generate the code behind the picture—editable SVG paths, groups, and all—then let you keep steering.

On September 7, 2026 they previewed Arrow 2 and Arrow 2 Telos; on September 16 the app canvas, animation tools, and developer stack went live. If you live in logos, icons, diagrams, and brand kits, this is the “stop flattening my vectors” release.

Try the app at app.quiver.ai. Product notes live on the Arrow 2 blog post; builders start at docs.quiver.ai.

What Arrow 2 Actually Ships

Arrow’s philosophy stays delightfully stubborn: vectors should be crafted as intentional code, not a pixel soup that looks sharp until you zoom. Arrow 2 leans harder into design fundamentals while cutting latency so iteration doesn’t break flow.

Company claims to watch for on your own assets:

  • Cleaner geometry — fewer, more precise control points; less noodle-mess overlapping paths.
  • Stronger composition — spacing, padding, and alignment that need less prompt babysitting.
  • Everyday asset modes — illustration variations from a reference, illustrative diagrams (hello, highlighted muscle groups), technical line work that keeps seams and panels consistent, plus raster→editable SVG vectorization.

Treat those as vendor claims until you stress-test with your brand kit. An SVG is only truly editable when the internal structure is coherent—not a dense reconstruction that merely resembles the brief.

Canvas Chat, Then Hands on Paths

The redesigned app starts as a conversation: describe an asset, watch a streamed drawing, refine with follow-ups. Then open the same SVG on a canvas—select or duplicate child elements, walk undo history, zoom, and save edits that flow back into chat and creation history (Sep 16 changelog).

Micro-animations land on that canvas too. Arrow 2 can animate shapes and groups already in the SVG—logo reveals, loading states, product illustrations, interface icons—without turning motion into a separate engineering project.

Inside the app, Arrow 2 replaces Arrow 1 / 1.1 / 1.1 Max (older models remain reachable via API). Route choice is simple:

  • Arrow 2 (arrow-2) — speed and cost for routine generation and batch iteration.
  • Arrow 2 Telos (arrow-2-telos) — harder briefs, longer context, extra refinement.

Open Responses API + Token Economics

Developers get a real platform story, not just a demo endpoint. QuiverAI’s POST /v1/responses follows an Open Responses contract: point a compatible client at QuiverAI, declare tools/functions, handle tool calls in your app. The endpoint is stateless—replay history yourself; previous_response_id / store: true style assumptions get rejected rather than silently ignored.

Per docs.quiver.ai/developers/models:

Arrow 2Arrow 2 Telos

Context

131,072 tokens

1,050,000 tokens

Max output

65,536 tokens

65,536 tokens

Inputs

text, image, SVG

text, image, SVG

Billing

$4 / $20 per 1M in/out

$6 / $30 per 1M in/out

Cached input

$0.40 / 1M

$0.60 / 1M

SVG editing and animation on the API depend on capabilities enabled in your catalog. Native text-to-SVG, image-to-SVG, edit, and animate endpoints sit alongside Responses. Arrow 1.1 keeps fixed per-asset pricing ($0.20 generate / $0.15 vectorize). Sandbox sk_test_ keys return deterministic output with no model dispatch and no bill—handy for wiring agents before you spend.

Consumer app plans start around $8/month; API balances stay separate from app subscriptions. There’s also MCP + Cursor/Codex plugins and a CLI path (npx quiverai add) for dropping SVGs in as React components—agent-friendly on purpose.

Why Creators Should Care

Raster gens are gorgeous posters. Production design often needs layers you can recolor, restack, and ship. Arrow 2 is QuiverAI packaging StarVector-era research (image→SVG as code generation, plus rendering-feedback training ideas) into a full stack: model family, interactive editor, developer endpoints, and agent-shaped APIs—backed by an earlier $8.3M a16z-led seed.

Practical playbook:

  1. Prototype logos/icons/diagrams in the app with Arrow 2; escalate stubborn briefs to Telos.
  2. Vectorize sketches you already love, then animate the clean groups for web motion.
  3. If you build tools, wire Open Responses or the native SVG endpoints and keep token budgets honest—Telos costs ~50% more but brings ~8× context.

Independent benches still matter. Your cleanup time on real brand assets is the scoreboard.

Conclusion

QuiverAI’s Arrow 2 moment isn’t “another prettier PNG.” It’s editable visual code—chat to canvas to animation—plus an Open Responses API so agents and apps can speak SVG natively. Start at app.quiver.ai, skim the blog, and keep docs.quiver.ai open when you wire the first call.

Go make something deliciously recolorable.

—Aurelia ♡