Describe what the buyer would receive
Begin with the supplying company, a business contact and the broad location. Explain whether you operate the hardware, own an allocation or act with written authority for another operator. Identify the unit being offered: a single GPU instance, a complete node, a cluster or another clearly defined service.
A useful submission contains the exact GPU variant, memory, GPU count, node arrangement, interconnect, host CPU and RAM, storage, network and supported access method. Distinguish installed equipment from capacity that is available for the dates being offered.
| Submission field | Useful evidence |
|---|---|
| Hardware | Configuration report and node or allocation specification |
| Availability | Start and end windows, minimum term and any competing commitment |
| Authority | Operator identity or the permission under which you offer capacity |
| Commercial terms | Currency, pricing unit, inclusions, exclusions and quote validity |
| Delivery | Provisioning process, access isolation, support and failure handling |
| Restrictions | Permitted workloads, region constraints and any relevant data conditions |
Quote in a unit a buyer can understand
State whether the price is per GPU-hour, node-hour, day or another reservation period. If an entire node must be booked, make that requirement explicit. List storage, data transfer, setup and support charges separately where they are additional. Give a date or event when the quote expires.
For a proposed allocation, explain what still needs to happen before it can be delivered. Do not describe planned equipment, unsigned hosting or a hoped-for release of capacity as available stock. Clear uncertainty is more useful than an apparently complete offer that cannot be confirmed.
Explain access and the operating relationship
Describe how a customer receives access, how access is removed after the booking, and who responds when the service does not work. Say whether you support the operating environment or provide infrastructure only. Any service level, replacement or refund commitment needs to be stated in the commercial terms.
Use the submission form for a specification and business contact. Do not upload passwords, customer access details or private datasets. Detailed commercial documents can be exchanged through the appropriate private process after the initial review.
Keep resale and transfer rights separate
Authority to offer your own available capacity does not automatically give a buyer permission to transfer a booking. If a proposed service involves another party's allocation, identify the relevant consent and restrictions. Machine Age AI's secondary marketplace and tokenisation remain coming soon.
The current supply process creates a private review record. It does not issue a token, create a transferable right, approve a supplier or make a purchase commitment. Publication and any subsequent order require separate confirmation of the relevant details.
What happens after submission
Machine Age AI reviews the specification, authority, availability and commercial fit. We may ask for clarification before considering publication or a buyer introduction. There is no guaranteed volume or acceptance time.
A focused submission is easier to assess than a general capacity claim. Start with one configuration and a credible delivery window, then explain what can scale if there is an appropriate buyer requirement.
Sources and scope
Source pages checked on 30 September 2026. Provider terms can change. Machine Age AI publishes this guide and may coordinate enquiries arising from it.
Frank Dean is Machine Age AI’s AI-generated founder persona.