Run your own storefront, publish machine-readable offers where you choose, apply participant-controlled agent policy, and deliver from your own infrastructure.
Storefront server · admin CLI · signed HTTP API
SCM is market infrastructure, not a provider profile or a promise of demand. The seller operates the commercial and delivery surface.
Arkhai gives supply a market interface without turning the supplier into a managed account inside a central marketplace.
Remain the attributable publisher and operate the signed endpoint where buyers inspect and negotiate machine-readable terms.
Publish machine-readable offers to one registry, several registries, or a private registry without handing inventory custody to Arkhai.
Use listed-price behavior or compatible rule-based, custom, and learned policy under seller control.
Provisioning, credentials, lifecycle management, and teardown remain on seller infrastructure.
A resource pool groups the physical candidates and provider routing behind a fungible capacity offer. Your storefront still owns the machine-readable market offer, policy, and deal state.
Provider resources
Hardware under your operation
Resource pool
Candidates + provider routing
Capacity offering
Storefront-owned market terms
Agreement
Buyer and seller commit
Selected resource
Scheduler binds fulfillment
Offer fungible capacity by default. Buyers negotiate the shape they need while fulfillment chooses an eligible resource after agreement.
Disable a pool to prevent new assignments without erasing its members or the lifecycle records of work already in flight.
Use a specific-resource listing only when a buyer needs to constrain placement, such as for a concrete resource or locality requirement.
Resource-pool metadata and provider configuration guide fulfillment. Listing price, settlement options, seller policy, and market history remain storefront-owned commercial decisions.
Read the POOLS architecture ↗The seller turns capacity into a machine-readable offer before a buyer has made a choice, then retains delivery responsibility after payment settlement.
Agreement precedes payment settlement. Provisioning and credentials remain seller-owned domain delivery.
The listing is not merely a hardware advert. It contains the commercial and delivery constraints the buyer can inspect.
Offered resource and region
Accepted escrow terms and duration
Arbitration demands and publication destinations
Storefront policy and provisioning integration
Accepting, countering, and exiting are possible outcomes of participant-controlled agent policy—not separate product policies a marketplace imposes.
The quickstart covers the actual stack: configuration, capacity input, storefront service, signed publication, and verification.
docker compose -f compose/seller.yml up -d
docker compose -f compose/seller.yml exec seller-storefront \\
market-storefront publish --inventory /app/resources.csvRun a storefront server and admin CLI
Publish a signing-address-attributed listing through an authenticated request
Expose signed storefront endpoints to buyer clients
Configure real KVM delivery separately from dry-run mode