igrantio-credential-schema-software-statementlisted

# Software Statement - credential schema ## When to use Use this skill when you issue or verify a **Software Statement** credential. A software statement attests a registered client application. The registry gives the title `Software Statement` and the credential type `SoftwareStatement`. It gives no namespace for this credential. The schema supports one format: SD-JWT VC (`dc+sd-jwt`). The registry keeps this schema under `credentialSchemas/claimPathPointer/softwareStatement`. Version **2025.7.1** is the latest version directory, and this skill uses it. The registry publishes the schema in one format: `dc+sd-jwt`. ## Prerequisites - An **iGrant.io Organisation Wallet Suite (OWS) API key**. Get it from [support@igrant.io](mailto:support@igrant.io). Keep it on the server, in an environment variable or a secret manager. The browser never sees it. - The **OWS environment** the key belongs to. The default is **demo** (`https://demo-api.igrant.io`). Use **staging** (`https://staging-api.igrant.io`) only when the integrator asks for it. A key works only in its own environment. ## Ask the integrator first Ask one question at a time. Wait for the answer. Give the recommended default with each question. Look up facts in the project (framework, environment variables, an existing backend) instead of asking for them. Record the answers before you write code. 1. **Environment** - demo or staging? _Default demo (`https://demo-api.igrant.io`); a switch later is a configur