FPX API

Request headers

Query parameters

All parameters are optional. Omit any you don't need.

Response

{
  "success": true,
  "count": 3,
  "total": 184,
  "offset": 0,
  "limit": 50,
  "deals": [ /* deal objects */ ]
}

Each deal object contains only fields relevant to its listing_type. Empty fields are omitted.

Example: search for H200 GPU supply

curl -H "x-api-key: YOUR_API_KEY" \
  "https://api.fpx.world/v1/deals?listing_type=hardware_gpu&gpu_model=H200&min_quantity=8&limit=10"

Example: colocation in Dallas, 1–5 MW

curl -H "x-api-key: YOUR_API_KEY" \
  "https://api.fpx.world/v1/deals?listing_type=colocation&location=Dallas&min_power_mw=1&max_power_mw=5"

Request headers

Common body fields (all listing types)

Response

{
  "success": true,
  "id": "70193bab-2b2f-423c-9c59-ac61990496c2",
  "status": "request_received",
  "created_at": "2026-04-22T07:31:00.123Z",
  "message": "Deal submitted for review. You will be notified when it is approved."
}

Keep the id — you can use it to reference the submission later.

Required fields

• listing_type = "hardware_gpu"
• gpu_model — string — e.g. "H100", "H200", "B200"
• available_units — integer
• price — number

Pricing

One price per unit in price + currency. Set price_unit to match:

Other commonly-used fields

• unit_type — enum — physical unit being sold. One of server, baseboard, gpu/card, rack
• moq — integer — minimum order quantity
• batch_size — integer — units grouped per shipment/batch
• gpus_per_unit — integer — number of GPUs per server/baseboard/rack
• gpu_hbm_gb_each — integer — GB of HBM memory per GPU (e.g. 80, 141, 192)
• gpu_hbm_type — string — HBM generation (e.g. "HBM3", "HBM3e")
• gpu_specs — string — free-form GPU specification detail
• cpu_specs — string — CPU model and configuration
• memory_specs — string — system memory spec (e.g. "2TB DDR5")
• storage_specs — string — storage configuration
• networking_specs — string — NIC / fabric details
• power_specs — string — PSU / power draw information
• chassis — string — chassis model or form factor
• condition — enum — one of new, refurbished, used, pulled, as_is, unknown
• warranty_months — integer — length of warranty coverage
• warranty_type — enum — oem, seller, third_party, none, unknown
• lead_time_text — string — delivery ETA (e.g. "4-6 weeks")
• server_age_years — integer — age of the unit in years (for used/refurbished)

Example

curl -X POST https://api.fpx.world/v1/deals \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "listing_type": "hardware_gpu",
    "title": "H200 SXM5 — Dallas — 256 units",
    "company_id": "<YOUR_COMPANY_ID>",
    "broker_id": "<YOUR_BROKER_ID>",
    "deal_type": "Offer",
    "unit_type": "server",
    "gpu_model": "H200",
    "gpus_per_unit": 8,
    "gpu_hbm_gb_each": 141,
    "gpu_hbm_type": "HBM3e",
    "available_units": 32,
    "moq": 8,
    "price": 285000,
    "currency": "USD",
    "price_unit": "per_server",
    "location": "Dallas, TX",
    "condition": "new",
    "warranty_months": 12,
    "warranty_type": "oem",
    "lead_time_text": "4-6 weeks",
    "notes": "Sealed, OEM warranty, FOB Dallas."
  }'

Required fields

• listing_type = "colocation"
• location — string — city or metro
• total_power_mw — number

Pricing

Colocation uses two pricing components instead of a single price:

Other commonly-used fields

• site_name — string — name of the data center / site
• site_status — enum — ready, under_construction, planned
• available_power_mw — number — MW currently available for contract
• power_density_kw_per_rack — number — supported rack density in kW
• cooling_type — enum — air, liquid, both, tbc
• liquid_cooling_supported — string — free-form description (e.g. "DLC + RDHx")
• power_redundancy — enum — N, N+1, 2N
• pue — number — power usage effectiveness (1.0 – 2.0)
• racks_available — integer — count of racks available
• contract_term — string — typical contract length offered
• minimum_commit — string — minimum contract commitment description
• rfs_date — date — ready-for-service date
• live_power_date — date — date power becomes live
• meet_me_room — boolean — meet-me room / carrier hotel access
• renewable_power_option — boolean — renewable energy option available
• carriers_available — string — list of connectivity carriers
• compliance_certifications — string — certifications (SOC 2, ISO 27001, etc.)

Example

