Compute service requests
Private tickets, quotes, authorization, delivery and retention.
Compute services accepts a scoped request for scientific computation or delivery. The current flow creates a private ticket and separates review, proposal, quote confirmation, budget, execution and delivery. Submitting a form is not a paid service execution or a guarantee of a particular result.
Describe a useful request#
Explain the question, intended model/task, stimulus or target scope, required outputs, deadline and whether any material is private. State the allowed scientific interpretation. For example, a numerical response comparison has a different deliverable from a claim of biological predictive performance.
Supported scoping concepts include stimulus search, response comparison, public sponsorship, retrieval and delivery. Private execution, arbitrary parameter scans, multiple-model products or undisclosed biological accuracy are not automatically available because a request field exists.
Do not submit executable instructions or secrets. Customer text is treated as data. Restricted or sensitive requests need actual review and appropriate authorization.
Request lifecycle#
| Stage | Meaning |
|---|---|
| Received | Validated request is durably stored and a private ticket is issued |
| Scope review | Operator assesses scientific, licensing, resource and privacy requirements |
| Proposal | Deliverables and acceptance criteria are described |
| Quote confirmation | Customer reviews the actual price and terms |
| Budget required | Work awaits its explicit funding/authorization conditions |
| Executing | Authorized work is being performed |
| Delivered | Agreed artifacts/evidence are delivered under the contract |
| Closed | Contract/ticket closure is recorded without erasing required obligations |
Signed operator actions and customer confirmations record the transitions. A repeated submission should use its idempotent request identity rather than generate another purchase for the same retry.
Quotes and acceptance#
A quote should separate execution, replay, archive retention, transport, transaction fees, account principal, deposits and prepayments. It should identify the asset, amount, beneficiary, funding source and applicable refund treatment.
Delivery criteria should specify model/task identity, complete run scope, file manifest, hashes, required replay and permitted uses. A delivered file is accepted according to those criteria; a proposed target metric is not an achieved accuracy result.
Production payment routes and formal assets remain unconfigured. Draft catalog prices are not active offers. See Marketplace roadmap.
Private tickets and publication#
The ticket is accessed through its private receipt token and authorized operations. Protect that token as an access credential. Public results require separate publication authorization; the ticket is not automatically posted to the Explorer or result center.
Confidential public-miner execution is not promised without real isolation and access control. Resolve licensing and customer-data boundaries before assigning work beyond the authorized operator environment.
Retention and help#
Request fields are removed after at most 365 days under the documented request policy. Audit and contract retention has separately disclosed requirements. Read Privacy and Terms for the applicable notices.
For a question about an existing request, use its private ticket path and provide the scope/status rather than sharing the receipt token publicly. The request page can also be used to report a product issue with nonsensitive diagnostic information.
See feature availability for release scope and pending acceptance.