Veo API and MCP: how to add video generation to your project

Veo is a family of video generation models. NeuralSpace offers the following models: Veo 3.1 Quality, Veo 3.1 Fast, Veo 3.1 Lite. They all run through a single public API, and there is a ready MCP server for AI agents. The key is issued on the API keys page. Below are the model capabilities, request examples and setup steps.

What Veo can do

Veo 3.1 generates video from text with a fixed price per clip. Three versions are available: Quality, Fast and Lite, differing in quality and price. Aspect ratios 16:9 and 9:16 are supported, and image_urls lets you pass a source image for image-to-video.

API endpoint

Send a request to POST /v1/videos/generations. Example: {"model": "veo-3.1", "prompt": "a city street at night, camera slowly moving", "aspect_ratio": "16:9"}. Authorization uses an API key in the x-api-key header. Available model ids: veo-3.1, veo-3.1-fast, veo-3.1-lite.

MCP tools

The NeuralSpace MCP server is available at POST /mcp (Streamable HTTP). To work with Veo, an agent uses the tools: generate_video, check_video, list_models, get_balance. This lets Claude Code, Cursor and other MCP clients use the site models directly.

How to connect

Sign up on NeuralSpace, open the API keys page and create an nsk-… key. Then pass it in the request header or in your MCP client settings. Full documentation is on the the /v1/docs page.

FAQ

How does Quality differ from Lite?

Quality gives the best output, Lite is faster and cheaper, Fast is the balance.

Does it support references?

Yes, image-to-video via image_urls.

What format is the request?

POST /v1/videos/generations with model and prompt fields.