Oxen
Oxen.ai is a blazing-fast data version control system and AI platform for teams building with their own data. Its open-source Rust core (liboxen) versions, branches, and shares terabyte-scale datasets, model weights, and experiments without Git's large-file limits. On top of the version control layer, Oxen.ai offers a unified, OpenAI-compatible inference API across 200+ text, image, video, and audio models, plus a fine-tuning API for training and deploying custom LLMs, vision-language, image, and video models. Developers work through a Python SDK (oxenai), a command-line tool (oxen), and an HTTP API for repository management, workspaces, data-frame diffing, generation queues, and model deployment.
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 Oxen the way a machine reads it — 23 machine-readable artifacts across 19 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 — Oxen scores 53.7/100 (developing), with a separate agent-readiness read of 65/100 (agent native). 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.
How we profile Oxen
Each block below is one kind of artifact we hold for Oxen. 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 19
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.
Oxen Ai API
The Ai API from Oxen — 17 operation(s) for ai.
Oxen Branches API
The Branches API from Oxen — 4 operation(s) for branches.
Oxen Commits API
The Commits API from Oxen — 17 operation(s) for commits.
Oxen Compare API
The Compare API from Oxen — 6 operation(s) for compare.
Oxen Data Frames API
The Data Frames API from Oxen — 5 operation(s) for data frames.
Oxen Directories API
The Directories API from Oxen — 1 operation(s) for directories.
Oxen evaluations API
The evaluations API from Oxen — 2 operation(s) for evaluations.
Oxen Export API
The Export API from Oxen — 1 operation(s) for export.
Oxen Files API
The Files API from Oxen — 1 operation(s) for files.
Oxen fine_tunes API
The fine_tunes API from Oxen — 13 operation(s) for fine_tunes.
Oxen Health API
The Health API from Oxen — 1 operation(s) for health.
Oxen Import API
The Import API from Oxen — 2 operation(s) for import.
Oxen Merge API
The Merge API from Oxen — 1 operation(s) for merge.
Oxen Metadata API
The Metadata API from Oxen — 1 operation(s) for metadata.
Oxen Namespaces API
Namespace management endpoints
Oxen Repositories API
Repository management endpoints.
Oxen Version Files API
The Version Files API from Oxen — 4 operation(s) for version files.
Oxen Workspace Files API
The Workspace Files API from Oxen — 5 operation(s) for workspace files.
Oxen Workspaces API
The Workspaces API from Oxen — 5 operation(s) for workspaces.
Scroll within the panel for all 19 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
oxen-mcp.yml
MCP SERVERSecurity 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 Oxen — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/oxen · machine-readable index on apis.io