How it all fits together
Restormel has two API surfaces and two key types. Use this page when you need to decide which URL/key belongs to which task.
| Surface | Base URL | Auth | Used for |
|---|---|---|---|
| Dashboard API (runtime) | https://restormel.dev/keys/dashboard/api | rk_... | Resolve, policy evaluate, routes/steps, simulate, lifecycle, public catalog feed, and project model index (GET/POST/PUT …/projects/{projectId}/models, binding CRUD). See Cloud API. |
| Gateway API (control-plane) | https://restormel-keys-gateway-main-bc13eba.zuplo.app/api | zpka_... | Project/key CRUD and gateway-level management (Zuplo Developer Portal / consumer key). |
Where to start
- If you are wiring app runtime decisions, start at Cloud API and use
rk_.... For per-project allowlists (picker merge, ingestion) vs the global catalog, see the project model index matrix on that page and the repo integrator notekeys-catalog-sync.md. - If you need control-plane API operations in the portal, use
zpka_.... - Dashboard UI setup is always at Dashboard.