Provider
Ownership, identity, support, security contact, status, and approved namespaces.
Catalog & Access Architecture
Pool API Marketplace
A reference architecture for cataloging models, prompts, compute, nodes, assets, domains, databases, CMS connectors, endpoints, and other pooled digital services.
Discovery is not execution
Separate the catalog from the gateway
The marketplace describes products, providers, versions, capabilities, regions, plans, trust evidence, and lifecycle. The gateway authenticates, routes, limits, meters, and records runtime traffic. A listing can evolve without putting a catalog database on the hot path.
Catalog entities
A marketplace is a versioned contract directory
Product
Stable identifier, summary, category, audience, capability model, and provider relationship.
Version
Specification, endpoints, regions, release notes, compatibility, deprecation, and sunset.
Plan
Scopes, quotas, concurrency, credit units, support, access conditions, and policy version.
Access grant
Consumer, application, product version, scopes, terms, approval, credentials, and state.
Usage record
Observed operation, units, consumer, provider, trace, policy, conversion, and reconciliation.
Pool-aware categories
Catalog the differences that matter
AI models & prompts
Modalities, tools, context class, output controls, prompt compatibility, evaluation evidence, data policy, and latency class.
Cloud & compute
CPU, RAM, GPU, accelerator memory, storage, network, architecture, container runtime, region, and isolation class.
Assets & settlement
Asset, network, issuer or contract, custody model, deposit and withdrawal status, finality, approvals, and reconciliation.
Domains & digital property
Domain name, registrar context, ownership evidence, transfer state, renewal, restrictions, and listing lifecycle.
Database & CMS connectors
Protocol, schema capability, read/write scope, data region, authentication, rate policy, freshness, and retention.
Nodes, bots & endpoints
Admission, capability, health, readiness, event types, signing, retry, region, and service-level evidence.
Provider workflow
Draft → verify → review → publish → operate → deprecate
Automated checks validate schemas, URLs, examples, endpoint ownership, and secret exposure. Human review evaluates claims and high-risk categories. Published listings point to immutable catalog revisions. Suspension and retirement preserve history instead of deleting evidence.
Verify ownership
Confirm the provider namespace, documentation domain, endpoint control, and security contact.
Validate contracts
Parse machine-readable specs, test examples, and reject embedded credentials or unsafe references.
Publish evidence
Label exactly what was reviewed, when, by whom, and when the evidence expires.
Trust without invented badges
“Verified” is useful only when its scope is visible. Ownership verification, specification validation, identity review, security assessment, uptime measurement, and regulatory status are different claims. Publish the evidence type, source, date, and limitations. Do not create testimonials, customer counts, ratings, partner logos, or certifications without support.
Machine-readable discovery
Agents and developer tools can search the catalog by capability, policy, region, format, authentication, lifecycle, and plan. Return only products and fields allowed for that consumer. A machine client should receive a short-lived route or tool reference, not a permanent marketplace credential embedded in prompt text.
Lifecycle and deprecation
Deprecation announces that a version remains available but should not receive new integrations. Sunset states a concrete stop date. Retirement blocks traffic while keeping documentation and history. Notify every affected access grant and expose dates through the catalog API and gateway headers.