For Agents
Call 500+ language, embedding, image, and audio models through one OpenAI-compatible endpoint with a single bearer token.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CometAPI, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with CometAPI API.
Generate chat completions across 500+ models via POST /chat/completions
Create vector embeddings via POST /embeddings for retrieval and semantic search
Generate images from text prompts via POST /images/generations
GET STARTED
Use for: I need to call GPT-4 and Claude through one API, Generate an embedding for a chunk of text, Create an image from a prompt using a single gateway, Transcribe an audio file to text
Not supported: Does not handle model fine-tuning, vector storage, or agent orchestration — use for OpenAI-compatible inference across multiple model providers only.
Jentic publishes the only available OpenAPI specification for CometAPI, keeping it validated and agent-ready. CometAPI is an OpenAI-compatible gateway that fronts 500+ underlying models (GPT-4, Claude, Gemini, Llama, and more) behind a single bearer token. The surface mirrors the OpenAI v1 shape: chat completions, text completions, embeddings, image generation, and audio transcription or synthesis. It lets agents and applications swap or combine models without learning each provider's auth and request format.
Transcribe uploaded audio to text via POST /audio/transcriptions
Synthesise speech from text via POST /audio/speech
List and inspect available models via GET /models and GET /models/{model}
Patterns agents use CometAPI API for, with concrete tasks.
★ Multi-Model A/B Routing
Route the same prompt to GPT-4, Claude, and Gemini through CometAPI's /chat/completions endpoint by changing only the model field. This makes it cheap to evaluate which model gives the best result for a specific task type without integrating three separate provider SDKs and three separate billing relationships.
Send the same prompt to /chat/completions three times with model values gpt-4o, claude-3-5-sonnet, and gemini-1.5-pro and return all three responses
Embeddings Pipeline for RAG
Use POST /embeddings to vectorise a corpus of documents, then store the vectors in a downstream vector database for retrieval-augmented generation. Because CometAPI is OpenAI-compatible, existing LangChain, LlamaIndex, or custom RAG code that targets the OpenAI embeddings shape can point at CometAPI by changing only base URL and key.
Embed a list of 50 documents via /embeddings using the text-embedding-3-large model and return one vector per input
Voice Note Transcription Bot
Build a Slack or Telegram bot that accepts voice notes and replies with a text transcript by uploading the audio to POST /audio/transcriptions. Combine with /audio/speech to produce spoken replies. The OpenAI-compatible shape means existing Whisper-based code can be reused without changes beyond auth.
Upload an mp3 file to /audio/transcriptions and return the transcribed text
AI Agent Model Selection via Jentic
An AI agent connected to Jentic can pick the right CometAPI model at runtime: search Jentic for the chat completion operation, list available models via /models, and execute against the chosen one. Jentic stores the bearer token in the MAXsystem vault so the agent never sees the raw key.
Search Jentic for 'send a chat completion through cometapi', load the operation, and execute with model gpt-4o and a user message
8 endpoints — jentic publishes the only available openapi specification for cometapi, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/chat/completions
Create a chat completion
/completions
Create a text completion
/embeddings
Create vector embeddings
/models
List available models
/models/{model}
Get model details
/images/generations
Generate an image from a prompt
/audio/transcriptions
Transcribe audio to text
/audio/speech
Generate speech from text
/chat/completions
Create a chat completion
/completions
Create a text completion
/embeddings
Create vector embeddings
/models
List available models
/models/{model}
Get model details
Three things that make agents converge on Jentic-routed access.
Credential isolation
The CometAPI bearer token is stored encrypted in the Jentic vault (MAXsystem). Agents call operations via Jentic and receive the response — the raw token is never injected into the agent context window.
Intent-based discovery
Agents search Jentic by intent (e.g., 'send a chat completion through cometapi') and Jentic returns the matching operation with its full input schema, so the agent calls the right endpoint without reading CometAPI docs.
Time to first call
Direct CometAPI integration: 1-2 hours to swap base URL and key from an existing OpenAI client. Through Jentic: under 30 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using CometAPI API through Jentic.
Why is there no official OpenAPI spec for CometAPI?
CometAPI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CometAPI via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does CometAPI use?
CometAPI uses a bearer token in the Authorization header (Authorization: Bearer <key>), matching the OpenAI auth shape. Through Jentic the key is stored in the MAXsystem vault and never enters the agent's context.
Is CometAPI really OpenAI-compatible?
Yes. The /chat/completions, /completions, /embeddings, /images/generations, and /audio/* endpoints follow the same request and response shape as the OpenAI v1 API, so OpenAI client libraries work by overriding base_url to https://api.cometapi.com/v1.
Can I switch models without changing my code?
Yes. Send the model field in the /chat/completions body to route to a different underlying model. Use GET /models to list every model available on your CometAPI key.
What are the rate limits for CometAPI?
Rate limits depend on the plan tier and the underlying model. CometAPI returns 429 with a Retry-After header when limits are hit; clients should back off and retry. Heavy embeddings or image workloads should be batched.
How do I send a chat completion through Jentic?
Search Jentic for 'send a chat completion through cometapi', load the schema for POST /chat/completions, and execute with model and messages. The Jentic Python SDK pattern is await client.search(...), await client.load(...), await client.execute(...).
/images/generations
Generate an image from a prompt
/audio/transcriptions
Transcribe audio to text
/audio/speech
Generate speech from text