Machine-readable records
Participation in SCM is machine-readable end to end: listings, negotiation rounds, agreements, settlement state, and fulfillment results are all data. Start with the Registry's pinned listing wire shape, then use the two larger website review projections to see how that data can be presented alongside domain, settlement, and delivery context.
Canonical Registry listing shape
Registry HTTP reads return an envelope with items, count, and
total_after_filter; market listing list aggregates the items arrays
from the Registries the buyer selected and prints that array as raw JSON.
The single-item HTTP response below is assembled directly from the pinned
Registry serializer and its authenticated-publish integration fixture.
Angle-bracket strings mark timestamps the Registry assigns at runtime:
{
"items": [
{
"listing_id": "eip191-listing-1",
"publisher_id": 1,
"storefront_url": "http://my-storefront/",
"offer_resource": {
"gpu_model": "H200",
"region": "us"
},
"accepted_escrows": [
{
"chain_name": "anvil",
"escrow_address": "0x1111111111111111111111111111111111111111",
"literal_fields": {
"token": "0x2222222222222222222222222222222222222222"
},
"rates": [
{
"field": "amount",
"per": "hour",
"value": "100"
}
]
}
],
"demands": [],
"max_duration_seconds": 3600,
"oracle_address": null,
"status": "open",
"created_at": "<ISO-8601 timestamp>",
"updated_at": "<ISO-8601 timestamp>"
}
],
"count": 1,
"total_after_filter": 1
}
The serializer is
order_to_dict;
the values retained above come from the pinned
signed-publish fixture.
The signature is part of the publish request, not the public listing-read
record. publisher_id and timestamps are Registry state; publisher
attribution ultimately resolves to the signing-wallet address, not a
verified real-world identity.
A Registry listing is one discovery artifact. Negotiation history, agreement, settlement state, and fulfillment results live in separate machine-readable artifacts; they are not fields on this listing response.
Both projections below are the deterministic review examples the
Market page also projects — each panel carries a persistent
Review projection label. They demonstrate record shape and field
semantics; they are not live listings, inventory, or availability, and this
site performs no transaction. They are website presentation records, not
canonical SCM wire objects.
Website virtual-machine presentation projection
A VM listing describes a compute slice, its attributed publisher, its commercial terms, and its delivery modality. Read it top to bottom as: who published what, on which terms, settled how, delivered how.
{
"market_data": true,
"listing_id": "vm-atlas-4x",
"kind": "virtual-machine",
"seller": "seller-a",
"publisher": "publisher-a",
"storefront": "storefront-atlas",
"registry": "registry-east",
"published_at": "2026-07-01T12:00:00Z",
"domain": "virtual-machine",
"schema": "arkhai.compute.vm@1.0.0",
"location": "Virginia, US",
"availability": {
"asserted_by": "seller",
"state": "asserted-available"
},
"pricing": {
"mode": "configured-negotiation",
"advertised_rate": {
"decimal": "2.40",
"currency": "USD",
"display": "$2.40"
},
"advertised_unit": "GPU-hour",
"quantity": {
"decimal": "4",
"unit": "GPU",
"display": "4 GPUs"
},
"duration": {
"decimal": "4",
"unit": "hour",
"display": "4-hour minimum"
},
"constraints": [
"4× H100 80 GB",
"192 vCPU",
"2 TB RAM",
"100 Gbps fabric",
"Buyer SSH key"
]
},
"negotiation": [
{
"stage": "advertised",
"status": "shown",
"actor": "seller",
"round": 0,
"signature": "seller-signature-00",
"occurred_at": "2026-07-01T12:00:00Z",
"amount": {
"decimal": "38.40",
"currency": "USD",
"display": "$38.40"
}
},
{
"stage": "buyer-proposed",
"status": "shown",
"actor": "buyer",
"round": 1,
"signature": "buyer-signature-01",
"occurred_at": "2026-07-01T12:04:00Z",
"amount": {
"decimal": "36.00",
"currency": "USD",
"display": "$36.00"
}
},
{
"stage": "seller-countered",
"status": "shown",
"actor": "seller",
"round": 2,
"signature": "seller-signature-02",
"occurred_at": "2026-07-01T12:05:00Z",
"amount": {
"decimal": "37.20",
"currency": "USD",
"display": "$37.20"
}
},
{
"stage": "agreed",
"status": "shown",
"actor": "buyer",
"round": 3,
"signature": "buyer-acceptance-03",
"occurred_at": "2026-07-01T12:06:00Z",
"amount": {
"decimal": "37.20",
"currency": "USD",
"display": "$37.20"
}
}
],
"settlement": {
"asset_class": "USD",
"network": "Configured settlement network A",
"mechanism": "Configured escrow"
},
"lifecycle": {
"advertised": {
"status": "complete",
"label": "Published"
},
"proposed": {
"status": "complete",
"label": "Buyer proposal signed"
},
"countered": {
"status": "complete",
"label": "Seller counter signed"
},
"agreed": {
"status": "complete",
"label": "Buyer accepted"
},
"settled": {
"status": "complete",
"label": "Settlement submitted"
},
"fulfilled": {
"status": "complete",
"label": "Credentials delivered"
},
"resolved": {
"status": "not-started",
"label": "No resolution invoked"
}
},
"delivery": {
"modality": "SSH lease",
"capacity": {
"status": "complete",
"label": "POOLS hold committed"
},
"fulfillment": {
"status": "complete",
"label": "Provider fulfillment complete"
},
"credential": {
"status": "complete",
"label": "Buyer SSH key issued"
},
"service": {
"status": "current",
"label": "Lease status available"
}
},
"resource": {
"hardware": "4× H100 80 GB",
"compute": "192 vCPU",
"memory": "2 TB RAM",
"network": "100 Gbps fabric",
"access": "Buyer SSH key"
}
}
Field notes:
provenance— the storefront and signing publisher. Attribution is cryptographic: publishing is an EIP-191-signed request, and the Registry creates the publisher record from the signature. This proves control of the signing key for that request; it does not verify real-world identity, capacity, availability, or performance.terms— the advertised rate and unit. Listed-price acceptance is the direct path; where scalar negotiation is configured, only the amount moves.settlement— the configured mechanism that services the escrow after explicit agreement. Payment lives here, not in delivery.delivery— seller-owned fulfillment: capacity reservation, VM lifecycle, and access credentials follow settlement.
Website inference API-credit presentation projection
An API-credit listing sells prepaid request quota for a named service. There is no compute provisioner in this path: fulfillment issues a seller-issued bearer credential, and a gateway meters credits per request.
{
"market_data": true,
"listing_id": "api-orbit-credits",
"kind": "api-credits",
"seller": "seller-c",
"publisher": "publisher-c",
"storefront": "storefront-orbit",
"registry": "registry-api",
"published_at": "2026-07-03T15:30:00Z",
"domain": "api-credits",
"schema": "arkhai.compute.api-credits@1.1.0",
"location": "Global API",
"availability": {
"asserted_by": "seller",
"state": "asserted-available"
},
"pricing": {
"mode": "listed",
"advertised_rate": {
"decimal": "48.00",
"currency": "USD",
"display": "$48"
},
"advertised_unit": "10M tokens",
"quantity": {
"decimal": "1",
"unit": "10M-token block",
"display": "One 10M-token block"
},
"duration": null,
"constraints": [
"OpenAI-compatible inference",
"Qwen3-235B-A22B-Instruct-2507",
"Text-generation quota",
"Metered balance"
]
},
"negotiation": [
{
"stage": "advertised",
"status": "shown",
"actor": "seller",
"round": 0,
"signature": "seller-signature-20",
"occurred_at": "2026-07-03T15:30:00Z",
"amount": {
"decimal": "48.00",
"currency": "USD",
"display": "$48.00"
}
},
{
"stage": "buyer-proposed",
"status": "shown",
"actor": "buyer",
"round": 1,
"signature": "buyer-signature-21",
"occurred_at": "2026-07-03T15:34:00Z",
"amount": {
"decimal": "48.00",
"currency": "USD",
"display": "$48.00"
}
},
{
"stage": "seller-countered",
"status": "not-applicable",
"actor": null,
"round": null,
"signature": null,
"occurred_at": null,
"amount": null
},
{
"stage": "agreed",
"status": "shown",
"actor": "buyer",
"round": 2,
"signature": "buyer-acceptance-22",
"occurred_at": "2026-07-03T15:35:00Z",
"amount": {
"decimal": "48.00",
"currency": "USD",
"display": "$48.00"
}
}
],
"settlement": {
"asset_class": "USD",
"network": "Configured settlement network B",
"mechanism": "Prepaid balance"
},
"lifecycle": {
"advertised": {
"status": "complete",
"label": "Published"
},
"proposed": {
"status": "complete",
"label": "Listed total proposed"
},
"countered": {
"status": "not-applicable",
"label": "No counter"
},
"agreed": {
"status": "complete",
"label": "Buyer accepted"
},
"settled": {
"status": "complete",
"label": "Balance committed"
},
"fulfilled": {
"status": "complete",
"label": "Quota delivered"
},
"resolved": {
"status": "current",
"label": "Metering active"
}
},
"delivery": {
"modality": "API credential",
"capacity": {
"status": "not-applicable",
"label": "No compute provisioner"
},
"fulfillment": {
"status": "complete",
"label": "Quota balance delivered"
},
"credential": {
"status": "complete",
"label": "API credential issued"
},
"service": {
"status": "current",
"label": "Metered quota active"
}
},
"resource": {
"service": "OpenAI-compatible inference",
"model": "Qwen3-235B-A22B-Instruct-2507",
"quota": "Text-generation quota",
"access": "New or existing API key",
"metering": "Metered balance"
}
}
Field notes:
resource.service— the named service the credential is valid for.resource.model— seller service metadata. The pinned API-credit resource schema exposes no canonicalmodelfield, so a model name here describes what the seller's endpoint serves; it is not an SCM wire field and not a Registry discovery filter.resource.quota/resource.metering— the prepaid balance and how the gateway consumes it; once spent, protected endpoints return402 insufficient_credits.
Where the shapes come from
Storefront reads return a listings array at GET /api/v1/listings. The
synchronized buyer quickstart and
seller quickstart show both queries
against real services, and
Custom-domain authoring
defines how a domain versions its offer_resource payload.