Becoming a provider
- Status
- Current
- Updated
- 2026-09-13
- Scope
- API Platform provider onboarding
There is exactly one requirement for publishing your service on ZaunEkko: having a ZaunEkko Account.
Three concepts
Once these three layers make sense, the process is straightforward:
| Concept | What it is | Analogy |
|---|---|---|
| Provider | Your identity as a provider; holds members and the settlement account | The shop |
| Connection | Your service address and credentials — how the platform reaches you | The delivery route |
| Listing | The capability you sell, with its request and response contract and its price | The item on the shelf |
The provider sits above the other two. Connections and listings both hang off a provider, and neither can be published without it.
The process
You create and submit; verification and approval are not on your side. Each of the three objects goes through one round of "you submit, then you wait", and they must be done in order — the next one cannot be created until the previous one has passed.
- Create a provider — identifier, display name, description — then submit it and wait for the outcome.
- Create a connection — service address and calling credentials — then submit it. Once it passes, the connection becomes ready.
- Create a listing — request and response contract, descriptive copy — then submit it. Only after it is approved and published does it appear in the public catalog.
Every step shows its current state on the corresponding page. You do not need to ask for progress.
Publishing produces an immutable exact version. It cannot be modified or overwritten; to change something you publish a new version, and the old one keeps serving existing callers under its original contract.
What your service must satisfy
- A publicly reachable HTTPS address. The platform will not call private ranges, loopback addresses, or cloud metadata addresses, and does not follow redirects.
- The platform's calling protocol, which has two entry points: execution and reconciliation. Reconciliation is used to establish what actually happened to a call whose outcome is unknown — it is the precondition for the platform never blindly resending, and it is required.
- Idempotency on your side. The platform reconciles using a stable identifier, and you need to recognise the same call when it does.
Protocol details are in Implementing your service.
Earnings
Publishing a listing fixes both the gross price and the split. Once a call happens and settles successfully, your share is credited to the settlement account.
You can view your earnings summary and line items at any time, and reassign the receiving account yourself — reassignment applies only to later calls, and already-settled earnings are not moved.
You see only your own share: not the platform's cut, and not the caller's identity.
What to know before you start
- Creating and submitting needs no extra authorisation — an account is enough.
- The technical half is yours to settle: once a connection is submitted you can run the contract conformance check yourself, see every item, and re-run it as often as you like, without waiting on anyone.
- Whether a listing belongs in the catalog is a business judgement and gets a human review, with no committed turnaround time. It never passes automatically, and a fully green check does not skip it.
If you plan to integrate, start with Implementing your service; for current gaps see Current limitations.