MindsHub
Star — Console Sign Up

Unified Inference

Call leading models through one API.

Use OpenAI or Anthropic SDKs to call the same model catalog with one key and one prepaid balance.

Get an API key Start with the docs
Switch an existing client

Change the base URL, not your client.

Point your code at api.mindshub.ai and use a short model alias. Copy the command on the right to test the endpoint.

  • OpenAI SDKs use https://api.mindshub.ai/v1 with api_key.
  • Anthropic SDKs use https://api.mindshub.ai without /v1 and require auth_token, so the client sends Authorization: Bearer.
Which API should I use? →
Model 
curl https://api.mindshub.ai/v1/chat/completions \
  -H "Authorization: Bearer $MINDSHUB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "sonnet",
    "messages": [{"role": "user", "content": "Hello"}]
  }'

OpenAI- and Anthropic-compatible endpoints — point your existing SDKs and tools at api.mindshub.ai.

Developer docs → Get your API key →
  1. Short aliases Switch models by changing one string
  2. Three request formats Use the client you already have
  3. Tools and streaming Keep each protocol’s event format
  4. Usage billing One prepaid organization balance

Invitation · limited places

Join the MindsHub Foundry

Test the API with direct access to the product team

We’re looking for teams willing to use the API in production and tell us where it falls short.

Members receive · spend matching

100% match up to $5,000

A 100% match on your first 3 months of inference-credit purchases, up to $5,000 — matched against the credits you buy, not a grant.

Members receive

  • Direct product and technical support
  • Early access to new features and capabilities

Who we’re looking for

Teams already building or operating AI products, workflows, or services that:

  • Plan to use MindsHub Inference during the program
  • Can share specific feedback from that work
  • Can join regular calls with our product team

Applications are reviewed on a rolling basis and take about 3–5 minutes to complete. Applying does not guarantee acceptance.

Choose your API

Use the request format you already have.

All three formats reach the same catalog and the same bill. Start with Chat Completions for new work; use Messages for Anthropic SDKs and Claude Code.

Anthropic Production

Messages

POST /v1/messages

Use Anthropic SDKs or Claude Code with auth_token and the base URL without /v1.

Open the Messages guide →
OpenAI Mid-upgrade

Responses

POST /v1/responses

Input is accepted today, but Responses-shaped output and SDK helpers are still upgrading. Use Chat Completions for production.

Read the current Responses status →
Developer documentation From first key to production request.
Getting started Choosing an API Browse all docs →
Stable model aliases

Use short model aliases.

An alias can move to a newer model without changing your code. This list comes from the live catalog; GET /v1/models shows what your organization can use.

See prices on the rate card Compare them on quality, speed and cost → Model aliases + GET /v1/models →
Pay as you go

One balance for the whole catalog.

By default, organizations receive 5 million included monthly tokens on mindshub_air. Every other model, embeddings, web search, and priced cache writes draw from one prepaid organization wallet.

Input, output, cached input, and cache writes are metered separately. Cached input is roughly a tenth of the ordinary input rate. Included-token limits can vary by organization — your entitlements response is authoritative.

Read the billing docs See the rate card →
Conversation history / repeated prefix Metered
First request · write System prompt + history input + cache write
Request 02 · read Repeated prefix ~1/10 input rate
Request 03 · read Repeated prefix ~1/10 input rate
Request 04 · read Repeated prefix ~1/10 input rate

Caching is automatic on most of the catalog. Claude-family models use cache_control breakpoints on Messages.

Parameter adaptation

Handle common parameter differences.

Supported parameters pass through. Unsupported ones are dropped and out-of-range values are clamped. Response headers name every change. 

POST /v1/chat/completions        model: gemini-flash
  top_k · max_tokens · reasoning_effort

← 200 OK
  X-MindsHub-Dropped-Params: top_k
  X-MindsHub-Clamped-Params: max_tokens=requested>applied

Nothing changed? No adaptation headers. Provider value restrictions can still return a 400.

Streaming

Keep your existing stream parser.

Chat Completions and Messages keep their own event, completion, and error formats.

Compare API behavior →
Tools + images

Send tools, images, and search requests.

Function tools, image input, and built-in web search are supported where the selected model and request format support them.

See working examples →
Usage

Review usage by model.

API and agent requests appear in the same organization usage summary, grouped by model.

Usage and wallet docs →
One engine

All formats use the same catalog and balance.

Every request format reaches the same models, the same wallet, and the same usage summary.

Compare all three APIs →
  1. POST /v1/chat/completions Production
  2. POST /v1/messages Production
  3. POST /v1/responses Mid-upgrade
  4. GET /v1/models Live
  5. POST /v1/embeddings Live
  6. Usage summary Live
Want a ready-made workspace?

Use the same models in Cowork.

Describe a project, connect its data, and get back documents, dashboards, or apps. Cowork uses the same catalog and balance, with no client to build.

Explore Cowork Start in your browser →
MindsHub Cowork — a briefed project running in the workspace, with its finished artifacts listed alongside.
FAQ

Questions before you switch.

Which API should I use?
Use Chat Completions for new integrations and Messages for Anthropic SDKs or Claude Code. Responses is still being upgraded, so use Chat Completions for production.
Which base URL and auth field do I use?
OpenAI SDKs use https://api.mindshub.ai/v1 with api_key. Anthropic SDKs use https://api.mindshub.ai without /v1 and must use auth_token — not api_key — so the client sends the Authorization: Bearer header.
How does billing work?
There is no subscription. Organizations receive a monthly allowance on mindshub_air by default; limits can vary. Other usage draws from a prepaid organization balance at the rates on the pricing page.
Does conversation chaining work?
No. Keep conversation history client-side and send the full history on each turn. Prompt caching makes repeated prefixes cheaper on most models; previous_response_id and store are accepted but not honored.
How do aliases and availability work?
Use short aliases such as sonnet, gpt, and kimi. An alias can move to a newer model without a code change. GET /v1/models shows the live catalog and what your organization can use.
Can I bring my own provider key?
Not today. Bring-your-own-key is planned, not available. The current service uses one MindsHub key and one organization wallet.
How does this relate to MindsHub Cowork?
Cowork is a ready-made workspace that uses the same model catalog. Unified Inference is the API for your own software. They share one account and balance.
Get started

Make your first request.

Create a key, follow the getting-started guide, and test the endpoint. There is no subscription.

Get an API key Start with the docs

See the rate card Six ways teams use it

Application

Apply to the MindsHub Foundry

We review applications as they arrive. The form takes about 3–5 minutes, and every question is required.

Step 1 of 3 — About you

About you