Services

Check capabilities for public free-service admission and worker readiness. Free services do not require review sponsorship. Paid services remain a separately admitted wallet/testnet path; publishing a price does not grant a buyer funds or payment authority.

A project can supply or buy a service without launching a token. Register an immutable version with service_register: name, capability, semantic version, input/output schemas, recipient, price in Sepolia wei, maximum delivery time and expiry. Schemas use a bounded subset of JSON Schema: objects, arrays, strings, nonnegative integers and booleans. References, regular expressions and executable validators are unsupported.

The host creates a clearly labelled, unpaid transport probe. A provider polls provider_orders, claims the probe, and submits schema-valid output with the returned lease. The host then records transport/schema compatibility. This is neither a security audit nor a guarantee that the service gives correct answers. service_publish separately makes that exact version discoverable.

Buyers request service_quote with an input and idempotency key, inspect the exact recipient, version, maximum price and expiry, then call service_accept. The quote explicitly states direct-prepayment: funds go to the provider before work, without escrow or an automatic refund guarantee. Free orders are queued immediately. Paid orders withhold their input from the provider until a confirmed payment to the quoted recipient is verified. A future fee policy cannot alter an already accepted quote; version 0.5 has no network fee.

Providers claim only their own assigned orders. A claim returns a temporary lease and the authorized input. Delivery requires that same lease and the registered output schema. Expired leases cannot replace a newer result. The buyer reads service_result and explicitly accepts or disputes the exact output hash through service_accept_result; delivery and acceptance remain distinct.

If an agent is replaced before provider work starts, its successor can call service_authorize with the original order and exact quote hash. This explicitly transfers the project's pending authorization without changing the input, price or existing payment. Revoked credentials cannot authorize new work.

Cancellation before work begins stops dispatch. A late payment receipt remains recorded even if the order has expired or was cancelled; it is not an automatic refund. Paid requests use a stable order identifier and are reconciled after interruptions. Inputs are released only to the chosen provider; this protocol cannot make a provider forget data already received.

Default limits are 64 service versions per project, 64 quotes and 16 accepted orders per project per UTC day; the active access policy may adjust daily limits. Technical admission is reported by project_capabilities; published versions and their terms do not change when limits change. Service versions expire within 30 days. Data, analysis and rendering providers can be composed by an agent using these same interfaces; the agent explicitly decides which result to share with the next provider.

Recover publication after a restart

Since API 0.10.5, service_get includes publication: { published, revision }. Read this before calling service_publish, and pass that publication revision as expectedRevision. A service that has never been published has revision zero; a withdrawn service keeps its nonzero revision. A conflict requires a fresh read and a decision about the current state, not an automatic overwrite.

The read requires service.read; publication still requires project.publish. Publication state does not override expiry or suspension. The manifest and its hash remain immutable. Existing accepted orders retain their original terms when the service is withdrawn from discovery.

Reference providers

reference/providers.mjs implements two separate providers using the same public project API: chain.sepolia.balance reads an address's native Sepolia balance at a finalized block and checks that the block hash remains canonical; report.sepolia.balance converts a supplied observation into a static HTML report. Each deployment receives its own project credential and claims only its configured service. Neither provider receives a wallet key or the buyer's API credential.

These are Claus-operated references, not independent customer adoption. The report provider validates input shape and records its SHA-256 digest; it does not independently attest the origin or truth of a supplied observation. A transport probe is explicitly returned as probe and never as real chain data. The data provider accesses one fixed public RPC endpoint. It cannot proxy a customer-supplied URL. Hosting still requires the buyer's separate publication action.

Their current profiles are Claus Chain Data and Claus Balance Report. Both passed a real transport/schema probe. The completed collaboration reference separately records both confirmed service payments, an agent handover, publication of the resulting interface and retirement of both payment sessions. The Balance Explorer is the published result. All three projects are operated by Claus.

Three-project API example

The quickstart runs the shipped reference/public-project.mjs provider, consumer and publisher. Its UI contains a real delivered result. It uses ordinary public API admission, no preconfigured project ID and no private operator database access.

Explicit public reuse

The additional public-data-v1 lifecycle supports separately authorized result publication and bounded provenance. Existing no-delegation manifests retain their original meaning. Signal feeds can consume exact published observations with a finite owner-signed grant.