Your first request
starts with your key.

Use one platform API to reach the models enabled for your project. Your platform key authenticates your application; vendor credentials stay on the backend.

Production access is invitation-only. Paid generation requires an enabled provider, an approved execution budget and sufficient workspace credit. Public credit checkout is not yet open.

1. Create your project key

1. Sign in to your workspace and open Developer API.
2. Enter a project and key name. Choose permissions, available models, and daily and monthly spending limits.
3. Select Generate API Key. Copy the key immediately; it is shown once.
4. Store it as VANTAEDGE_API_KEY in your application server's environment. Keep it out of browser bundles, mobile binaries and source control.

2. Discover available models

Send your key as a Bearer token. The response lists the models permitted by the project and currently enabled by the owner.

const response = await fetch(
  'https://new.vantaedge.ai/v1/models',
  { headers: {
    Authorization: `Bearer ${process.env.VANTAEDGE_API_KEY}`
  }}
);

const { data: models } = await response.json();

3. Quote, generate, retrieve

Generation is asynchronous. Review a quote before submitting a job, then poll its status. Use a unique idempotency key for each intended generation and reuse that key if you retry the same submission.

POST https://new.vantaedge.ai/v1/quotes
Authorization: Bearer <your-platform-key>
Content-Type: application/json

{
  "capability": "text",
  "model": "<model-id-from-v1/models>",
  "prompt": "Write a short welcome message."
}

POST https://new.vantaedge.ai/v1/jobs
Authorization: Bearer <your-platform-key>
Content-Type: application/json
Idempotency-Key: <a-unique-request-id>

{ "quoteId": "<id-from-the-quote-response>" }

Poll GET /v1/jobs/{id} until the job succeeds, fails, or requires review. Successful jobs include the result and the recorded charge. The dashboard provides complete copyable JavaScript, Python and cURL examples for your selected model.

4. Operate with clear limits

A quote does not execute a provider call. Job submission checks credit and spending limits atomically. Completed work settles against measured usage; uncertain provider charges remain held for review. Fallback routes require explicit approval.

Rotate keys when replacing credentials and revoke keys immediately when access should end. A rotated or revoked key stops authenticating. Keep separate projects for separate applications and monitor their usage from the dashboard.

Handle 401 for an invalid key, 403 for denied access, 402 for insufficient credit, and 429 for rate or budget limits. Availability errors do not authorize an automatic retry with another provider.