Media API
Generate images, video, and music through one VAP integration.
Two product APIs with separate keys and access plans. Start with the integration contract, then generate the key for the product you use.
Generate images, video, and music through one VAP integration.
Connect Nemesis Deep Coder to IDEs, coding agents, and OpenAI-compatible clients.
Separate VAP keys for Media API and Coding Plan API.
Keep each key private. Product access follows the matching active plan.
Image, video, and music generation API.
https://api.vapagent.com/api/v1/generationsimage · video · musicvap_live_…
Your Media API key is hidden for security.
A paid Room or Media plan unlocks your Media API key.
View Room & Media PlansOpenAI-compatible coding endpoint for agents and IDE workflows.
OpenAI Compatiblehttps://api.vapagent.com/v1vap-codeSession + weekly token windowsvap_live_…
Your Coding Plan API key is hidden for security.
A Coding Plan API plan unlocks your product key.
View Coding Plan API plansLive consumption for Media API and Coding Plan API.
A paid plan unlocks your media usage.
View plansA Coding Plan API plan unlocks Nemesis Deep Coder usage.
View Coding Plan API plansEverything you need to call the VAP Media API and Coding Plan API.
Send the matching product key as a Bearer token. Get Media API and Coding Plan API keys under API Keys.
Authorization: Bearer YOUR_PRODUCT_API_KEY
New integrations should use the product APIs below: Media API on /api/v1/generations, and Coding Plan API on OpenAI-compatible /v1 endpoints.
Older /v3/execute and /v3/tasks routes remain live for compatibility with existing integrations, MCP tools, and older agent workflows. They are not the recommended starting point for new Media API builds.
A product plan unlocks the matching surface: Room or Media plans unlock AI Room and Media API keys, while Coding Plan API plans unlock the vap-code endpoints.
Media usage is counted against the active Room or Media plan allowance and shown in Dashboard usage. Coding Plan API usage is governed by its session and weekly token windows. Legacy/custom balance can still appear for older /v3 integrations, but new users should start from the plan-backed product APIs above.
curl -X POST https://api.vapagent.com/api/v1/generations \
-H "Authorization: Bearer YOUR_MEDIA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"kind":"image","prompt":"a neon city at night"}'
kind: image · video · music — prompt: your text.
curl https://api.vapagent.com/api/v1/generations/GENERATION_ID \ -H "Authorization: Bearer YOUR_MEDIA_API_KEY"
Add VAP to Claude Desktop, Claude Code, or any MCP client with your Media API key.
https://api.vapagent.com/mcp
Claude Desktop · config
{
"mcpServers": {
"vap": {
"url": "https://api.vapagent.com/mcp",
"headers": { "Authorization": "Bearer YOUR_MEDIA_API_KEY" }
}
}
}
curl -X POST https://api.vapagent.com/v1/responses \
-H "Authorization: Bearer YOUR_CODE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"vap-code","input":"Review this patch."}'
Responses-compatible endpoint for Codex and agent clients.
curl -X POST https://api.vapagent.com/v1/chat/completions \
-H "Authorization: Bearer YOUR_CODE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"vap-code","messages":[{"role":"user","content":"Review this patch."}]}'
OpenAI-compatible endpoint for IDEs, agents, and coding tools.
curl https://api.vapagent.com/v1/models \ -H "Authorization: Bearer YOUR_CODE_API_KEY"
Use model vap-code. Provider details stay internal to VAP.