# Igrantio Credential Schema Software Statement > Claim path pointer schema for the Software Statement credential, which attests a registered client application. The registry defines it in the dc+sd-jwt format with one mandatory claim, client_uri. Use this skill when you build a software statement credential definition for the iGrant.io OpenID4VC API. - Skill: `l3-igrant/igrantio-credential-schema-software-statement` (Agent Skill) - Install (CLI): `npx skillmds@latest add l3-igrant/igrantio-credential-schema-software-statement` - Raw SKILL.md: https://api.skillmd.com/api/skills/l3-igrant/igrantio-credential-schema-software-statement/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Integrations & APIs - License: Apache-2.0 - Author: L3-iGrant (https://skillmd.com/u/l3-igrant) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/l3-igrant/igrantio-credential-schema-software-statement --- # 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`. ## What the claims describe The registry defines one claim. - **`client_uri`** - mandatory. It holds the URI of the client application that the statement covers. The pointer does not set `limitDisclosure`. The credential has one claim, so selective disclosure adds nothing here. Do not add a claim path that the registry does not hold. A verifier that reads the registry does not expect it. ## Claim path pointer documents Each document below is the file that the registry holds. Copy it without a change. ### SD-JWT VC (`dc+sd-jwt`) | Fact | Value | | --- | --- | | Title | Software Statement | | Format | `dc+sd-jwt` | | `credentialType` | `SoftwareStatement` | | `vct` to send | `SoftwareStatement` | | `validationPath` | `$` | | Claim carrier in the request | `claims` | ```json { "claims": [ { "path": [ "client_uri" ], "mandatory": true } ] } ``` ## How to read a claim path pointer A claim path pointer selects one claim in the credential. Each item of the `claims` array holds these fields. - `path` is mandatory and holds at least one element. Read the elements from left to right. A string element selects an object key. An integer element selects one array index. A `null` element selects every element of an array, so `["nationalities", null]` covers each entry of the `nationalities` array. - `mandatory` says whether the issuer must supply a value for the claim. The issuer reads a missing `mandatory` field as `true`. - `limitDisclosure` says that the holder can disclose the claim on its own. Set it only inside the `claims` object of a `dc+sd-jwt` or `mso_mdoc` configuration. The `jwt_vc_json` format has no selective disclosure, so its documents leave the field out. A path that names a parent object, such as `["address"]`, and a path that names a child, such as `["address", "country"]`, can both appear. The parent pointer lets the holder disclose the full object. The child pointers let the holder disclose one field at a time. For `mso_mdoc`, the **first element of the path is the mDoc namespace**, every path holds at least two elements, and every path of one configuration uses the same first element. For `jwt_vc_json`, the first element of the path is always `credentialSubject`. ## Use with the iGrant.io API Create a credential definition with `POST /v2/config/digital-wallet/openid/sdjwt/credential-definition`. Put the `claims` array of the registry document into the configuration entry, and set the format fields that the table above gives. ```json { "label": "Issue Software Statement", "version": "version_01", "credentialDefinitions": [ { "credentialFormat": "dc+sd-jwt", "vct": "SoftwareStatement", "validationPath": "$", "claims": { "claims": [ { "path": [ "client_uri" ], "mandatory": true } ] } } ] } ``` Notes on the request. - `label` must hold at least 3 characters. The platform reserves the labels `Payment User Credential`, `Payment Card Credential`, `Payment Account Credential`, `PID Issuance` and `Photo ID Issuance`, so pick another label. - Always send `version` with the value `version_01`. The issuer falls back to an earlier version of the specification when you leave the field out, and you cannot change the value after you create the credential definition. - Add one entry of `credentialDefinitions[]` for each format that you want to publish. You can publish more than one format from one credential definition. - Keep the `id` that the response returns for each entry. The issue operation uses that value to match the claims to a configuration. - Add `supportRevocation`, `revocationMethod`, `expirationInDays`, `display` and the other entry fields as your use case needs them. Read `igrantio-api-issuer` for the full operation reference, the other request fields, and the issue operation that follows. ## Source is the registry The verifiable data registry is the source of truth. If this skill and the registry file disagree, **the registry wins**. Fetch the source before you rely on a claim path, and report the difference so this skill can be corrected. - Template directory: - Raw dc+sd-jwt document: - The metadata file sits next to each schema file, with the suffix `.schema.metadata.json`. It carries the title, the credential type, the doctype and the format flags. ## Cross-references - `igrantio-api-issuer` - the create credential definition and issue credential operations. - `igrantio-api-verifier` - the DCQL query that asks a holder for the credential. - `igrantio-ows-overview` - architecture and glossary.