Osmosis
Osmosis (Gulp AI Inc.) is a forward-deployed reinforcement-learning platform for post-training large language models. Teams implement an AgentWorkflow and a Grader in Python, then use the Osmosis CLI and web platform to submit evaluation and training runs (GRPO/DAPO, multi-turn tool training) that produce task-specific LoRA models which beat foundation models at a fraction of the cost. Osmosis also ships an Agent Improvement REST API for storing agent interaction knowledge and enhancing agent tasks from past interactions, an open-source Python SDK/CLI (osmosis-ai), a TypeScript logging SDK, an open-source MCP server (Osmosis-Apply), webhooks, and hosted documentation. Backed by CRV, Felicis, and Paradigm.
Osmosis publishes 3 API contracts indexed on the APIs.io network: Agent API, Knowledge API, and Agent Improvement API. Tagged areas include Company, Artificial Intelligence, Reinforcement Learning, LLM, and Post-Training.
The Osmosis catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.
Osmosis’ developer surface includes documentation, API reference, getting-started guide, engineering blog, support, signup flow, CLI, and 24 more developer resources.
What this lets a business do 1
Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Hugging Face Hub Organisations | builds-on | 26.8 (thin) | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 2
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 3
Individual APIs this provider publishes, each with its own machine-readable definition.
Osmosis Agent API
Operations for enhancing agent interactions and decisions
Osmosis Knowledge API
Operations for managing the knowledge base
Osmosis Agent Improvement API
The Osmosis Agent Improvement API API from Osmosis — 1 operation(s) for osmosis agent improvement api.
Open Collections 3
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Osmosis Improvement agent API
OPEN COLLECTIONOsmosis Improvement agent knowledge API
OPEN COLLECTIONOsmosis Improvement agent Osmosis Agent Improvement API API
OPEN COLLECTIONMCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Osmosis MCP Server
An open-source Model Context Protocol server that uses the Osmosis-Apply-1.7B model (served locally via Ollama) to merge code edits into files. Integrates into AI IDE / MCP-clie...
MCP SERVERAgent Skills 2
Packaged agent skills for driving this provider's APIs from an AI assistant.
Enhance an agent task with Osmosis memory
AGENT SKILLStore and manage agent interaction knowledge
AGENT SKILLEvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Osmosis Webhooks
ASYNCAPISpectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
Osmosis API Rules
SPECTRALOpenAPI Overlays 1
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Source (apis.yml)
Osmosis API — frequently asked questions
Does Osmosis have an API?
Yes. APIs.io lists 3 APIs from Osmosis, including Osmosis Agent API, Osmosis Knowledge API and Osmosis Agent Improvement API.
Is there an OpenAPI specification for the Osmosis API?
Yes. APIs.io indexes 3 OpenAPI specifications for Osmosis, each linked for download from this page.
How do I authenticate with the Osmosis API?
Osmosis uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Osmosis Authentication.
Does Osmosis have an MCP server?
Yes. APIs.io lists 1 MCP server for Osmosis: An open-source Model Context Protocol server that uses the Osmosis-Apply-1.7B model (served locally via Ollama) to merge code edits into files. Integrates into AI IDE / MCP-client workflows. Requires
Is the Osmosis API ready for AI agents?
Osmosis has a Kin Score of 46.2 out of 100 (developing) and an Agent Readiness score of 35.6 (agent-ready), scored by API Evangelist on 2026-11-06.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.