curl -X POST https://api.fpx.world/v1/deals \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "listing_type": "colocation",
    "title": "Frankfurt FRA-03 — 5MW",
    "company_id": "<YOUR_COMPANY_ID>",
    "broker_id": "<YOUR_BROKER_ID>",
    "site_name": "FRA-03",
    "site_status": "ready",
    "location": "Frankfurt, Germany",
    "total_power_mw": 5,
    "available_power_mw": 5,
    "power_density_kw_per_rack": 80,
    "cooling_type": "liquid",
    "liquid_cooling_supported": "DLC + rear-door heat exchanger",
    "power_redundancy": "2N",
    "pue": 1.25,
    "power_capacity_charge": 145,
    "power_capacity_charge_currency": "EUR",
    "power_consumption_charge": 0.12,
    "power_consumption_charge_currency": "EUR",
    "is_dynamic_pricing": false,
    "rfs_date": "2026-07-01",
    "meet_me_room": true
  }'

Required fields

• listing_type = "cloud_gpu"
• price — number
• total_qty_available — integer — number of GPUs available
• One of gpu_model or gpu_type — string — e.g. "H100", "B200"

Pricing

Cloud GPUs are always billed per GPU-hour. Set:

• price — number — rate per GPU-hour
• currency — string — e.g. "USD"
• price_unit — string — leave as "per_gpu_hour" (default and enforced server-side)

Rental model

Other commonly-used fields

• gpus_per_node — integer — GPUs per node/instance
• cpu_spec — string — CPU configuration per node
• ram_gb — integer — RAM per node in GB
• local_ssd_nvme — string — local storage description
• storage_options — string — attached storage tiers offered
• network_type — enum — ethernet, infiniband, roce, unknown
• network_bandwidth — string — e.g. "3.2Tbps non-blocking"
• availability_start_date — date — date capacity becomes available
• sla_support_level — string — support SLA tier
• support_hours — string — e.g. "24/7", "business hours"
• managed_services — string — managed services offered
• software_stack — string — preinstalled OS / drivers / CUDA version
• container_support — string — e.g. "kubernetes", "docker"
• orchestration_support — string — orchestration platforms supported
• data_egress_cost — string — egress pricing description
• private_connectivity_options — string — direct connect / private link options

Example

curl -X POST https://api.fpx.world/v1/deals \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "listing_type": "cloud_gpu",
    "title": "H200 on-demand — us-east",
    "company_id": "<YOUR_COMPANY_ID>",
    "broker_id": "<YOUR_BROKER_ID>",
    "gpu_model": "H200",
    "gpu_type": "H200 SXM",
    "total_qty_available": 512,
    "gpus_per_node": 8,
    "ram_gb": 2048,
    "rental_type": "both",
    "cloud_duration": 12,
    "cloud_duration_unit": "months",
    "price": 3.95,
    "currency": "USD",
    "price_unit": "per_gpu_hour",
    "billing_granularity": "hourly",
    "network_type": "infiniband",
    "network_bandwidth": "3.2Tbps non-blocking",
    "location": "us-east",
    "availability_start_date": "2026-05-15"
  }'

Required fields

• listing_type = "powered_land"
• location — string — e.g. "West Texas"
• power_available_now_mw — number

Pricing

Powered land supports five pricing models. Use pricing_type to declare which one, then fill the matching fields.

pricing_type: "purchase" — one-time purchase

pricing_type: "option_purchase" — option plus closing price

pricing_type: "phased" — tranche-based

"phased_pricing": [
  { "block": 1, "mw": 50, "price_per_mw": 800000 },
  { "block": 2, "mw": 100, "price_per_mw": 900000 }
]

pricing_type: "jv" — joint venture

"jv_split": [
  { "party": "Landowner", "ratio": "30" },
  { "party": "Developer", "ratio": "70" }
]

pricing_type: "ground_lease" — land rent + power premium

Other commonly-used fields

• parcel_name — string — name of the parcel / site
• parcel_id_apn — string — assessor's parcel number
• total_land_area_acres — number — total parcel size in acres
• buildable_area_acres — number — usable / buildable acreage
• zoning — string — zoning classification (e.g. "Heavy Industrial")
• land_type — string — land classification
• power_topology — enum — on_grid, btm, hybrid
• grid_mw — number — grid-connected MW
• btm_mw — number — behind-the-meter MW
• generation_types — array — any of "Gas", "Solar (BESS)", "Nuclear", "Other"
• power_expandable_to_mw — number — max expandable capacity
• estimated_rfs_date — date — estimated ready-for-service date
• full_mw_delivery_date — date — date of full MW delivery
• estimated_energization_date — date — energization date estimate
• utility_provider — string — serving utility
• substation_name — string — name of nearest substation
• substation_distance — string — distance to substation (e.g. "1.2 miles")
• interconnection_status — string — current interconnection queue status
• entitlement_status — string — permitting / entitlement progress
• fiber_availability — string — available fiber carriers / routes
• water_availability — string — water supply description
• sewer_availability — string — sewer infrastructure description
• transaction_type — enum — purchase, ground_lease, option, jv, other
• asking_price — number — headline asking price
• closing_timeline — string — expected closing timeline

