Find compute resources on the marketplace

The Fluence compute marketplace is a decentralized platform where you can find and rent compute resources from various providers worldwide. Each provider has offers with different geographies, configurations, and prices. The marketplace API helps you discover resources that meet your specific requirements.

In this document, you'll learn:

The core concepts of the Fluence Marketplace
How to search for available compute offers
How to filter resources based on your requirements
How to estimate the cost of your deployment

The core concepts

Before exploring the Fluence Marketplace, let’s define five key terms:

Term	Description
Offer	A listing published by a provider. An offer groups one or more physical servers that run in the same datacenter and share a single pricing schedule.
Compute Peer	A physical server inside an offer with it's own set of hardware resources. Peers are the machines that will actually host your workloads.
Resource	A consumable item on a peer: vCPU, RAM, storage, public IP.
Hardware specification	Metadata that describes a resource (CPU architecture, memory generation, storage medium, etc.).
Epoch	A fixed 24-hour billing period. All marketplace prices are quoted in USDC per epoch.

What distinguishes one compute peer from another?

Hardware resources – Each peer has it's own set of hardware resources and capacity.
Hardware specifications – Detailed metadata lets you target exactly the hardware you need (e.g. manufacturer: "AMD", storage.type: "NVMe").
Price per epoch – Cost depends on the hardware specification; more powerful peers cost more per 24-hour epoch.
Location – All peers in a single offer are located in the same datacenter.
Availability – Peers differ in how many VMs (of a given basic configuration) they can still host and how much additional resource (such as extra storage) remains unallocated.

Before deploying your workloads, you can search for offers that satisfy your CPU, RAM, storage, and location constraints and estimate their cost.

tip

You can skip the exploration step and simply declare your deployment requirements and the Marketplace algorithms will automatically match you with the best available offer. For this, proceed to Deploy virtual machines section.

Search for available offers

The marketplace offers a powerful API endpoint that allows you to search for available compute resources with specific filters. Without filters, you will receive all compute providers' offers available on the marketplace. By applying different filters, you can find offers that match your specific requirements. To get the Marketplace offers, send a POST request to the following endpoint with a JSON body containing your filters:

https://api.fluence.dev/marketplace/offers

Request parameters

You can use the request body to filter offers based on your specific requirements. All filters are optional and in case you do not want to apply any filters, send an empty object {} in the body.

Example of a request body with all filters applied:

{
  "basicConfiguration": "cpu-8-ram-16gb-storage-25gb", // optional
  "additionalResources": {
    // optional
    "storage": [
      {
        "supply": 4,
        "units": "GiB",
        "type": "NVMe"
      }
    ]
  },
  "hardware": {
    // optional
    "cpu": [
      // optional
      {
        "manufacturer": "AMD",
        "architecture": "Zen"
      }
    ],
    "memory": [
      // optional
      {
        "type": "DDR",
        "generation": "5"
      }
    ],
    "storage": [
      // optional
      {
        "type": "NVMe"
      }
    ]
  },
  "datacenter": {
    // optional
    "countries": ["FR"]
  },
  "maxTotalPricePerEpochUsd": "12.57426" // optional
}

Let's break down the request body parameters and their usage

Basic configuration

The basicConfiguration parameter allows you to specify a standardized resource profile using a predefined string format. This format follows the pattern cpu-{cores}-ram-{memory}gb-storage-{size}gb, where:

{cores} represents the number of vCPU cores
{memory} represents the RAM amount in GB
{size} represents the storage capacity in GB

To get the list with names of all available basic configurations on the marketplace, you can use specific endpoint. Read more about it in the Basic configurations available on the Marketplace section.

Example:

{
  "basicConfiguration": "cpu-8-ram-16gb-storage-25gb"
}

Hardware specifications constraints

If you need specific CPU architecture or storage type, you can filter based on hardware requirements. To get the list of all available hardware specifications on the marketplace, you can use specific endpoint, read more about it in the Hardware specifications available on the marketplace section.

hardware
- Specific hardware requirements for the compute resources.
- Fields:
  - cpu
    - manufacturer : CPU manufacturer (e.g., "AMD", "Intel (R)")
    - architecture : CPU architecture (e.g., "Zen", "ICE LAKE")
  - memory
    - type : Memory type (e.g., "DDR")
    - generation : Memory generation (e.g., "4", "5")
  - storage
    - type : Storage type - one of: "HDD", "SSD", or "NVMe"

Example:

