Purchasing checklist
Confirm model access, effective prices, capacity inclusions and acceptance before starting a Grid, Dedicated or Projects engagement.
Use this checklist to review the written scope with your technical, finance and procurement teams. Start with Pricing to choose a buying path. A submitted inquiry starts that conversation; access, capacity and delivery are confirmed separately.
Grid API access#
| Confirm | Record in the account agreement |
|---|---|
| Eligible models | Model identifier, served version and precision, enabled capabilities and limits. |
| Run mode | Serverless or eligible Batch, request limits and the operating region. |
| Token rates | Separate input, cached-input and output rates; currency, effective date and validity. |
| Other usage | Any routing charge, credits, taxes and other chargeable services. |
| Activation | The account owner, enabled access and the first verified request. |
The public model prices are new-account references reviewed on 4 October 2026. Existing agreements retain their effective rates. The authenticated model list determines what the account can call. Billing explains token calculation and reconciliation.
Dedicated and Private capacity#
Prepare configuration, quantity, desired region, start and duration in the capacity brief. Brazil inventory is planned for May 2027. The quote confirms availability and the following terms.
| Confirm | Record in the capacity proposal |
|---|---|
| Deliverable configuration | Accelerator and node type, memory, interconnect and supporting resources. |
| Quantity and location | Number of GPUs or nodes, the billing unit, operating region and any data boundary. |
| Commitment | Minimum quantity, minimum duration, billed period and delivery window. |
| Price | Setup fee, recurring rate, currency, validity, payment schedule and tax treatment. |
| Inclusions | Storage, networking, egress, licences, support and included model usage. |
| Excess and changes | Additional consumption, changes to quantity, renewal and cancellation terms. |
| Acceptance and operation | The acceptance test, start of billing, support responsibilities and agreed service levels. |
The L4 and B200 GPU-hour references on Pricing identify metering units. Configuration and total package cost are confirmed in the capacity proposal. State whether token consumption is included or billed separately so an included service is counted once.
Projects#
Prepare the problem, volume, integrations and success criterion in the project brief. The proposal separates implementation from ongoing operation.
| Confirm | Record in the project proposal |
|---|---|
| Outcome and boundary | Production problem, deliverables, exclusions and the responsible teams. |
| Workload | Expected volume, data inputs, integrations and deployment requirements. |
| Implementation | Discovery and delivery fees, milestones, dependencies and timeline. |
| Recurring operation | Operating fees, included volume, model and capacity consumption, and excess usage. |
| Acceptance | Evaluation set, baseline, measurable success criterion and the person approving the result. |
| Handover | Support, monitoring, change requests and responsibilities after acceptance. |
Training has a separate job, training-token or capacity scope. Detection confirms its own text unit, limits and rates. Their prices are confirmed for the selected service and workload.
Procurement and follow-up#
Use Trust and deployment to prepare the required deployment boundary and document review. The evidence and procurement guide helps your team request applicable documents and record the review outcome. Confirm the applicable agreement, data-processing terms, support scope and any required approved evidence with the team before production acceptance.
After submission, keep the request reference and include it if you follow up by email. Closing a form keeps its answers and current step during this browser visit. Open the same request to continue. If a different offer, prepared brief or Grid pricing context is opened, choose whether to continue the existing draft or use the new request. Using the new request replaces the prior draft and clears its contact details. Company contact topics keep separate requirements and additional context while you switch between them. Completed confirmations remain available until you start another request. Refreshing the page clears these drafts and confirmations; they are not saved between visits. Preparing or resuming a draft does not submit it.
A submission confirmation does not reserve capacity or grant Grid access. If the form cannot confirm submission, your draft stays available for editing and retrying.