# GPU and accelerator capacity by type, count and term

> Record a requirement for GPU or accelerator capacity: chip type, count, hours or term, region, interconnect and how firmly you would commit.

Status: request only.

## What it is for

A team training or serving a model needs a specific accelerator in a specific quantity, often with a fast interconnect between nodes, for a known number of hours or a contract term, sometimes in a region set by data rules. Availability of large clusters is uneven, and smaller buyers struggle to get term pricing. This records chip, count, duration, region and commitment so that which configurations buyers cannot get, and at what price, can be studied.

Machine-learning engineers and research groups, startups training or fine-tuning models, inference teams planning capacity, and agents provisioning compute for them.

## What happens to a request

The configuration and term are recorded as given. No capacity is held, reserved or resold here, no provider is contacted and no account is opened. If you leave a contact and a provider offering that configuration can be identified, a reply may come; it is not promised. Contact details are stored apart from the requirement and deleted after 180 days.

## What you get

A receipt with the request's identifier, the fields we could not match (a provider, an hourly price or an availability date is never supplied here), and a plain statement of what happens next.

## Scope and limits

Any region; data-residency requirements are recorded as stated.

- No compute is held, reserved or resold; this records the requirement.
- Prices and availability you mention are recorded as your statement, not checked against any provider.
- Export controls and data-residency rules that apply to your workload are yours to determine.

## Make a request

POST the configuration to /compute-capacity/requests (or /requests), use the form on this page, or call the submit_request MCP tool with proposition "compute-capacity".

POST https://services.forevenza.com/compute-capacity/requests with JSON like:

```json
{
  "action": "lease",
  "need": "64 NVIDIA H100 SXM GPUs (8 nodes) with InfiniBand between nodes, bare metal with Slurm, in the US or EU, for one month from 1 December to train a 30B-parameter model.",
  "specifications": {
    "accelerator": "NVIDIA H100 SXM 80GB",
    "accelerator_count": 64,
    "gpu_hours": 46080,
    "term": "RESERVED_1_MONTH",
    "region": "United States or European Union",
    "interconnect": "INFINIBAND",
    "start_date": "2026-12-01",
    "deployment": "SLURM"
  },
  "quantity": {
    "amount": 46080,
    "unit": "GPU-hours"
  },
  "timing": {
    "earliest": "2026-12-01",
    "latest": "2026-12-31"
  },
  "geography": {
    "text": "United States or European Union"
  },
  "budget": {
    "amount": 2.2,
    "currency": "USD",
    "per": "unit"
  }
}
```

Schema: https://services.forevenza.com/compute-capacity/schema.json