Baseten
Baseten is a production inference platform for deploying and serving custom and pre-trained ML models. Offers a Model APIs catalog with OpenAI-compatible endpoints (DeepSeek, Qwen, GLM, Nemotron), dedicated deployments via Truss, autoscaling GPU compute, async/queue inference, training, chains (multi-model workflows), and management APIs.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Baseten the way a machine reads it — 57 machine-readable artifacts across 3 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 — Baseten scores 49.8/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Baseten
Each block below is one kind of artifact we hold for Baseten. 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 3
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.
Baseten Management & Async API
Deployment management, async/queued inference, chain calls (multi-model workflows), training, dedicated-deployment lifecycle, async result polling, and webhook delivery.
Baseten Chat Completions API
The Chat Completions API from Baseten — 1 operation(s) for chat completions.
Baseten Messages API
The Messages API from Baseten — 1 operation(s) for messages.
Open Collections 2
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).
Baseten LLM Inference API
OPEN COLLECTIONBaseten Anthropic-Compatible Inference API
OPEN COLLECTIONPricing 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 six things the Kin Score reads for commercial clarity.
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.
Baseten 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.
Baseten Finops
FINOPSSpectral Rules 1
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.
Baseten API Rules
SPECTRALJSON Schema 43
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.
ChatCompletionContentPartImageParam
JSON SCHEMAChatCompletionContentPartInputAudioParam
JSON SCHEMAChatCompletionContentPartTextParam
JSON SCHEMAChatCompletionLogProb
JSON SCHEMAChatCompletionLogProbs
JSON SCHEMAChatCompletionLogProbsContent
JSON SCHEMAChatCompletionMessage
JSON SCHEMAChatCompletionMessageToolCallParam
JSON SCHEMAChatCompletionNamedFunction
JSON SCHEMAChatCompletionNamedToolChoiceParam
JSON SCHEMAChatCompletionRequest
JSON SCHEMAChatCompletionStreamResponse
JSON SCHEMAChatCompletionResponseStreamChoice
JSON SCHEMAChatCompletionToolsParam
JSON SCHEMACompletionTokensDetails
JSON SCHEMADeltaMessage
JSON SCHEMADisaggregatedParams
JSON SCHEMAFile
JSON SCHEMAFileFile
JSON SCHEMAFunction
JSON SCHEMAFunctionCall
JSON SCHEMAFunctionDefinition
JSON SCHEMAImageURL
JSON SCHEMAInputAudio
JSON SCHEMAInputMessage
JSON SCHEMAJsonSchema
JSON SCHEMAMessagesRequest
JSON SCHEMAMessagesResponse
JSON SCHEMAPromptTokensDetails
JSON SCHEMAResponseFormatGrammar
JSON SCHEMAResponseFormatJson
JSON SCHEMAResponseFormatJsonObject
JSON SCHEMAResponseFormatStructuralTag
JSON SCHEMAResponseFormatText
JSON SCHEMAStreamOptions
JSON SCHEMATextBlock
JSON SCHEMAToolCall
JSON SCHEMAToolChoice
JSON SCHEMAToolDefinition
JSON SCHEMAToolResultBlock
JSON SCHEMAToolUseBlock
JSON SCHEMAUsage
JSON SCHEMAUsageInfo
JSON SCHEMAScroll within the panel for all 43 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Baseten Structure
JSON STRUCTURESecurity Posture 3
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 Baseten — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/baseten · machine-readable index on apis.io