Example (phased purchase)

curl -X POST https://api.fpx.world/v1/deals \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "listing_type": "powered_land",
    "title": "150MW BTM parcel — West Texas",
    "company_id": "<YOUR_COMPANY_ID>",
    "broker_id": "<YOUR_BROKER_ID>",
    "parcel_name": "Abilene North",
    "location": "Abilene, TX",
    "total_land_area_acres": 320,
    "power_topology": "btm",
    "btm_mw": 150,
    "generation_types": ["Gas"],
    "power_available_now_mw": 50,
    "power_expandable_to_mw": 150,
    "estimated_rfs_date": "2026-09-01",
    "full_mw_delivery_date": "2027-06-01",
    "zoning": "Heavy Industrial",
    "utility_provider": "Oncor",
    "substation_distance": "1.2 miles",
    "transaction_type": "purchase",
    "pricing_type": "phased",
    "phased_pricing": [
      { "block": 1, "mw": 50, "price_per_mw": 750000 },
      { "block": 2, "mw": 100, "price_per_mw": 850000 }
    ]
  }'

Required fields

• listing_type = "power_equipment"
• equipment_category — enum — one of "generator", "ups", "transformer", "switchgear", "pdu", "chiller_cooling", "other"
• rated_capacity_kw_mw — string — rated capacity including units (e.g. "2500kW", "2MW")
• price — number

Pricing

Single price + currency. Typically a per-unit price.

Other commonly-used fields

• manufacturer — string — equipment manufacturer (e.g. "Caterpillar", "Schneider Electric")
• model_part_number — string — manufacturer model / part number
• voltage_phase_frequency — string — electrical specs (e.g. "480V / 3ph / 60Hz")
• fuel_prime_mover — string — fuel type or prime mover (e.g. "Diesel", "Natural Gas")
• hours_runtime — integer — runtime hours on the unit
• manufacture_year — integer — year the unit was manufactured
• condition_grade — enum — A, B, C, D, unknown
• testing_documentation — string — test reports / certifications available
• available_units — integer — count of units available

Example

curl -X POST https://api.fpx.world/v1/deals \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "listing_type": "power_equipment",
    "title": "Caterpillar 3516B — 2MW diesel genset",
    "company_id": "<YOUR_COMPANY_ID>",
    "broker_id": "<YOUR_BROKER_ID>",
    "equipment_category": "generator",
    "manufacturer": "Caterpillar",
    "model_part_number": "3516B",
    "rated_capacity_kw_mw": "2MW",
    "voltage_phase_frequency": "480V / 3ph / 60Hz",
    "fuel_prime_mover": "Diesel",
    "hours_runtime": 850,
    "manufacture_year": 2019,
    "condition_grade": "A",
    "available_units": 2,
    "price": 285000,
    "currency": "USD",
    "location": "Houston, TX"
  }'

Response

Examples

Pretty terminal output with colors:

curl https://api.fpx.world/v1/help

Plain text (e.g. saving to a file or piping to less):

curl -A "Mozilla/5.0" https://api.fpx.world/v1/help > fpx-api.txt

Sample response (truncated):

FPX Public API — v1
Base URL: https://api.fpx.world

ENDPOINTS
GET  /v1/deals                  Search public supply
POST /v1/deals                  Submit a new deal for review
POST /v1/add-bid                Place a bid on an existing offer
GET  /v1/bids                   List bids placed by a broker
GET  /v1/bid-status/:id         Get the status of a single bid
GET  /v1/help                   This page
...

Where it appears

The tracking_number field is included on every deal returned by GET /v1/deals — it is part of the common allowlist applied to every listing type, so it shows up regardless of category.

Step 1 — Search for the offer

Use any combination of filters described in GET /v1/deals to narrow down to the offer you want to bid on:

curl -H "x-api-key: YOUR_API_KEY" \
  "https://api.fpx.world/v1/deals?listing_type=hardware_gpu&gpu_model=H200&min_quantity=8&limit=10"

Step 2 — Read tracking_number from the response

{
  "success": true,
  "count": 1,
  "deals": [
    {
      "listing_type": "hardware_gpu",
      "tracking_number": "20267996029",
      "gpu_model": "H200",
      "available_units": 32,
      "price": 285000,
      "currency": "USD",
      "price_unit": "per_server",
      "location": "Dallas, TX"
    }
  ]
}

Copy the tracking_number value verbatim — both numeric strings and string forms are accepted by the bid endpoint, but treating it as an opaque string is safest (it preserves any leading zeros).

Notes

• tracking_number is stable: it does not change once an offer is published, so it is safe to store on your side.
• Only offers with deal_type = "Offer" can be bid on. Bids and archived deals are not valid targets — the bid endpoint returns 404 for unknown tracking numbers and 409 for archived offers.
• If you cannot find a tracking number for a deal you saw elsewhere, it may not be public yet (still pending approval).