{
  "hardware": {
    "cpu": [
      {
        "manufacturer": "AMD"
      }
    ],
    "memory": [
      {
        "type": "DDR",
        "generation": "4"
      }
    ],
    "storage": [
      {
        "type": "NVMe"
      }
    ]
  }
}

Datacenter constraints

API allows you to filter datacenters by country. To get the list of all available countries on the marketplace, you can use specific endpoint, read more about it in the Datacenter countries available on the marketplace section.

datacenter
- Geographic constraints for the compute resources.
- Fields:
  - countries: ISO country codes where you want your resources to be located (e.g., ["FR", "DE"] for France and Germany)

Example:

{
  "datacenter": {
    "countries": ["FR", "DE"]
  }
}

Additional resources

Additional resources are hardware resources that you can request beyond the basic configuration. You can specify them to find offers with sufficient extra capacity. Currently, only additional storage is supported.

warning

Currently, additionalResources can be used only along with hardware.storage filter.

additionalResources
- Additional resources you need beyond the basic configuration.
- Fields:
  - storage
    - type : Type of storage - one of: "HDD", "SSD", or "NVMe"
    - units: Units of measurement - currently only "GiB" (Gibibytes) is supported
    - supply : Required storage volume size in the specified units

Example:

{
  "additionalResources": {
    "storage": [
      {
        "supply": 20,
        "units": "GiB",
        "type": "NVMe"
      }
    ]
  }
}

Maximum price per epoch constraint

You can apply filter for the max price per epoch (24 hours) in USDC that you're willing to pay for the resources you've specified in the request body: both basic configuration and additional resources.

maxTotalPricePerEpochUsd - Expressed as a string to handle decimal precision (e.g. "12.5")

Example:

{
  "maxTotalPricePerEpochUsd": "12.5"
}

Response structure

When you send a request to /marketplace/offers, you'll receive a response containing an array of offers that match your criteria. Each offer represents a unique configuration available from a specific provider in a particular data center. The array consists of objects, with each object representing an offer from a provider for a specific basic configuration. If no offers match your criteria, the response will contain an empty list.

note

To view all available basic configurations, use the endpoint described in the Basic Configurations available on the marketplace section.

General structure of the response for a single object:

[
  {
    "configuration": {
      "slug": string,
      "price": string
    },
    "resources": [
      {
        "type": string,
        "metadata": {...},
        "price": string
      }
    ],
    "datacenter": {
      "countryCode": string,
      "cityCode": string,
      "cityIndex": number,
      "tier": number,
      "certifications": [string]
    },
    "servers": [
      {
        "availableBasicInstances": number,
        "additionalResources": [
            {
            "supply": number,
            "perVmLimit": number | null,
            "type": string,
            "metadata": {...},
            "price": string
          }
        ]
      }
    ],
    "maxAdditionalSupply": [
      {
        "supply": number,
        "perVmLimit": number | null,
      }
    ]
  },
  // More offers with different configurations and prices
]

Let's break down the key components of the response:

Response fields of a single offering object

Configuration

The configuration object represents the basic configuration of the offer. It includes:

slug: The basic configuration identifier. Read more about basic configurations in the Basic Configurations available on the marketplace section.
price: The base price for this configuration (in USDC per epoch)

Example:

{
  "configuration": {
    "slug": "cpu-2-ram-4gb-storage-25gb",
    "price": "0.30698"
  }
}

Resources

The resources array contains details about the base resources included in the offer with the basic configuration. This shows the exact resources that will be allocated to the VM in case of matching with the offer.

Each resource element in the array includes:

type: Resource type, can be one of the following: VCPU, RAM, STORAGE, PUBLIC_IP
metadata: Its type-specific metadata. You can find more details about the metadata for each hardware resource type in the Hardware specifications available on the marketplace section.
price: The price for this resource per epoch

Example:

{
  "resources": [
    {
      "type": "VCPU",
      "metadata": {
        "manufacturer": "AMD",
        "brand": "EPYC",
        "architecture": "Zen",
        "generation": "2"
      },
      "price": "0.005"
    },
    {
      "type": "RAM",
      "metadata": {
        "type": "DDR",
        "generation": "4"
      },
      "price": "0.002"
    }
    // Other resources (STORAGE, PUBLIC_IP)
  ]
}

This example object represents hardware configuration for the example basic configuration from the previous example.

Datacenter

The datacenter object provides information about the physical location of the resources and the certifications the datacenter holds.

Each datacenter object includes fields:

