Complete service listing
Present the product, provider, audience, documentation, support model and commercial conditions in one installable listing.
Commercial model
Partner marketplace
Register, review, publish and install external services with signed access and per-use accounting.
Overview
Register, review, publish and install external services with signed access and per-use accounting.
Features
What Partner marketplace can do
Review and release gates
Move each version through draft, review, approval and publication before it becomes available to customers.
Controlled installation
Create an explicit relationship between the customer account, the installed service and the partner that operates it.
Signed launch context
Open the external product with HMAC-protected account, user, installation and request identifiers.
Version and availability control
Update documentation, endpoints and commercial data without losing the status of existing installations.
Per-use accounting
Record executions, gross value, platform commission and partner net revenue as separate auditable amounts.
Partner settlement
Connect verified usage to the payment profile and payout lifecycle managed from the partner portal.
Publication lifecycle
A controlled route from listing to settlement
Every stage keeps product state, customer installation and commercial activity connected.
-
01 Register
Create the listing, endpoint, documentation, audience and commercial terms.
-
02 Review and publish
Validate the release and make the approved version discoverable.
-
03 Install and launch
Connect a customer account and send signed execution context to the provider.
-
04 Account and settle
Record verified usage and route partner revenue into the payout process.
Operational detail
How Partner marketplace works in practice
The marketplace is the governed distribution layer for partner products: it turns a provider endpoint into a reviewed, installable and commercially traceable service.
The listing is a product contract
Identity, screenshots, documentation, support ownership, endpoint and pricing explain what the customer installs and what the provider commits to operate.
Publication is versioned governance
Draft and review states allow changes to be checked before customers see them, while existing installations remain associated with a known service.
Launch creates a trust boundary
HMAC-protected context lets the provider validate account, user, installation and request identifiers without exposing reusable platform credentials in the browser.
Accounting follows execution
Usage events connect the installed service with gross value, commission and partner net revenue, creating the evidence required for reporting and settlement.
Frequently asked questions
Questions about Partner marketplace
Yes. Documentation, endpoints and commercial information can evolve through the managed service lifecycle and may require a new review before publication.
No. Installation creates a controlled relationship. The launch context and any additional API permissions must remain limited to the capabilities required by the product.
Future launches stop and the installation relationship is closed. Historical usage and accounting records remain available for traceability.
Commercial accounting is tied to the execution records defined by the service model, not merely to catalogue views or page visits.