Give an agent a keypair and a spending cap. It provisions GPUs, runs the job and settles with the host peer to peer in compute credits it can verify itself — and stops the moment it hits the cap.
For agentsHow it works
Buy compute credits by card or with BSV. At launch credits are entries in GPUte's ledger; from phase 2 each credit is a b017 token on Bitcoin SV, the token protocol stewarded by the BOLT Association, and traces back to GPUte's published issuer key.
Describe the job once, from the command line or from a coding agent: gpute deploy run.sh. GPUte picks a machine, sets up the environment and streams the logs.
The job's time limit sets the cap, which is the most the job can cost. You transfer a token worth the cap when the job starts. When it ends, the system keeps payment for the seconds run and returns the rest automatically. Queueing and setup are free.
For agents
From phase 2 an agent is a first-class customer: it holds credits and spends them without a person. This describes the planned design, not yet live.
gpute deploy is an MCP tool, so an agent scales out by calling it, not by clicking — under the same cap and metering as a person.What is different
The comparisons below come from each service's public documentation in October 2026. The GPUte lines describe the planned design.
For GPU owners
The community tier opens by invitation first, then to anyone once verification is in place.
Where this stands. GPUte is a concept. No service is live, prices are not set, no credits have been issued and the settlement token has not been written. The legal treatment of the credit token still needs professional review before any sale.
Sources and references
Links