Fluence
Fluence is a decentralized (DePIN) cloud-computing platform offering enterprise-grade CPU and GPU compute — virtual machines, GPU containers, and bare-metal instances — rented from a global marketplace of independent infrastructure providers at up to 85% below traditional clouds, with predictable pricing and zero egress fees. The Fluence API (api.fluence.dev) gives programmatic access to the marketplace: search available compute, deploy and manage VMs, attach storage and public IPs, configure VPCs, subnets, and security groups, register SSH keys, and handle billing. Compute is paid in USDC; the FLT token is used for staking and protocol governance on Fluence's Arbitrum Orbit L2 appchain. Backed by Multicoin Capital.
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 Fluence the way a machine reads it — 17 machine-readable artifacts across 12 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 — Fluence scores 45.4/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Fluence
Each block below is one kind of artifact we hold for Fluence. 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 12
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.
Fluence Billing API
Billing and payment related endpoints
Fluence Hardware API
Hardware API endpoints
Fluence Prices API
Endpoints to get prices for different resources and cost estimation
Fluence PublicIP API
The PublicIP API from Fluence — 3 operation(s) for publicip.
Fluence SecurityGroup API
Endpoints to create, view, update and delete security groups
Fluence Service API
The Service API from Fluence — 1 operation(s) for service.
Fluence SSH keys API
Endpoints to manage SSH keys
Fluence Storage API
Endpoints to create, view, update and delete storage resources
Fluence Subnets API
Endpoints to create, view, update and delete subnets
Fluence Users API
Users API endpoints
Fluence VMs API
Endpoints to create, view, update and delete VMs
Fluence VPCs API
Endpoints to create, view, update and delete VPCs
Scroll within the panel for all 12 ·
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.
fluence-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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Fluence — 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 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/fluence · machine-readable index on apis.io