The Mistral AI Agents API handles agent completion operations at https://api.mistral.ai/v1. Its catalog entry carries twenty-seven properties — the widest property spread of any API in this week’s sweep — including OpenAPI, Documentation, Authentication, APIEndpoint, AsyncAPI, GraphQL, Pricing, and seven separate GettingStarted entries.
Seven getting-started guides on one API is not redundancy. It is a signal about who is expected to show up.
Onboarding as the product surface
Most APIs in the catalog carry one getting-started link, if any. The pattern here — seven, interleaved with Documentation and APIEndpoint properties — describes a provider that has segmented its onboarding by path rather than writing one canonical tutorial.
That makes sense for agent APIs specifically. The person wiring up a chat completion, the person building a tool-calling loop, and the person deploying a multi-step agent are three different developers with three different first questions. A single quickstart serves one of them and loses the other two.
The explicit Pricing property is the other notable inclusion. Agent workloads are the hardest LLM spend to predict, because a single request can fan out into an unbounded number of model calls depending on how the loop terminates. Surfacing pricing as a first-class described property rather than a marketing page is the provider acknowledging that cost is an integration concern, not a sales concern.
Authentication as a named property
The entry carries Authentication as its own property type. That sounds mundane until you look at how rarely it appears across the catalog — most providers fold auth into general documentation and let you find it.
For agent APIs this matters more than usual. An autonomous agent that cannot deterministically resolve its own credential model is an agent that fails at 3am. Naming the auth surface explicitly is what makes the difference between an API an agent can adopt and one a human has to wire up first.
The AsyncAPI presence
Agents are long-running. A completion that triggers tool calls, waits, and resumes is a stream of events, not a request-response pair. The AsyncAPI alongside the OpenAPI is Mistral describing both halves — and it puts them in the minority of the 661 providers on the network that describe an event surface at all.
Takeaway
Twenty-seven properties, seven onboarding paths, explicit pricing, and named authentication. The Mistral Agents API is what it looks like when a provider treats adoption as the thing to specify, not just the endpoint. For an agent API, where the consumer is increasingly another machine, that is the whole game.
See it at docs.mistral.ai/api, and the provider entry at apis.io/providers/mistral/.