Vectali

View saved version →

---
name: vectorize-image
description: Convert a user-supplied PNG or JPEG logo, icon, or illustration into SVG with Vectali. Use for requested raster-to-vector conversion, not generating new artwork or general photo editing.
---

Use the Vectali MCP tools for images the user asks to vectorize. Check allowance when the user asks or when needed to explain an account problem; do not add a separate account call before every conversion. API Starter includes 500 successful conversions for $19/month; API and MCP share that allowance. Browser export plans do not cover server conversions. Never initiate a purchase or switch plans as part of conversion. Do not invent higher API tiers; refer users to the current billing page for available plans.

Send the original attachment through `file` to `convert_image` and normally omit `request_id`. Vectali derives a stable ID from the image bytes; identical automatic retries or reattached copies reuse the saved result without another charge. Never ask the user for an ID, URL, credentials or encoded bytes. Never generate, copy, print or re-encode base64 in ChatGPT. Software clients can still supply programmatically encoded bytes for compatibility. Advanced clients can specify an explicit ID for a deliberate new conversion; preserve that ID on retries. The server accepts PNG/JPEG up to 10 MiB, 262144 total pixels and 4096 pixels per side.

When explaining usage, use `allowance_used_this_call`: `1` for a new conversion, `0` for a retry or retrieval. `reused_result` confirms an existing SVG was returned. The legacy `allowance_cost_for_request_id` is a lifetime cost and does not mean this call used another allowance.

Return a short success message and the normal clickable Markdown SVG download link. Keep conversion IDs, path counts and processing statistics internal unless requested. Do not replace the link with a generated button. Note visible limitations only if inspected. The link expires after 10 minutes; use `get_conversion` to refresh it without converting again. Links are bearer capabilities: do not publish them elsewhere without the user's request.

Inspect small lettering, holes, disconnected shapes, edges and gradients when visual access is available. Do not infer quality from byte size, path count or overlap alone. Do not claim an exact recovery of the original vector paths. Never claim to have inspected a result that you have not viewed.

Follow the error’s `next_action` and `retry_after_seconds`. Retry only when `retryable` is true, using the same image and explicit ID, or omitting the ID again. If an attachment fails, ask for the original PNG/JPEG again; do not attempt another encoding. A deleted or unavailable saved result needs a new explicit ID and one new allowance, only if the user wants a fresh conversion. Stop after two retries and explain the error. Authentication, quota and invalid-image errors require an account or input correction; do not loop. Never ask the user to paste credentials into the conversation.