JovethraAPI documentation
JOVETHRA / API REFERENCE

Build with a familiar OpenAI-compatible endpoint.

Use your existing SDK against https://api.jovethra.xyz/v1. The public model is gpt-5.6-sol; usage is metered against your subscription limits.

01 / QUICKSTART

One base URL, one key.

Set the base URL and API key in the OpenAI client you already use. Keep the key server-side and never place it in browser code.

curl https://api.jovethra.xyz/v1/responses \\
  -H "Authorization: Bearer $JOVETHRA_API_KEY" \\
  -H "Content-Type: application/json" \\
  -d '{
    "model": "gpt-5.6-sol",
    "store": false,
    "input": "Summarize this release note in one sentence."
  }'
02 / RESPONSES

Responses API

Use POST /v1/responses for new integrations. Text input, structured output, usage accounting, and tool definitions follow the OpenAI-compatible contract.

const client = new OpenAI({
  apiKey: process.env.JOVETHRA_API_KEY,
  baseURL: "https://api.jovethra.xyz/v1"
});

const response = await client.responses.create({
  model: "gpt-5.6-sol",
  store: false,
  input: "List three concise naming ideas."
});
03 / CHAT COMPLETIONS

Chat Completions

Existing clients can keep using POST /v1/chat/completions. Send the same model name and subscription key; no upstream identity is required.

curl https://api.jovethra.xyz/v1/chat/completions \\
  -H "Authorization: Bearer $JOVETHRA_API_KEY" \\
  -H "Content-Type: application/json" \\
  -d '{"model":"gpt-5.6-sol","messages":[{"role":"user","content":"Hello"}]}'
04 / STREAMING

Server-sent events

Set stream: true on generation requests. Consume the event stream until data: [DONE]; quota accounting is applied to the completed request.

05 / TOOLS

Function calling

Pass tool definitions using the standard tools field. Validate tool arguments in your application before performing side effects, as with any model-generated call.

06 / ERRORS

Predictable errors

HTTP errors use a stable Jovethra error envelope with a public code and request reference. Provider names, upstream URLs, internal model names, and raw provider messages are never part of the client response.

{
  "error": {
    "message": "The API request could not be completed.",
    "type": "gateway_error",
    "code": "service_unavailable",
    "request_id": "jov_..."
  }
}
07 / SUPPORT

Keep support contextual.

Customers can report an issue from the portal. Reports are attached to the subscription order and should include a request reference, never an API key, payment credentials, or full prompts.

General contact: contact@jovethra.xyz