Skip to main content

Introduction to the Fluence API

The Fluence API provides programmatic access to the decentralized Fluence compute marketplace. With the API you can find, rent, and manage compute resources on both CPU Cloud and GPU Cloud without using the web interface.

Authentication​

Fluence API endpoints require credentials: an API key in the X-API-KEY header, or an access token in the Authorization: Bearer header. You can create and manage your keys in the Fluence Console settings or with POST /v1/api_keys. A request without valid credentials is rejected with 401, or 400 when the key is missing or malformed on some endpoints; a key without the permission an endpoint needs gets 403.

AI agents and scripts can skip the console entirely: pay with x402 to fund an account with USDC on Base, sign in with the same wallet to get an access token, and create an API key from it. The x402 and sign-in endpoints themselves need no credentials.

Request and response format​

The Fluence API accepts and returns data in JSON format. When making POST requests, set the Content-Type header to application/json.

Example request:

curl -i -X GET https://api.fluence.dev/gpu/plans \
  -H "X-API-KEY: <YOUR_API_KEY>"

Response HTTP statuses​

  • Success: Status codes in the 200 range indicate the request was fulfilled successfully.
  • Client errors: Status codes in the 400 range indicate an issue with the request — missing or invalid API key, malformed request body, resource not found, etc.
  • Server errors: Status codes in the 500 range indicate a server-side problem.

All error responses return a JSON body with a description of the problem. The exact error format differs between CPU Cloud and GPU Cloud — see the cloud-specific overview pages for details.

Contents​

The Fluence API covers two cloud platforms — CPU Cloud and GPU Cloud. Pick the one that matches your workload:

  • CPU Cloud — choose locations and plans, deploy and manage virtual machines, disks and public IP addresses
  • GPU Cloud — browse available GPU plans, deploy and manage containers, VMs, and bare metal instances

In addition, the API provides shared account-level management that applies across both platforms:

  • SSH keys — register and manage SSH keys for use during deployment
  • Pay with x402 — fund the balance with USDC over HTTP and sign in with the paying wallet, for AI agents and scripts