Live execution key X-API-Key
Browse the catalog & schemas anonymously. Paste a demo API key to run a real execution against the live server. The key stays in this tab's memory only — it is never stored or sent anywhere but demo.honua.io.
Process catalog GET /ogc/processes/processes
Live from demo.honua.io. Community processes execute on the open tier; Pro (analytics.*) require a Pro entitlement.
Process detail
Select a process to load its live input schema from /ogc/processes/processes/{id}.
Execution
A real POST .../execution is sent to the live server. The exact server response — plan validation, job acceptance, result, or auth/entitlement gate — is shown verbatim below.
No execution yet.
How execution is gated
The OGC API Processes catalog and schemas are public and load anonymously here, along with the live layer registry (GET /odata/Layers) used to resolve a friendly layer name to its integer id. Execution (POST /execution) requires a server X-API-Key; without one a live submit returns an honest 401 Authentication required. With a valid key the request reaches the server's catalog plan validation: a correct integer layerId and parameters produce a plan the server accepts (a wrong layer or missing param is rejected live with a 400, proving the validation is real). On the public demo, durable async job storage is not provisioned, so an accepted plan terminates at 503 — job storage unavailable rather than running to completion; a fully-provisioned deployment continues to a job and GeoJSON result. The Pro analytics.* processes additionally require a Pro entitlement (HTTP 402) even with a key. This demo surfaces every live response rather than faking a result.