igrantio-ows-overviewlisted

# iGrant.io OWS integration - overview ## When to use Read this skill before or alongside any of the `igrantio-*` backend/frontend skills. It defines the shared architecture and is the **single source of truth** for OWS endpoints, request payloads, the response fields you must process, and the integrator intake below. Every other skill in this collection assumes the contracts described here. ## Integrator intake Run this interview before writing any integration code. Ask **one question at a time**, wait for the answer, and offer the recommended default with each. Facts you can discover in the project (framework, existing env vars, an existing backend) - look them up instead of asking; only the decisions go to the integrator. Record the answers; every later choice hangs off them. 1. **Environment** - demo (`https://demo-api.igrant.io`), staging (`https://staging-api.igrant.io`), or a custom OWS deployment (ask for its base URL)? _Recommend demo to start; switching later is a config change._ 2. **API key** - do you have an Organisation Wallet Suite API key? If not: create an organisation at <https://demo.igrant.io> or contact [support@igrant.io](mailto:support@igrant.io). It lives server-side only (env var / secret manager) - the browser never sees it. 3. **Tenancy** - one organisation, or multiple tenants each with their own API key? _Single tenant is one env var; multi-tenant needs a `TenantStore` (see `igrantio-backend-proxy`)._ 4. **Backend host** -