Mixedbread
Mixedbread is a Berlin-based AI search and retrieval platform. It provides embeddings (mxbai-embed, Wholembed v3), rerankers (mxbai-rerank v1/v2/v3-listwise), multimodal stores, document parsing, structured extraction, and connector-based ingestion. Models are published as open weights on Hugging Face and consumed via a hosted REST API at api.mixedbread.com. The platform powers RAG and agent retrieval over text, PDFs, images, audio, and video across 100+ languages.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Mixedbread the way a machine reads it — 70 machine-readable artifacts across 12 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Mixedbread scores 58.1/100 (strong), with a separate agent-readiness read of 27/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Mixedbread's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/mixedbread-ai/"
title="Mixedbread on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/mixedbread-ai.svg"
alt="Mixedbread Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/mixedbread-ai/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/mixedbread-ai/"
title="Mixedbread on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/mixedbread-ai/card.svg"
alt="Mixedbread Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Mixedbread
Each block below is one kind of artifact we hold for Mixedbread. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 14
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Mixedbread admin API
The admin API from Mixedbread — 1 operation(s) for admin.
Mixedbread api_keys API
The api_keys API from Mixedbread — 4 operation(s) for api_keys.
Mixedbread billing API
The billing API from Mixedbread — 4 operation(s) for billing.
Mixedbread completions API
The completions API from Mixedbread — 1 operation(s) for completions.
Mixedbread data_sources API
The data_sources API from Mixedbread — 6 operation(s) for data_sources.
Mixedbread deprecated_vector_stores API
The deprecated_vector_stores API from Mixedbread — 10 operation(s) for deprecated_vector_stores.
Mixedbread Embeddings API
The Embeddings API from Mixedbread — 1 operation(s) for embeddings.
Mixedbread extractions API
The extractions API from Mixedbread — 6 operation(s) for extractions.
Mixedbread files API
The files API from Mixedbread — 7 operation(s) for files.
Mixedbread Mixedbread Embeddings API API
The Mixedbread Embeddings API API from Mixedbread — 1 operation(s) for mixedbread embeddings api.
Mixedbread parsing API
The parsing API from Mixedbread — 2 operation(s) for parsing.
Mixedbread Reranking API
The Reranking API from Mixedbread — 1 operation(s) for reranking.
Mixedbread schemas API
The schemas API from Mixedbread — 1 operation(s) for schemas.
Mixedbread stores API
The stores API from Mixedbread — 17 operation(s) for stores.
Scroll within the panel for all 14 ·
Postman Collections 14
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Mixedbread admin API
POSTMANMixedbread admin billing API
POSTMANMixedbread admin files API
POSTMANMixedbread admin parsing API
POSTMANMixedbread admin schemas API
POSTMANMixedbread admin stores API
POSTMANScroll within the panel for all 14 ·
Open Collections 27
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONMixedbread Admin API
OPEN COLLECTIONMixedbread admin API
OPEN COLLECTIONMixedbread admin api_keys API
OPEN COLLECTIONMixedbread admin billing API
OPEN COLLECTIONMixedbread admin completions API
OPEN COLLECTIONMixedbread admin data_sources API
OPEN COLLECTIONMixedbread admin deprecated_vector_stores API
OPEN COLLECTIONMixedbread admin Embeddings API
OPEN COLLECTIONMixedbread admin extractions API
OPEN COLLECTIONMixedbread admin files API
OPEN COLLECTIONMixedbread admin Mixedbread Embeddings API API
OPEN COLLECTIONMixedbread admin parsing API
OPEN COLLECTIONMixedbread admin Reranking API
OPEN COLLECTIONMixedbread admin schemas API
OPEN COLLECTIONMixedbread admin stores API
OPEN COLLECTIONMixedbread API Keys API
OPEN COLLECTIONMixedbread Billing API
OPEN COLLECTIONMixedbread Chat Completions API
OPEN COLLECTIONMixedbread Data Sources API
OPEN COLLECTIONMixedbread Embeddings API
OPEN COLLECTIONMixedbread Extractions API
OPEN COLLECTIONMixedbread Files API
OPEN COLLECTIONMixedbread Parsing API
OPEN COLLECTIONMixedbread Reranking API
OPEN COLLECTIONMixedbread Schemas API
OPEN COLLECTIONMixedbread Stores API
OPEN COLLECTIONScroll within the panel for all 27 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Mixedbread Ai Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Mixedbread Ai Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Mixedbread Ai Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Mixedbread API Rules
SPECTRALMixedbread API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Examples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Mixedbread Reranking Example
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Mixedbread — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 13
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 13 ·
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/mixedbread-ai · machine-readable index on apis.io
This is an independent, third-party profile of Mixedbread, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.