Request headers

Mandatory body fields (all listing types)

Mandatory body fields per listing_type

In addition to the always-required fields above, the bid must include further fields that depend on the offer's listing_type:

Optional body fields

Anything outside this allowlist is silently dropped:

Response

{
  "success": true,
  "id": "f3a2c1b0-8d4e-4d2b-9a90-22e4b7c81234",
  "status": "request_received",
  "tracking_number": "20267996029",
  "created_at": "2026-04-27T07:31:00.123Z",
  "message": "Bid submitted for review. You will be notified when it is approved."
}

Status is 201 on success. The id is your pending-bid ID — keep it if you need to reference this submission later.

Error responses

Rate limit

Bids share the write bucket with POST /v1/deals: 10 requests / minute / IP. The successful response includes X-RateLimit-Remaining.

Example — bid on a hardware_gpu offer

curl -X POST https://api.fpx.world/v1/add-bid \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tracking_number": "20267996029",
    "broker_id": "<YOUR_BROKER_ID>",
    "company_id": "<YOUR_COMPANY_ID>",
    "price": 268000,
    "currency": "USD",
    "price_unit": "per_server",
    "quantity": 16,
    "notes": "Firm bid, FOB Dallas, 2-week close."
  }'

Example — bid on a colocation offer

curl -X POST https://api.fpx.world/v1/add-bid \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tracking_number": "20284551108",
    "broker_id": "<YOUR_BROKER_ID>",
    "company_id": "<YOUR_COMPANY_ID>",
    "power_capacity_charge": 138,
    "power_capacity_charge_currency": "EUR",
    "power_consumption_charge": 0.11,
    "is_dynamic_pricing": false,
    "notes": "5MW commit, 5-year term."
  }'

Example — bid on a cloud_gpu offer

curl -X POST https://api.fpx.world/v1/add-bid \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tracking_number": "20271108882",
    "broker_id": "<YOUR_BROKER_ID>",
    "company_id": "<YOUR_COMPANY_ID>",
    "price": 3.65,
    "currency": "USD",
    "price_unit": "per_gpu_hour",
    "duration": 12,
    "duration_unit": "months",
    "quantity": 256
  }'

Request headers

Query parameters

Status pipeline

The status field reflects where an inquiry sits in the FPX deal pipeline. Stages flow top-to-bottom; deals can also exit at any point via closed_lost_cancelled.

Response

{
  "success": true,
  "count": 2,
  "offset": 0,
  "limit": 50,
  "total": 2,
  "bids": [
    {
      "id": "f3a2c1b0-8d4e-4d2b-9a90-22e4b7c81234",
      "deal_id": "9b1d6c84-1f47-4b9d-8c1b-77f0e1aa0001",
      "deal_name": "H200 supply, Dallas",
      "status": "in_discussion",
      "tracking_number": "20267996029",
      "created_at": "2026-04-20T07:31:00.123Z"
    },
    {
      "id": "0d2bc44a-7c39-4e27-9b61-3a9b1b22aaaa",
      "deal_id": "ab6c5c81-89b7-43c3-8d72-19e22a11bbbb",
      "deal_name": "5MW colocation, Frankfurt",
      "status": "matching_inventory",
      "tracking_number": "20284551108",
      "created_at": "2026-04-19T16:02:11.443Z"
    }
  ]
}

Error responses

Examples

List every bid for a broker (newest first):

curl -G https://api.fpx.world/v1/bids \
  -H "x-api-key: YOUR_API_KEY" \
  --data-urlencode "broker_id=<YOUR_BROKER_ID>"

Page through bids 50 at a time, only the ones currently in negotiation:

curl -G https://api.fpx.world/v1/bids \
  -H "x-api-key: YOUR_API_KEY" \
  --data-urlencode "broker_id=<YOUR_BROKER_ID>" \
  --data-urlencode "status=negotiating" \
  --data-urlencode "limit=50" \
  --data-urlencode "offset=0"

URL parameters

Response

// inquiry being routed by FPX
{
  "success": true,
  "id": "f3a2c1b0-8d4e-4d2b-9a90-22e4b7c81234",
  "status": "matching_inventory"
}

// buyer and supplier in active discussion
{
  "success": true,
  "id": "0d2bc44a-7c39-4e27-9b61-3a9b1b22aaaa",
  "status": "in_discussion"
}

// signed deal
{
  "success": true,
  "id": "12cb7e9a-4abc-49a1-9f8b-77ff90112233",
  "status": "signed_confirmed"
}

Error responses

Example

curl https://api.fpx.world/v1/bid-status/f3a2c1b0-8d4e-4d2b-9a90-22e4b7c81234 \
  -H "x-api-key: YOUR_API_KEY"