Cursor, OpenCode, Codex, and internal developer agents are harnesses. VAP supplies the model endpoint: an OpenAI-compatible Coding Plan API powered by Nemesis Deep Coder for long-context coding, review, planning, and agent workflows.
vap-code for planning, implementation support, and patch review.
/v1 model contract.
If your harness can call a custom OpenAI-compatible endpoint, point it at VAP and use the Coding Plan API key.
Use Chat Completions for broad compatibility, or the Responses endpoint for agent-style workflows documented in Developer Hub.
curl -X POST https://api.vapagent.com/v1/chat/completions \
-H "Authorization: Bearer YOUR_CODING_PLAN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"vap-code","messages":[{"role":"user","content":"Audit this feature branch and produce an implementation plan."}]}'
Coding Plan API gives these harnesses a flagship reasoning model with a 1 million-token context window, SOTA-level open-source coding performance, long-horizon mission capabilities, and stronger agent engineering.
No. This is a Coding Plan API use case page. The product is Coding Plan API; Cursor, OpenCode, Codex, and internal agent tools are harness surfaces.
No. Coding Plan API uses its own product-scoped key and plan access. Media API keys are for image, video, and music generation.
Use native custom endpoint support where available. Otherwise, route through an adapter, proxy, or internal agent service that speaks OpenAI-compatible /v1.
Generate a Coding Plan API key and use vap-code in your agent workflow.