countryCode: ISO country code
cityCode: LOCODE code for the city
cityIndex: Index if multiple datacenters exist in the same city
tier: Datacenter tier level (1-4, with 4 being highest reliability)
certifications: Array of compliance certifications this datacenter holds

Example:

{
  "datacenter": {
    "countryCode": "FR",
    "cityCode": "PAR",
    "cityIndex": 1,
    "tier": 2,
    "certifications": ["ISO 200027", "SOC2", "ISO 50001:2011", "PCI DSS 3.2"]
  }
}

Servers

The servers array provides information about the actual physical machines available to host your workloads that are available in an offer. Each element in this array represents a distinct physical server in the provider's infrastructure.

Each server object includes:

availableBasicInstances: Number of instances with the basic configuration of the object that can be created on this set of resources
additionalResources: Extra resources this specific server can provide beyond the basic configuration.
- type: Resource type (currently only STORAGE is supported)
- metadata: Its type-specific metadata. You can find more details about the metadata for each hardware resource type in the Hardware specifications available on the marketplace section.
- price: Cost per unit of this resource per epoch (24 hours)
- supply: Total amount of a resource available on the server.
- units: Units of measurement (currently only GiB is supported)
- perVmLimit: Limit for the amount of this resource that can be allocated to a single VM, set by the Protocol.

Example:

{
  "servers": [
    {
      "availableBasicInstances": 5,
      "additionalResources": [
        {
          "type": "STORAGE",
          "metadata": {
            "type": "NVMe"
          },
          "price": "0.00001",
          "supply": 100,
          "units": "GiB",
          "perVmLimit": 200
        }
      ]
    }
    // Other servers
  ]
}

Max additional supply per VM

The maxAdditionalSupply array provides information about the maximum amount of additional resources you can purchase in addition to a VM with the basic configuration. Each element in this array represents a distinct resource type and has the following fields:

supply: Total available quantity of this resource type.
perVmLimit: Maximum amount of this resource that can be allocated to a single VM, set by the Protocol.
type: Resource type (currently only STORAGE is supported)
metadata: Resource-specific details
price: Cost per unit of this resource

{
  "maxAdditionalSupply": [
    {
      "type": "STORAGE",
      "metadata": {
        "type": "NVMe"
      },
      "price": "0.00001",
      "supply": 100,
      "units": "GiB",
      "perVmLimit": 200
    }
  ]
}

Discovering available options for filter parameters

The Fluence Marketplace API provides several endpoints to help you discover valid values for filter parameters. These endpoints allow you to see what options are available for basic configurations, countries, and hardware specifications.

Basic Configurations available on the marketplace

To retrieve all available basic configurations, send a GET request to the following endpoint:

https://api.fluence.dev/marketplace/basic_configurations

The response will return all available basic configurations in the marketplace without specification of concrete hardware. The basicConfiguration parameter allows you to specify a standardized resource profile using a predefined string format. This format follows the pattern cpu-{cores}-ram-{memory}gb-storage-{size}gb, where:

{cores} represents the number of vCPU cores
{memory} represents the RAM amount in GB
{size} represents the storage capacity in GB

Response

The response returns an array of strings with names of all available basic configurations.

For example:

[
  "cpu-2-ram-4gb-storage-25gb",
  "cpu-4-ram-8gb-storage-25gb",
  "cpu-8-ram-16gb-storage-25gb"
  // Other basic configurations
]

Datacenter countries available on the marketplace

To retrieve all available countries that have datacenters with available offers in the marketplace, send a GET request to the following endpoint:

https://api.fluence.dev/marketplace/countries

The response returns all available countries ISO codes that have datacenters with available offers in the marketplace.

For example:

["DE", "FR", "GB", "LT", "PL", "US"]

Use these ISO country codes in the datacenter.countries array of your search parameters to filter results and show only offers from specific geographic locations.

Hardware specifications available on the marketplace

To retrieve all available hardware specifications on the marketplace, send a GET request to the following endpoint:

https://api.fluence.dev/marketplace/hardware

The response returns all hardware specifications available across all providers in the marketplace. The response is an object with arrays of hardware specifications for each resource type.

For example:

{
  "cpu": [
    {
      "manufacturer": "AMD",
      "architecture": "Zen"
    },
    {
      "manufacturer": "Intel (R)",
      "architecture": "ICE LAKE"
    }
    // More CPU options
  ],
  "memory": [
    {
      "type": "DDR",
      "generation": "5"
    },
    {
      "type": "DDR",
      "generation": "4"
    }
  ],
  "storage": [
    {
      "type": "SSD"
    },
    {
      "type": "NVMe"
    }
  ]
}

