Nebius
Nebius is an AI-focused cloud platform spun out of Yandex, offering NVIDIA GPU virtual machines and clusters (GB300, GB200, B300, B200, H200, H100) connected over InfiniBand, managed Kubernetes and Slurm (Soperator), S3-compatible storage, managed PostgreSQL, container registry, MLflow, JupyterLab, vLLM, and the Token Factory inference platform. Nebius exposes a gRPC control plane API, a Terraform provider, a nebius CLI, and Go and TypeScript SDKs.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Nebius the way a machine reads it — 23 machine-readable artifacts across 6 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 — Nebius scores 30.3/100 (thin), with a separate agent-readiness read of 7/100 (human only). 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 Nebius
Each block below is one kind of artifact we hold for Nebius. 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 6
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.
Nebius Compute API
The Nebius Compute API provisions and manages virtual machines and GPU clusters with NVIDIA GPUs and InfiniBand interconnect for ML and AI workloads. Exposed over gRPC and acces...
Nebius Managed Kubernetes API
The Managed Kubernetes API provisions Kubernetes clusters with GPU and InfiniBand support for distributed training and inference workloads.
Nebius Storage API
The Nebius Storage API exposes AWS S3-compatible object storage for ML/AI datasets and model artifacts.
Nebius IAM API
The Nebius Identity and Access Management API controls users, service accounts, projects, and resource-level access policies.
Nebius Managed Applications API
The Managed Applications API deploys and manages JupyterLab, vLLM, Open WebUI, MLflow, and other ready-made apps on Nebius infrastructure.
Nebius Token Factory
Nebius Token Factory is the AI model inference platform offering OpenAI-compatible endpoints for serving open-source LLMs on Nebius GPU infrastructure.
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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Nebius Plans Pricing
PLANSRate 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.
Nebius 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.
Nebius Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
GPU Compute
Virtual machines and clusters with NVIDIA GB300, GB200, B300, B200, H200, and H100 GPUs.
InfiniBand Networking
High-bandwidth InfiniBand interconnect for large-scale distributed training.
Managed Kubernetes
Kubernetes clusters with GPU and InfiniBand support.
Slurm via Soperator
Slurm workload manager running on Kubernetes via the open-source Soperator project.
S3-Compatible Storage
Object storage optimized for ML datasets and model artifacts.
Managed Applications
One-click JupyterLab, vLLM, Open WebUI, and MLflow deployments.
Token Factory
OpenAI-compatible inference endpoints for open-source LLMs.
Scroll within the panel for all 7 ·
Security 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.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Terraform
Official Terraform provider for Nebius infrastructure.
Kubernetes
Standard Kubernetes API across managed clusters.
Slurm
Slurm workload manager via the open-source Soperator project.
MLflow
Managed MLflow for experiment tracking.
PostgreSQL
Managed PostgreSQL database clusters.
Resources
Every other property we hold for Nebius — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 2
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
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/nebius · machine-readable index on apis.io