CometAPI

Name: CometAPI API
Brand: CometAPI
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLLanguage Modelsbearer8 EndpointsREST

For Agents

Call 500+ language, embedding, image, and audio models through one OpenAI-compatible endpoint with a single bearer token.

Quickstart

Get started with CometAPI in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a chat completion through cometapi"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

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

Transcribe uploaded audio to text via POST /audio/transcriptions

Synthesise speech from text via POST /audio/speech

GET STARTED

Start building with CometAPI API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for CometAPI, keeping it validated and agent-ready.

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.

Use Cases

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

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for cometapi, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/chat/completions

Create a chat completion

POST

/completions

Create a text completion

POST

/embeddings

Create vector embeddings

GET

/models

List available models

GET

/models/{model}

Get model details

POST

/images/generations

Generate an image from a prompt

POST

/audio/transcriptions

Transcribe audio to text

POST

/audio/speech

Generate speech from text

POST

/chat/completions

Create a chat completion

POST

/completions

Create a text completion

POST

/embeddings

Create vector embeddings

GET

/models

List available models

GET

/models/{model}

Get model details

POST

Why though Jentic?

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.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

OpenRouter

OpenRouter is the closest equivalent multi-model gateway with the same OpenAI-compatible shape.

Choose OpenRouter when you want explicit per-model pricing visibility and route-level controls; choose CometAPI for a wider model catalogue with one bearer token.

Alternative

OpenAI API

OpenAI is the upstream OpenAI-only API; CometAPI proxies it alongside other providers.

Use OpenAI directly when you only need OpenAI models and want first-party support; use CometAPI to cover OpenAI plus Claude, Gemini, and Llama in one integration.

Alternative

Groq API

Groq is OpenAI-compatible but limited to its own hosted models with very low latency.

Choose Groq when latency is the top constraint on a supported open model; choose CometAPI for breadth across closed and open models.

FAQs

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(...).