Service catalog

Status

Current

Updated

2026-08-11

Scope

API Platform public catalog

The catalog lists every published service version. Whether a service is operated by the platform itself or by a third party, it looks exactly the same in the catalog.

List services

GET /v1/catalog/listings

Returns listings and a summary of their published versions, including the stable serviceCode, display name, and listed price of each version. The serviceCode remains the exact invocation identifier; it does not introduce a second Service product layer in the catalog.

The old /v1/catalog/services/** paths are compatibility endpoints. New integrations should use the Listing paths documented here.

Look at one service

GET /v1/catalog/listings/{serviceCode}

Look at an exact version

GET /v1/catalog/listings/{serviceCode}/versions/{version}
GET /v1/catalog/listings/{serviceCode}/versions/{version}/contract

The second returns that version's request and response schema, its content digest, and whether it carries an artifact contract.

Versions are exact — there is no latest

Every call must name a specific version, for example v1. The platform offers no implicit alias such as latest.

This is deliberate. A published version is immutable: it cannot be overwritten, and its version number cannot be reused. A request that works against v1 today is still the same contract at the same price tomorrow. If the provider wants to change something, they publish v2; v1 will not change behaviour behind your back.

Price

Each version in the catalog carries one gross price, denominated in points. What you see is the entire amount the call will spend. How that amount is divided between the platform and the provider is not published to callers, and does not affect what you pay.