CometAPI
CometAPI is a unified API gateway that routes requests to more than 500 AI models from over 20 providers through a single OpenAI-compatible key, billed as prepaid credits at rates set below official provider pricing.
What is CometAPI?
CometAPI is an AI model aggregator: a single gateway that resells access to more than 500 models from over 20 providers behind one credential and one endpoint. Instead of holding separate accounts with OpenAI, Anthropic and Google, a developer sends every request to the same address and names the wanted model in the request itself. The catalogue spans GPT, Claude, Gemini, Grok, DeepSeek, Llama, Mistral, Qwen, Kimi and Cohere for text, alongside Sora, Veo, Midjourney, Flux, Kling and Suno for images, video and music, plus speech and real-time models for audio.
The technical proposition is compatibility rather than novelty. The endpoint mirrors the OpenAI API, so code already written against the official Python, Node or Go SDKs keeps working once two values change: the key and the base URL. Moving between providers then becomes a matter of editing one string, which is how the vendor grounds its claim of no vendor lock-in.
The commercial proposition is price. Official models are billed at the provider's published rate multiplied by 0.8, and the pricing page prints the CometAPI rate next to the official one for every model listed, so the discount can be checked line by line. Billing runs on prepaid credits deducted against actual usage, with no monthly fee, no minimum spend and no subscription; unused credits do not expire while the account stays in good standing.
Around that core sit the operational features an aggregator is bought for: intelligent routing and automatic failover between upstream providers, a real-time dashboard reporting spend, latency and call volume, budget alerts, a playground for side-by-side comparison, a public status page with incident history, and a 99.9% monthly uptime commitment backed by a published SLA. The vendor advertises more than 10,000 active developers, average latency under 400 ms and savings of 20 to 40%.
What the site does not supply is corporate substance. No legal entity, registered address or certification appears anywhere: the Trust page states that formal certifications have not been initiated, and the terms place the service under Hong Kong law.
What it does
- Call more than 500 AI models from over 20 providers with a single API key
- Move an existing OpenAI SDK integration across by changing only the base URL and the key
- Switch from one model to another by editing a single string, with no re-authentication
- Generate text, images, video, audio and music from the same endpoint
- Track spend, latency and call volume on a real-time dashboard
- Set budget alerts before spending runs over
- Compare models side by side in the playground before committing to one
When to use CometAPI / When not to
A quick filter to help you decide if CometAPI is the right fit.
When to use CometAPI
- Development teams calling several model providers who want one key, one endpoint and one invoice
- Engineering teams with an existing OpenAI SDK codebase, where only the base URL and the key need to change
- Product teams building multimodal features that mix text, image, video, audio and music generation
- Cost-sensitive production workloads, for which the advertised 20 to 40% discount on provider rates is material
- Automation builders and agencies wiring tools such as n8n, Zapier, Coze or Dify to a single AI account
When not to use CometAPI
- Organisations that require formal security certifications, since the vendor states none have been initiated
- EU compliance teams needing a DPA, a subprocessor list or an Article 27 representative, none of which are published
- Workloads bound by a data residency requirement, as no hosting country or region is disclosed
- Buyers who need a named legal entity and a registered address before signing a contract
- Non-developers looking for a ready-made generation interface rather than a raw API
How to use CometAPI
A typical end-to-end flow, from setup to results.
- Create a free account; no credit card is required and test credits are granted at signup
- Open the dashboard sidebar and select the API Keys section
- Click Create new key and give the key a name
- Copy the key, which starts with sk-, into an environment variable rather than into source code
- Keep your existing OpenAI SDK and point its base URL at the CometAPI endpoint
- Replace the API key value in your client with the CometAPI key
- Name the model you want in the model parameter, choosing it from the online catalogue
- Run a first call to confirm the setup; the vendor times a typical migration at under thirty minutes
- Watch spend, latency and call volume on the dashboard, and set budget alerts
- Enable automatic credit top-up, and follow the public status page for incidents
Pros & Cons
Pros
- One key and one invoice replace an account and a bill per provider
- Migration is genuinely light: two values change in existing OpenAI SDK code
- Each rate is printed next to the official one, so the discount is verifiable model by model
- No subscription and no minimum spend, and credits do not expire while the account is in good standing
- Multimodal breadth is unusual for a single gateway, covering music and video as well as text
- The vendor commits explicitly to not retaining prompts and to not training on API data
- The Trust page is candid, stating plainly that no certification has been obtained
Cons
- No security certification at all; the Trust page says the process has not even been started
- No legal entity name and no postal address appear anywhere on the site
- GDPR documentation is entirely absent: no DPA, no subprocessor list, no Article 27 representative
- No hosting country or region is disclosed, so data residency cannot be assessed
- Prompts necessarily reach the upstream provider, whose policy applies and lies outside the vendor's control
- Credits are generally non-refundable, and refunds are granted at the vendor's sole discretion
- The SLA excludes upstream provider outages, a leading failure mode for an aggregator
Pricing & Plans
There is no permanent free plan. New accounts receive free trial credits at signup without a credit card, and the comparison page advertises one million free tokens. Beyond that the service is pay-as-you-go on prepaid credits, with no monthly fee, no minimum spend and no subscription, so no single entry price can be quoted: charges are per token for text models and per image, clip or second for media models, with official models billed at the provider's rate multiplied by 0.8. Published unit rates are expressed in US dollars and run, by way of example, from 1.20 USD per million tokens for Gemini 3.6 Flash to 8.00 USD per million tokens for Claude Fable 5, while MiniMax H3 video is charged at 0.08 USD per second. Enterprise pricing is negotiated case by case.
- Pay-as-you-go — prepaid credits deducted on actual usage
- with no monthly fee
- no minimum spend and no subscription
- credits do not expire while the account remains in good standing
- and automatic top-up can be enabled
- negotiated rates and volume discounts
- dedicated account manager
- custom SLA
- dedicated servers
- unlimited RPM and TPM
- custom models
- early access to new models
- staff training and integration
Data, GDPR & hosting
A consolidated view of how CometAPI handles your data.
GDPR overview
There is no GDPR implementation to report. Across the twelve pages collected, in visible text and in archived HTML alike, the terms GDPR, CCPA and General Data Protection do not appear once. No EU representative is designated under Article 27, no data protection officer is named, no lawful basis for processing is stated, and no section covers data subject rights such as access, rectification, erasure, portability or objection. No Data Processing Agreement is published or offered, and no subprocessor list exists. The terms place the service under the laws of Hong Kong and the exclusive jurisdiction of its courts. Substantive commitments do exist — prompts are not collected, personal data is not sold, API data is not used for training — but they are made outside any European regulatory framework. Readers subject to the GDPR should treat this documentation as absent rather than merely incomplete.
Who owns the data?
CometAPI states that it neither collects, stores nor records the prompts, inputs, outputs or conversation content passing through the service, and that this material is never written to its databases or to persistent storage. Requests are instead routed in real time to the upstream provider, which necessarily receives the prompt in order to answer and then applies its own data policy. The vendor says it performs no aggregation, no analytics sharing and no secondary use of prompt content on its own side. No clause in the collected terms assigns ownership of generated outputs to either party, so that question is left unanswered by the published documents.
Reuse rights
The published documents neither grant nor restrict any right of reuse over generated outputs: the terms are silent on output ownership, and the only restrictions imposed concern the service itself, which may not be resold, sublicensed or redistributed without prior written authorisation. What the vendor does describe is its own use of data. Technical information is collected automatically — IP address, browser type and version, access date and time, pages visited, device type and operating system, plus limited request logs — and is used for security, compliance, analytics and service optimisation. Account data comes from registration or from GitHub and Google sign-in, with prior consent, and is limited to a username and an email address. It serves account management, transaction processing, service and promotional messages that users may opt out of, and abuse and fraud prevention. CometAPI states that it does not sell, rent or trade personal information, and discloses it only where law or a regulatory authority requires.
Data retention & training
Hosting summary
CometAPI publishes no data hosting location. No country is named on any page, and no region is named either: the About page refers only to a multi-region server architecture, without detailing it. No data residency option is offered, so a customer can neither choose nor verify where processing happens. What the vendor does document is protection in transit: the Trust page states that TLS 1.2 or above is enforced, and the enterprise page claims end-to-end encryption. The About page adds that data in transit is never persisted longer than immediate processing requires. One network fact should not be mistaken for hosting information: the domain resolves to an Amazon CloudFront edge node geolocated in Zurich, which describes how the marketing site is delivered, not where customer data is processed or stored. Jurisdiction, by contrast, is explicit: the terms place the service under the laws of Hong Kong and the exclusive jurisdiction of its courts.
Things to keep in mind
Risks and trade-offs to weigh before adopting CometAPI.
- The vendor holds no security certification and says none has been initiated; SOC 2 Type II is only a roadmap item
- No legal entity, registration number or postal address is published, leaving no identified counterparty behind an enterprise contract
- Prompts leave the gateway for the upstream provider, so the no-retention promise stops at CometAPI's own boundary
- Prepaid credits are generally non-refundable and approval is discretionary, which places the balance risk on the customer
- The SLA excludes upstream provider failures, the very outages an aggregator is bought to absorb
- Performance and savings figures are vendor claims with no third-party verification, and the catalogue and prices change quickly
- Concentrating every provider behind one credential creates a single point of failure and a single key worth compromising
Setup & Integrations
Technical difficulty
Low for a developer, out of reach for anyone else. Nothing is installed: the official OpenAI SDK is reused as is, and only two values change, the API key and the base URL. Keys start with sk- and are created from the dashboard in a step the vendor times at sixty seconds, while a typical migration is announced as taking under thirty minutes with no rewrite of business logic. Compatibility is claimed for the Python, Node and Go SDKs. The real prerequisite is being able to call an API and handle a secret safely.
Deployment
Integrations
Supported languages
Behind CometAPI
Social
Resources
All the official URLs gathered for verification and reference.
Alternatives
Tools that compete with or complement CometAPI.
Frequently asked questions
What is CometAPI?
How do I migrate an existing OpenAI integration?
How does billing work?
Is there a free plan or a free trial?
Why is it cheaper than going direct to the provider?
Are my prompts stored, and are they used for training?
Does CometAPI hold security certifications?
What happens if a generation fails, and can I get a refund?
What uptime is guaranteed?
Should you pick CometAPI?
CometAPI does what an API aggregator is supposed to do, and does it legibly. One key reaches more than 500 models, the endpoint is a genuine drop-in for the OpenAI SDK, and the discount is not a slogan but a published figure set beside each provider's official rate. Operationally it is more mature than its size suggests: a 99.9% SLA with a defined downtime rule and a claims procedure, a public status page, billing rules that spell out when a failed generation is charged, and a dashboard that makes spending visible before it becomes a surprise.
The reservations are contractual rather than technical, and they are substantial. No legal entity, registration number or postal address is published anywhere on the site, which is unusual for a vendor selling to enterprises. No security certification exists — the Trust page says the process has not been started — and there is no GDPR documentation whatsoever: no Data Processing Agreement, no subprocessor list, no Article 27 representative, no data subject rights. No hosting country or region is disclosed. The service is governed by Hong Kong law.
To the vendor's credit, none of this is concealed. The Trust page refuses explicitly to claim certifications it does not hold, and the About page is candid that prompts must reach the upstream provider, whose own policy then applies — which means the no-retention promise stops at CometAPI's own boundary.
The trade is therefore clear. Teams optimising for cost, model breadth and integration speed will find the offer strong and the claims unusually checkable. Teams that must answer a procurement questionnaire, prove data residency or sign with an identified counterparty will not get past the first page. Verify current rates and catalogue before committing: the vendor itself advises it.
- Choosing a selection results in a full page refresh.
- Opens in a new window.