{"id":"chatcmpl_codxer_mrjvzhjh_acmdnhoxj4","object":"chat.completion","created":1783987316,"model":"CodXER-Low-2-X1.0","choices":[{"index":0,"message":{"role":"assistant","content":"Hello! How can I help you today?"},"finish_reason":"stop"}],"usage":{"prompt_tokens":1901,"completion_tokens":141,"total_tokens":2042},"_codxer":{"provider":"agixer","codxer_model":"CodXER Low-2 X1.0","upstream_model":"CodXER-Low-2-X1.0"}}
curl --location --request POST 'https://zylalabs.com/api/13186/artificial+intelligence+chat+api/26807/chat+completions' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"model": "CodXER Low-2 X1.0",
"messages": [
{
"role": "user",
"content": "Hello"
}
],
"max_tokens": 256
}'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Artificial Intelligence Chat API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
This API generates text responses for chat, reasoning, coding and content generation. It accepts structured text prompts and returns generated text in JSON responses. It supports streaming responses and model routing. It can be integrated into websites, mobile applications, automation workflows and software agents through HTTPS requests.
The Chat Completions endpoint returns a JSON object containing generated text responses based on input messages. It includes details such as the assistant's reply, usage statistics, and model information.
Key fields in the response include "id" (unique identifier), "object" (response type), "created" (timestamp), "model" (used model), "choices" (generated messages), and "usage" (token counts).
Users can customize requests using parameters like "messages" (input messages), "temperature" (response randomness), and "max_tokens" (response length). These parameters help tailor the output.
The response data is structured as a JSON object. It contains an array of "choices," each with a "message" field that includes the assistant's content and a "finish_reason" indicating how the response ended.
Typical use cases include customer support chatbots, coding assistance, content generation, and interactive applications where users seek conversational AI responses.
Users can extract the "content" field from the "message" object to display the assistant's response. Additionally, they can analyze "usage" data to monitor token consumption for optimization.
Data accuracy is maintained through continuous model training and updates based on user interactions and feedback. This ensures that the AI generates relevant and contextually appropriate responses.
If the response contains partial or empty results, users should check the "finish_reason" field for context. They can also adjust input parameters to refine the request for more complete outputs.
The Chat Completions endpoint provides generated text responses based on user input messages. It includes the assistant's reply, token usage statistics, and metadata about the model used for generation, allowing for diverse applications in chat, coding, and content creation.
Users can customize requests by adjusting parameters such as "messages" (input text), "temperature" (to control randomness), and "max_tokens" (to limit response length). This flexibility allows for tailored interactions based on specific needs.
The JSON response is structured with fields like "id," "object," "created," "model," and an array of "choices." Each choice contains a "message" with the assistant's content and a "finish_reason" that indicates how the response concluded.
The "finish_reason" field provides context on how the response was generated. It can indicate whether the response completed normally, was truncated, or stopped due to reaching a token limit, helping users understand the output's completeness.
The "usage" data includes "prompt_tokens," "completion_tokens," and "total_tokens," which help users monitor their token consumption. This information is valuable for optimizing requests and managing resource usage effectively.
Common scenarios include developing chatbots for customer support, creating coding assistants for developers, generating content for blogs or articles, and building interactive applications that require conversational AI capabilities.
The API maintains response quality through continuous model training and updates based on user interactions. Feedback loops help refine the models, ensuring they produce relevant and contextually appropriate outputs.
If responses are unexpected or incomplete, review the "finish_reason" for insights. Adjusting input parameters like "temperature" or "max_tokens" can help refine the output. Additionally, providing clearer prompts may yield better results.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund