---
name: svgai-create-vector
description: Create SVG concepts from prompts or image references, or vectorize existing raster artwork with SVG AI. Use for an authorized SVG generation or tracing task that needs complete output files and a target-size check.
metadata:
  requirements: Network access and an SVG AI API key or OAuth-capable MCP client. Generation and vectorization require paid account access and available credits.
---

# Create and inspect an SVG with SVG AI

## When to use this

| User's task | Operation | What to check |
| --- | --- | --- |
| Make a new icon, logo concept or illustration from a brief | POST /api/v1/generate or MCP generate_svg | Inspect the result against the brief and intended display size. |
| Reinterpret an owned image in a new style or composition | Generate with an image reference and a prompt | The generator can change lettering, palette, geometry and framing. |
| Turn an existing raster design into vector paths | POST /api/v1/vectorize or MCP vectorize_image | Start with the cleanest source; tracing can still change edges and colors. |
| Change an exact fill, coordinate or accessibility attribute in an existing SVG | Edit the SVG in the user's available code/vector workflow | A new paid generation is usually unnecessary for a known source-value change. |

Use generation for new concepts and vectorization for tracing. For input fields and supported image types, consult the [OpenAPI contract](https://www.svgai.org/openapi.json).

## Establish the permitted request

Identify the intended use, smallest display size, transparency requirement and features that must remain exact. Use images the user supplied or is authorized to use. For a matching set, establish one anchor before spending on the remaining subjects.

Use the [authentication reference](https://www.svgai.org/auth.md) to connect with an API key or MCP OAuth. Keep credentials in request headers or the client's credential storage, never in URLs or delivered files. If an account connection is missing, give the user the [API and MCP console](https://www.svgai.org/dashboard/api) link.

Read authenticated GET /api/v1/credits or MCP get_credits before billable work. Check api_access, the available balance and current operation costs against the user's task budget. Stay within the requested number of attempts; obtain permission before buying credits or increasing the budget. Website starter credits alone do not unlock API use. If paid access or credits are unavailable, explain what the account needs.

## Generate or vectorize

For a new concept, supply a concise subject, intended use, visual style and important constraints. Choose the requested model and variations within the budget. Send image or image_url when needed, never both. A minimal REST request body for one new draft is:

```json
{
  "prompt": "One simple outline envelope for a messaging button, no lettering, readable at 24px",
  "model": "classic",
  "variations": 1,
  "aspect_ratio": "square",
  "transparent_background": "on",
  "wait": false
}
```

Send this example body to POST https://www.svgai.org/api/v1/generate with the user's API-key header. Check the current cost before sending it. For MCP, use the connected server's generate_svg tool and its advertised input schema.

For tracing, send an image to POST /api/v1/vectorize or MCP vectorize_image. Set remove_background only when requested; inspect background_removed to learn whether that optional operation succeeded. Do not reinterpret a fidelity task as permission to redesign the image.

## Finish an accepted request before retrying

Preserve the generation ID and any poll_url in a processing response. Poll that accepted generation using the same account's credentials until it completes or fails. A completed generation returns SVG markup in its svgs entries; vectorization returns svg directly. Do not call a processing preview or a null SVG a finished deliverable.

Creation requests are not idempotent. A timeout can occur after acceptance, so do not repeat the creation request just because the first response was delayed. If no generation identifier was received, report the uncertain outcome and resolve it before spending again. For rate_limit_exceeded, respect retry_after_seconds when provided; for other errors, follow the [error reference](https://www.svgai.org/docs#errors).

## Inspect and deliver

Save the complete returned SVG and inspect its markup and rendering. Check the viewBox, visible bounds, requested colors, lettering, embedded images, and transparency on the intended background. Render at the requested CSS size; a large preview does not establish 24px readability.

When an exact manual correction is useful, preserve the generated result and save the manual version separately. Explain any unrequested geometry or palette changes. Deliver the SVG file with a short description of the changes and any remaining visual limitations. Keep API keys, account balances and private reference material out of shared files.

For request examples and setup details, use the [documentation index](https://www.svgai.org/docs/llms.txt). For plans and credit packs, consult [current pricing](https://www.svgai.org/pricing.md).