Use these values in the hardware section of your search parameters:

CPU specifications: Use architecture and manufacturer values to specify CPU requirements
Memory specifications: Use type and generation values to filter by RAM type
Storage types: Use the type value to filter by storage technology (HDD, SSD, or NVMe)

For example, if you need high-performance storage, you might filter for offers with NVMe storage based on the values returned by this endpoint.

Estimate price for a deployment

Before committing to a deployment, you'll often want to know how much it will cost. The /vms/v3/estimate endpoint allows you to calculate the expected price for your deployment based on your configuration requirements and the number of instances you plan to deploy.

POST /vms/v3/estimate

Request parameters

The request body follows a similar structure to the /marketplace/offers endpoint, with the addition of an instances field to specify how many VMs you want to deploy.

Example of a request body with all filters specified:

{
  "constraints": {
    "basicConfiguration": "cpu-2-ram-4gb-storage-25gb",
    "additionalResources": {
      "storage": [
        {
          "type": "NVMe",
          "supply": 20,
          "units": "GiB"
        }
      ]
    },
    "hardware": {
      "cpu": [
        {
          "manufacturer": "AMD"
        }
      ],
      "storage": [
        {
          "type": "NVMe"
        }
      ]
    },
    "datacenter": {
      "countries": ["FR", "US"]
    },
    "maxTotalPricePerEpochUsd": "1.2"
  },
  "instances": 3
}

constraints: Contains all your requirements for the deployment, identical to the filters used in the /marketplace/offers endpoint.
- basicConfiguration: The predefined VM configuration you want (e.g., "cpu-2-ram-4gb-storage-25gb")
- additionalResources: Extra resources you need beyond the basic configuration
- hardware: Specific hardware requirements (CPU manufacturer, storage type, etc.)
- datacenter: Geographic constraints for your deployment
- maxTotalPricePerEpochUsd: Maximum price per epoch (24 hours) you're willing to pay
instances: The number of VMs you want to deploy with this configuration

Response structure

The endpoint returns detailed pricing estimation for your proposed deployment. Example of a successful response:

{
  "depositAmountUsdc": "7.01532", // totalPricePerEpoch * depositEpochs
  "depositEpochs": 2,
  "totalPricePerEpoch": "3.50766", // total price for all instances per epoch
  "maxPricePerEpoch": "0.35793", // max price for a single instance per epoch
  "instances": 10 // number of instances
}

In case no offers are found to satisfy the constraints, the endpoint will return an 422 error response with a message:

{
  "error": "Not enough offers found"
}

Response fields

depositAmountUsdc: The total deposit amount required in USDC. This is calculated as totalPricePerEpoch × depositEpochs.
depositEpochs: The number of epochs (days) for which the deposit is calculated. This represents the initial commitment period.
instances: The number of VM instances you requested in your estimate.
maxPricePerEpoch: The maximum price per epoch (24 hours) for a single instance of your configuration.
totalPricePerEpoch: The total price per epoch for all instances combined.

The next steps

The Fluence compute marketplace API provides a powerful and flexible way to find and compare compute resources from various providers across the globe. By using the filtering capabilities and understanding the response structure, you can quickly find resources that match your specific requirements including price, location, and hardware specifications.

In the next document, we'll cover how to use your selected offer to create and manage deployments on the Fluence platform.

The core concepts​

What distinguishes one compute peer from another?​

Search for available offers​

Request parameters​

Basic configuration​

Hardware specifications constraints​

Datacenter constraints​

Additional resources​

Maximum price per epoch constraint​

Response structure​

Response fields of a single offering object​

Configuration​

Resources​

Datacenter​

Servers​

Max additional supply per VM​

Discovering available options for filter parameters​

Basic Configurations available on the marketplace​

Response​

Datacenter countries available on the marketplace​

Hardware specifications available on the marketplace​

Estimate price for a deployment​

Request parameters​

Response structure​

Response fields​

The next steps​

The core concepts

What distinguishes one compute peer from another?

Search for available offers

Request parameters

Basic configuration

Hardware specifications constraints

Datacenter constraints

Additional resources

Maximum price per epoch constraint

Response structure

Response fields of a single offering object

Configuration

Resources

Datacenter

Servers

Max additional supply per VM

Discovering available options for filter parameters

Basic Configurations available on the marketplace

Response

Datacenter countries available on the marketplace

Hardware specifications available on the marketplace

Estimate price for a deployment

Request parameters

Response structure

Response fields

The next steps