- Reserved: buyers purchase available whole nodes for a fixed window on Market.
- Spot: offer interruptible VM capacity on the Spot orderbook. Your asking price is the amount you want to receive per GPU-hour; it does not automatically become the market price. Spot begins only when physical nodes are delivered and available.
Relist a reservation
1
Listing
Open your reservation in Nodes and choose Relist capacity. Select the nodes to offer.
Leave Offer on Spot unchecked for reserved sales, or check it to offer Spot capacity. Spot
requires VM capacity and does not require a reserved term. Full physical nodes must be assigned
to your reservation before you can relist them. You can offer future dates without starting a
workload on those nodes. Renewable reservations, including month-to-month contracts, cannot be
relisted, even if they have a scheduled end. Spot and On-demand reservations cannot be relisted.
2
Pricing
Enter your Asking price (USD / GPU-hr): what you receive for each GPU-hour sold. Buyers see
their applicable price including fees.
3
Availability
Choose a start and, if your reservation has a committed end, an end within that window. If your
reservation has no committed end, you can leave End blank for no scheduled availability
deadline. For reserved sales, set a minimum rental commitment and, when availability has no end,
a maximum rental duration. Spot uses renewable one-hour terms automatically. You can offer any
subset of your whole nodes—for example, two nodes from a four-node reservation. Availability
cannot extend beyond your reservation. The review shows exact seconds and your time zone.
Reserved resale windows are fixed; renewable Reserved resale terms are not supported. Each
Reserved purchase still has its own fixed end. Hourly rentals stop at a listing deadline when
one is set, or can end earlier through the usual interruption and stop rules.
4
Review and publish
Choose Review listing, check the nodes, type, price, and dates, then Publish listing.
Open Market or Spot from the confirmation. Future Spot capacity will not be offered for
immediate use before its start time and delivery.
Several relists of one reservation
You can relist the same reservation more than once, as long as no two live relists cover the same node at the same time. For example, reserve days 10–17 and create separate listings for days 11–13 and 15–17. Use Create another listing after publishing to enter the next window. In the Market, relists of the same nodes appear together on one bar, each in its own color, and a buyer can buy across them in one drag. If a relist would overlap another live relist of the same nodes, Ornn refuses it and says so. Delist the other relist, or choose different nodes or a time slice that does not overlap. Ornn also refuses a relist for a window that is already sold from this reservation. Delisting stops new sales but keeps existing bookings valid. Changing another relist’s availability cannot overlap those booked windows, even after the original listing is delisted. Your organization cannot buy or fill its own listings. Existing listings with legacy terms may continue to offer both scheduled windows and idle Spot capacity. Their existing contracts and prices are unchanged.Manage a relist
Open Nodes → Offers & listings to see your relists, their availability, offered terms and prices, sold windows, and trades. Offered term prices refresh automatically. If loading another page fails, choose Retry loading listings; your existing listings stay visible.- Listing prices are shown per offered term. Price editing is not available in the console.
- Delist to withdraw the listing from new bookings. Running Spot VMs will stop. You cannot delist while a non-Spot reservation is active. Future scheduled reservations keep their agreed terms.
ornn spot cancel --order-id <spot-reservation-id> ends one spot VM running on your nodes without delisting.
Getting paid
- Sold windows: you receive your asking price for the window. The buyer pays the whole window up front, and you are credited when the window ends. If Ornn cancels a sold window early, you are credited for the part that was used.
- Spot hours: you receive your asking price for each hour a buyer takes from your ask, or the bid price shown when your node fills a resting bid. A trade on your relist shows the price you receive.
Use the API
You can relist with an API key, the Ornn CLI, or the MCP server instead of the console. Prices are integer micro-USD per GPU-hour:2500000 is $2.50. Your asking price is what you receive. The Relist API reference lists every field and error.
1. Check what you can relist
relistableNodeCount is how many whole nodes you can relist. When it is 0, relistUnavailableReason says why. relistableNodeIds lists the assigned nodes you can select. A node already relisted or sold for part of your window is refused when you relist.
2. Create the relist
Choose a window inside the reservation, using whole-second times, and one or more terms:- Reserved (
type: reserved): buyers buy windows in the Market. SetminDurationHoursto the shortest rental you accept andmaxDurationHoursno longer than your window. Userenewable: false. - Spot (
type: spot): your nodes’ idle time goes on the Spot order book at your asking price. Spot requires VM capacity. Set both durations to1andrenewabletotrue.
nodeCount IDs in nodeIds. Omit nodeIds to let Ornn choose free assigned nodes.
Every relist needs an Idempotency-Key header. Use a new key for each relist and keep it: if the response is lost, send the same request with the same key to get the original listing back instead of creating a second one. The CLI generates a key for you unless you pass --idempotency-key.
201 with the listing, in state available, and its terms. Errors use detail.code: for example relist_nodes_unavailable when a selected node is already relisted or sold for part of the window, relist_delivery_pending before nodes can be relisted, or invalid_spot_listing for a Spot term on Bare Metal capacity.
Listing changes are sent to Market as soon as they are saved, including new
listings, availability changes, and withdrawals. If publication is temporarily
unavailable, your saved change is retried automatically.
3. Manage your relists
- Pause or resume a listing:
PATCH /commerce/v2/listings/{listingId}withstateset todraft,available, ordelisted. On a relist, capacity, specifications, and dates cannot change. An active non-Spot reservation prevents changing the listing to draft or delisted. - Add a term:
POST /commerce/v2/listings/{listingId}/terms, with anIdempotency-Key. For example, add a Spot term to a VM relist that sells reserved windows. - Delete an unused term:
DELETE /commerce/v2/listings/{listingId}/terms/{listingTermsId}. - List the listing’s nodes:
GET /commerce/v2/listings/{listingId}/nodes.
listingId set to your listing: the response shows the trades on it, priced at what you receive.
Listing reads (GET /commerce/v2/listings and GET /commerce/v2/listings/{listingId}) include optional offer specifications: cpu, ram, storage, fabricType (GPU interconnect), and internet (internet bandwidth). Unknown specifications are null. Reservation-based relists inherit these specifications from their source listing.
The API also provides listing preview images at GET /commerce/v2/listings/{listingId}/og.png and specification PDFs at GET /commerce/v2/listings/{listingId}/spec.pdf. These show capacity and facility details. Specification PDFs also include CPU, RAM, storage, and GPU interconnect when supplied. Retrieve selectable terms with GET /commerce/v2/listings/{listingId}/terms to compare their prices.
What’s next

Market
See how buyers find and buy relisted capacity.

Nodes
Find your reservations and their relists.