VectoKit for developersOne image workflow. API or MCP.
Use your existing VectoKit token balance. Every successful result is saved in your workspace for seven days.
1. Upload an image
Send PNG, JPEG or WebP as multipart/form-data. Maximum 25 MB and 40 megapixels; logo digitization accepts up to 15 MB. Keep keys on your server.
curl https://vectokit.com/api/v1/files \
-H "Authorization: Bearer $VECTOKIT_API_KEY" \
-F "file=@logo.png"
2. Start processing
Use the returned file_id, or supply a directly downloadable HTTPS image_url instead. Redirects and private network URLs are rejected.
curl https://vectokit.com/api/v1/vectorize \
-H "Authorization: Bearer $VECTOKIT_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: unique-request-123" \
-d '{"file_id":"YOUR_FILE_ID"}'Keep the same Idempotency-Key for retries of the same request. It prevents duplicate processing and charges. Use a new key for a new intentional operation.
3. Retrieve your result
The response contains job_id. Poll GET /api/v1/jobs/{id} every five seconds. When status is succeeded, use download_url or the authenticated download endpoint. Signed links expire in ten minutes; requesting job status refreshes them.
Available operations
No free API previews or automatic purchases. Tokens are reserved before processing and returned on technical failure. Requests without enough tokens return 402. Limits return 429 with Retry-After.
Default connection limits: 50 tokens/day, 500/month, adjustable in the workspace. Up to three active jobs per account, 120 requests/minute per connection, and up to 20 retained input uploads (100 MB total) per connection.
MCP for AI assistants
https://vectokit.com/api/mcpRemote Streamable HTTP. Connect through OAuth with PKCE, then review the requested permissions and spending limits. Clients without OAuth can use Authorization: Bearer YOUR_API_KEY in their server configuration.
Tools: vectorize_image, remove_background, upscale_image, digitize_logo, get_account, get_job, list_jobs. Each processing call requires a unique request_id; keep it unchanged when retrying.
Use an accessible HTTPS image URL or upload through the API first. A local path or a ChatGPT attachment ID is not a downloadable image URL. Native attachment delivery varies by client; this initial version does not resolve arbitrary client-local attachments.
Connections can only read their own jobs. API keys do not grant access to billing, passwords or key management. Revoke a connection in the workspace to invalidate its credentials and signed output links.