MARKET INFRASTRUCTURE · EXECUTIVE POINT OF VIEW

The Market Beneath the Marketplace

Circle can evolve agent commerce into a market for the smallest economically meaningful units of data, information, knowledge, and capability—each packaged as an offer, governed by LOAC, purchased and settled through x402.

Granular
Markets
Circle
discovery + USDC
LOAC
rights + trust
x402
machine checkout
3 live offersone knowledge asset
3 primitivesdiscovery, rights, settlement
8 examplesdata through derived knowledge
6 layersmarket infrastructure
THE VISION

From Service Catalog to Asset Economy

Circle Agent Marketplace can become more than a directory of paid agent services. Its consequential form is a market in granular digital commodities: bounded units of data, information, knowledge, and executable capability that agents can discover, purchase, exercise, and audit independently.

The listing unit becomes a capability offer joining a resource to its seller, price, usage unit, license, access policy, delivery route, and provenance.

Circlecreates the discovery and settlement surface
LOACcreates the semantic contract for identity, rights, and delivery
x402creates the machine-native checkout moment
WHY IT MATTERS

The Executive and Investor Thesis

Granularity is not a packaging detail. It changes market size, transaction velocity, pricing power, and the defensibility of the trust layer.

01

A larger addressable market

The marketplace expands from whole-agent services to every bounded unit of data, information, knowledge, and executable capability that can carry an offer.

THE STRATEGIC SHIFTFrom selling access to agents
to clearing rights in digital assets.

Payment Is Not the Whole Contract

Payment

Was the requested value transfer authorized and settled?

Identity

Which principal, agent, seller, or buyer does the identifier denote?

Authority

Which agent may act for which principal, for what bounded purpose?

Rights

What may the buyer do after payment, and under which constraints?

Delivery

Which route supplies the resource or executes the capability?

Proof

Which evidence connects offer, policy, payment, delivery, and result?

Six-layer Architecture

Circle and x402 occupy crucial layers, while Linked Data joins the full commercial and trust envelope.

1. Discovery and Qualification

Circle's marketplace role: searchable service metadata, input/output schemas, health signals, ranking, and compliance-oriented seller admission.

2. Offer and Rights Description

RDF joins each commodity to its seller, price, usage unit, license, access policy, delivery route, and provenance.

3. Identity and Delegation

WebID or another verifiable identifier distinguishes principal, agent, seller, buyer, and the authority under which each acts.

4. Payment and Settlement

x402 communicates the price challenge and produces payment evidence, while stablecoin settlement provides machine-speed value transfer.

5. Authorization and Entitlement

Policy evaluation determines whether the authenticated party may exercise the purchased right under purpose, time, territory, quantity, and delegation constraints.

6. Storage, Delivery, and Audit

DAV, SPARQL, API, object storage, or another route delivers the resource and emits a provenance-bearing receipt.

What Becomes Tradable

CommodityBoundaryIllustrative unitOffer
Dataset slicerow, record, partition, or time windowper row, MB, or snapshotOffer
Named-graph accessRDF graph or graph patternper query, triple, or intervalOffer
File accessdocument, model artifact, archive, or media fileper download or time windowOffer
Query executionSPARQL, SQL, GraphQL, or inference requestper execution or compute unitOffer
Agent skillbounded prompt, workflow, tool contract, or executable skillper invocation or license termOffer
Attestationidentity, compliance, quality, or provenance assertionper verificationOffer
Storage operationread, write, append, transform, or publishper operation or byteOffer
Derived answeranalysis, summary, recommendation, or scored resultper answer or confidence tierOffer

Dataset slice

Boundary
row, record, partition, or time window
Pricing unit
per row, MB, or snapshot

Named-graph access

Boundary
RDF graph or graph pattern
Pricing unit
per query, triple, or interval

File access

Boundary
document, model artifact, archive, or media file
Pricing unit
per download or time window

Query execution

Boundary
SPARQL, SQL, GraphQL, or inference request
Pricing unit
per execution or compute unit

Agent skill

Boundary
bounded prompt, workflow, tool contract, or executable skill
Pricing unit
per invocation or license term

Attestation

Boundary
identity, compliance, quality, or provenance assertion
Pricing unit
per verification

Storage operation

Boundary
read, write, append, transform, or publish
Pricing unit
per operation or byte

Derived answer

Boundary
analysis, summary, recommendation, or scored result
Pricing unit
per answer or confidence tier
LIVE MARKET PROOF

One Knowledge Asset. Three Purchasable Rights.

URI Burner's live catalog shows the granular marketplace in operation: graph access, HTML presentation, and RDF-Turtle delivery are separate offers with their own licenses—even when two rights point to the same underlying Turtle URL.

THE MARKET DESIGN SIGNALValue attaches to the right being cleared,
not only to the bytes being delivered.

Verified against named graph urn:shop:offering:info. Use the offer recipes in the SPARQL Workbench to inspect the live records.

