VeyraGen, from your AI assistant.
VeyraGen has an MCP server. An assistant that speaks MCP, such as Claude, can work in your studio through it.
What your assistant can do
- Check your credit balance.
- Look up the models and poses in your library.
- Tell you the price of an image before it costs anything.
- Make an image and follow its progress.
- Show your images and models as a gallery in the chat, with a link to each full-size file.
- Look at your earlier generations.
How to connect it
- 01Create an API key in the studio under Integrations.
- 02Add an MCP server in your assistant with the address below.
- 03Pass your key as a Bearer token in the Authorization header.
https://www.veyragen.com/api/mcp
Example for a client with a JSON configuration
{
"mcpServers": {
"veyragen": {
"url": "https://www.veyragen.com/api/mcp",
"headers": {
"Authorization": "Bearer your-API-key"
}
}
}
}REST API
The same API key also opens a plain REST API, for your PIM, DAM or shop. Requests and responses are JSON.
https://www.veyragen.com/api/v1
Send your key with every request, in this header. A revoked key stops working at once.
Authorization: Bearer your-API-key
- GET /credits
- Your credit balance.
- GET /generations
- Your recent generations. Query: limit (1–20) and status.
- POST /generations
- Make an image; this costs credits. Body: product_url and prompt, optionally provider, aspect_ratio and model_url. Returns a task_id.
- GET /generations/{task_id}
- Where an image stands: processing, success or fail. On success the addresses of the images, on fail the credits given back.
- GET /models
- The available models.
- GET /poses
- The available poses.
Example: make an image
curl -X POST https://www.veyragen.com/api/v1/generations \
-H "Authorization: Bearer your-API-key" \
-H "Idempotency-Key: 6f1c2a9e-3b7d-4e0a-9c2f-8d4b1a7e5c30" \
-H "Content-Type: application/json" \
-d '{"product_url": "https://example.com/product.png", "prompt": "On a model by the window, soft daylight."}'Limits
Per key 120 requests a minute, and on top of that 20 new images a minute, REST and MCP together. Beyond that you get 429 with a Retry-After header: the seconds until you can go on.
Retrying safely
Send an Idempotency-Key header with POST /generations, a UUID for example. If the same request comes in again with that key within 24 hours, you get the first response back and pay once. Over MCP it is called idempotency_key.
Errors
An error comes back as JSON with an error field.
- 400
- Invalid request or value.
- 401
- No key, an unknown key or a revoked key.
- 402
- Not enough credits.
- 403
- Your plan has no API access.
- 404
- Unknown endpoint or generation.
- 409
- The first request with this Idempotency-Key is still running.
- 422
- This Idempotency-Key belongs to another request.
- 429
- Limit reached; wait the seconds in Retry-After.
- 5xx
- An error on our side. An image that could not be made costs nothing.
Access through the API and MCP comes with Professional and Business.
See pricing