Mithril
Mithril is an AI omnicloud compute platform, operated by Foundry Technologies, that aggregates GPU, CPU, and storage capacity across multiple cloud providers behind a single interface with transparent, market-based pricing. Developers reserve NVIDIA A100/H100/H200 GPUs on flexible reservations or burst onto interruptible spot capacity via price-limited bids, attach WEKA/NVMe persistent storage, run Kubernetes clusters, and drive it all through the v2 Compute REST API, the `ml` CLI, and a Python batch/inference SDK. Used for training, fine-tuning, inference, and batch workloads; SOC 2 Type II certified. Backed by Lightspeed, Multicoin Capital, and Redpoint.
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 Mithril the way a machine reads it — 20 machine-readable artifacts across 14 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 — Mithril scores 58.4/100 (developing), with a separate agent-readiness read of 69/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Mithril
Each block below is one kind of artifact we hold for Mithril. 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 14
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.
Mithril API Keys API
The API Keys API from Mithril — 2 operation(s) for api keys.
Mithril image versions API
The image versions API from Mithril — 2 operation(s) for image versions.
Mithril instance types API
The instance types API from Mithril — 2 operation(s) for instance types.
Mithril instances API
The instances API from Mithril — 5 operation(s) for instances.
Mithril kubernetes clusters API
The kubernetes clusters API from Mithril — 2 operation(s) for kubernetes clusters.
Mithril lifecycle scripts API
The lifecycle scripts API from Mithril — 3 operation(s) for lifecycle scripts.
Mithril pricing API
The pricing API from Mithril — 2 operation(s) for pricing.
Mithril profile API
The profile API from Mithril — 2 operation(s) for profile.
Mithril projects API
The projects API from Mithril — 1 operation(s) for projects.
Mithril quotas API
The quotas API from Mithril — 1 operation(s) for quotas.
Mithril reservations API
The reservations API from Mithril — 10 operation(s) for reservations.
Mithril spot API
The spot API from Mithril — 5 operation(s) for spot.
Mithril SSH Keys API
The SSH Keys API from Mithril — 2 operation(s) for ssh keys.
Mithril volumes API
The volumes API from Mithril — 2 operation(s) for volumes.
Scroll within the panel for all 14 ·
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.
mithril-mcp.yml
MCP SERVERSecurity Posture 4
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 Mithril — 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 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
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
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/mithril · machine-readable index on apis.io