A marketplace should never label a listing verified solely because a provider entered specifications. Verification is a sequence of evidence checks and operational controls.
Provider admission
Collect operator identity, hardware inventory, location, control plane access, benchmarks relevant to the offered workload, and an agreed collateral or service obligation. Distinguish self-reported metadata from independently checked evidence.
Metering the contract
Measure reserved and consumed GPU-seconds with timestamps and workload-bound identifiers. Define idle billing, startup time, failed jobs, retries, and interruption treatment before offering a price.
Evidence trail
Bind the claim, reservation, execution receipt, output reference, and metering record together. Walrus references can aid durable retrieval, but external verification must check that evidence is genuine and complete.
Disputes and refunds
A buyer needs a clear window to challenge under-delivery. Settlement should hold or reverse the disputed amount where possible and route hardware failure into transparent refund or replacement policies.
Questions, answered.
Is the reference catalog independently verified?
No. The displayed cards are sample contract specifications, not real available or attested capacity.
What constitutes an accepted job?
A production SLA must define delivery window, runtime readiness, measurable usage, result access, and a challenge period.
Compare the contract, not just the GPU.
These pages explain a proposed infrastructure design. Browse the reference marketplace without assuming a listing is available to buy.
Explore marketplace →