Simple Compute Market For Compute Buyers

Simple Compute Market Series

Historical release context — May 29, 2026 component release

This post discusses the May 29 market-cli-v0.5.3 component release and its publication-time framing. Current main is later and is covered by the repository's root MIT license; the component tag predates that root license. Neither the release nor current source proves an Arkhai-hosted market or live supply. See Arkhai Compute and current SCM source for current boundaries.

Key Takeaways

• SCM gives buyers a software-driven path through configured registries: discover, negotiate scalar price, escrow, receive, and settle
• Agent procurement needs machine-readable evidence and actions rather than browser-only dashboards and manual clicks
• Beyond machine-readable APIs, SCM adds crypto-native settlement, policy-governed price negotiation, deployment-set settlement assets, and arbiter and release criteria
• Buyer software drives buyer-side decisions through discover, evaluate, negotiate, commit, receive, track, settle, and recover; the seller still provisions and delivers
• Listings retain publisher provenance, seller-asserted availability, and separate displayed and final terms; provenance is not verified legal identity or KYB
• The public open-beta code release provisions KVM VMs with SSH access and optional GPU passthrough; other delivery adapters require separate implementation and confirmation

Your software can already schedule a workload. Buying the compute to run it still means dashboards, sales forms, fixed catalogs, quotes, and a person clicking approve.

That model does not fit an agent.

SCM gives buyers a path through one or more configured operator registries: discover publisher-attributed listings, negotiate scalar price under policy, lock escrow, receive access, and settle through software. Registry access can be open or gated, and operators and optional services can still coordinate a deployment; SCM does not require one mandatory platform-owned broker. The launch post introduced the release; this is the same software from the buyer's seat.

The public open-beta code release has a concrete delivery path: KVM virtual machines with SSH access and optional GPU passthrough. Other delivery adapters require separate implementation and confirmation.

What Agent Procurement Needs

Human buying assumes a human in the loop: a dashboard to read, a form to fill, a quote to wait on, an approval to click. None of that survives contact with an agent that has a workload, a budget, and a deadline.

An agent needs the market evidence to be inspectable. Listings retain signing-publisher and source provenance, but that is not verified legal identity or KYB. Availability is seller-asserted rather than independently verified real-time capacity. Displayed terms and final negotiated terms remain distinct; commitments, delivery state, and the settlement path must be readable without implying that every assertion is verified.

Plenty of compute APIs are already machine-readable. What SCM adds is crypto-native settlement, policy-governed price negotiation, settlement assets that can vary by deployment, and arbiter and release criteria a deployment can set for itself.

It also means a registry or market operator does not rebuild escrow, recovery, and settlement from scratch for every new deployment. Those paths come with the buyer flow.

The Buyer Flow

The buyer's path through SCM is a sequence software can drive on the buyer side; sellers remain responsible for infrastructure, provisioning, credentials handoff, and delivery:

• Discover. Query one or more configured operator registries for listings.
• Evaluate. Weigh the offers against what the workload needs.
• Negotiate. Talk to a seller's storefront over signed HTTP and a negotiation policy. The current VM flow negotiates price; duration, resource, and escrow fields are fixed or validated by the selected schema and policies.
• Commit. Lock escrow through Alkahest once terms are accepted.
• Receive. Take VM access through SSH credential handoff.
• Track. Follow lease status and delivery evidence.
• Settle and recover. Work the settlement, reclaim, refund, and recovery paths when a deal completes, expires, or fails.

Buyer-side choices remain under buyer policy. Sellers still provision and deliver, while operators configure registries, access, and settlement. No single mandatory broker must hold the relationship, set a universal price, or custody the funds.

What To Try

A buyer evaluating SCM can start small:

• Inspect the market buyer runtime in the repository.
• Follow the buyer quickstart.
• Run or read a negotiation against a market-storefront.
• Decide whether KVM VMs, with optional GPU passthrough, fit the first workload, or whether another compute adapter should be scoped separately.
• Decide which pricing policy fits: deterministic, custom, or a Puffer-based reinforcement learning example.

Try The Buyer Flow

• Explore the repository
• Follow the buyer quickstart
• Request a Market
• Scope a buyer evaluation

Find compute. Agree on terms. Make a credible commitment. Receive the machine.

Give software a workload. Let it procure compute.

Next, the seller's side: publishing capacity, setting policy, verifying commitments, and running delivery.