THE MARKET FLYWHEEL

One Resource. One Offer. One Verifiable Economic Event.

01PackageBound a data, information, knowledge, or capability unit
→
02DiscoverRank the offer through Circle's marketplace surface
→
03SettleComplete machine checkout through x402 and USDC
→
04EntitleEvaluate LOAC identity, delegation, policy, and rights
→
05DeliverSupply the resource and emit a provenance receipt

A buyer agent discovers a bounded offer, resolves the resource and policy IRIs, presents its identity and delegated authority, receives an x402 challenge, authorizes settlement, and returns with payment evidence. The seller authenticates the requester, evaluates the resulting entitlement, delivers through the declared route, and emits a provenance receipt.

Investor implication: finer product units create more transaction moments, while provenance and fulfillment history improve the trust surface that helps future transactions clear.

Design Implications

Wallets are not complete identities

A payment address should connect to, not replace, the principal and delegated-agent identity graph.

Settlement is not universal authorization

The entitlement policy still governs purpose, quantity, time, territory, retention, and redistribution.

Offers should be dereferenceable

Agents should inspect the resource boundary, price, policy, schema, and delivery route before buying.

Reputation should be granular

Health, quality, and dispute signals should attach to individual offers and resources as well as sellers.

How to Publish a Granular Digital Commodity

2. Describe the offer

Attach seller, price, currency, usage unit, validity period, delivery route, and machine-readable input/output schema.

3. Bind identity and delegation

Identify the principal, buyer agent, seller agent, and any acted-on-behalf-of relationship without treating a wallet address as the whole identity.

4. Express rights and constraints

State permissions, prohibitions, duties, purpose, quantity, territory, retention, and redistribution constraints in a machine-readable policy.

5. Issue and settle the x402 challenge

Return the payment requirement, let the buyer agent authorize settlement, and retain payment evidence without equating payment with authorization.

6. Evaluate entitlement and deliver

Authenticate the requesting party, evaluate the purchased right, deliver through the declared route, and enforce any continuing constraints.

7. Emit a provenance receipt

Link the offer, policy, resource, parties, delegated authority, payment evidence, delivery result, and timestamps in a queryable record.

Frequently Asked Questions

Answer: It contributes an HTTP-native price challenge and payment-settlement handshake. It does not by itself define identity, delegation, license terms, or resource authorization.

Answer: Circle contributes a discovery and commerce surface around x402 services, including structured service metadata, machine-readable schemas, seller admission, service health, and stablecoin settlement infrastructure.

Answer: RDF gives every offer, party, resource, policy, entitlement, and receipt a globally identifiable node whose relationships can be queried and independently extended.

Answer: Yes. A file, graph, query result, skill, prompt, model artifact, or individual storage operation can be offered independently when its identity, rights, price, and delivery are explicit.

Answer: No. Payment evidence identifies a payment authorization context, not necessarily the legal or organizational principal, the operating agent, or the authority delegated to that agent.

Core Technical Glossary

HTTP 402

Definition: The HTTP Payment Required status used by x402 to signal that a resource requires payment and to carry a machine-readable challenge.

x402

Definition: A protocol for machine-readable payment requests and settlement around HTTP resources.

USDC

Definition: A regulated dollar-denominated stablecoin used as a settlement asset in Circle's agent-commerce stack.

WebID

Definition: A Web-addressable identifier that denotes an agent or person and can connect identity claims to a profile graph.

Authorization

Definition: A decision that an authenticated party may perform a specified action on a resource under stated conditions.

Delegation

Definition: A relationship in which an agent is authorized to act on behalf of a principal for a bounded purpose.

Entitlement

Definition: A machine-verifiable right obtained under an offer and policy, often after payment but not reducible to payment.

ODRL

Definition: The Open Digital Rights Language, an RDF vocabulary for expressing permissions, prohibitions, duties, and constraints.

Provenance

Definition: Information about the origin, custody, transformation, responsibility, and evidence associated with an entity or activity.

Named graph

Definition: An RDF graph identified by an IRI so that its statements can be queried, governed, and licensed as a distinct resource.

Dereferenceable offer

Definition: An offer identified by an IRI that resolves to a machine-readable description of the thing sold and the terms governing it.

Knowledge Graph Explorer

ClassesPropertiesInstances

Graph data is derived from the companion RDF. Click the graph to activate zoom; click outside to release it. Drag nodes to pin and double-click to unpin.

Explore the Knowledge Graph Using SPARQL

Use the collection recipes or query the three live offers in urn:shop:offering:info. SELECT queries use text/x-html+tr; DESCRIBE uses text/x-html-nice-turtle.

SELECT format: text/x-html+tr. DESCRIBE format: text/x-html-nice-turtle.

Sources and Evidence

The factual baseline combines three linked editorial and product sources with live offer records from URI Burner. The broader granular-marketplace architecture is an explicitly labeled synthesis and inference.