How do I install the Igrantio Dcapi Android skill?

Run npx skillmds@latest add l3-igrant/igrantio-dcapi-android in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Igrantio Dcapi Android safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Igrantio Dcapi Android?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Igrantio Dcapi Android free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Igrantio Dcapi Android?

L3-iGrant (@l3-igrant) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Igrantio Dcapi Android by l3-igrant

Name: Igrantio Dcapi Android
Author: L3-iGrant

Igrantio Dcapi Android

Same-device and cross-device credential verification on Android via the W3C Digital Credentials API (browser invokes the wallet, no QR scan needed on same device) using OpenID4VP on the iGrant.io Organisation Wallet Suite. Presentation definition with responseMode dc_api (or signed with expectedOrigins), verification request v3 with requestByReference, navigator.credentials.get invocation from Chrome 141+, then verify vpTokenResponse and trust-list status. For EUDI Wallet (EUDIW) and European Business Wallet (EUBW) relying parties under eIDAS 2.0.

L3-iGrant a8b3969 3.2 KB Updated Sep 17, 2026

File contents

DC API verification on Android

When to use

Verify a credential in the browser on Android without a QR scan on the same device: the page calls the W3C Digital Credentials API and Chrome invokes the wallet. Cross-device still works (Chrome shows a QR; Bluetooth must be on for the proximity check).

Before you build: run the integrator intake in igrantio-ows-overview - environment, API key, tenancy, backend host, webhooks, frontend - one question at a time, a recommended default with each.

Prerequisites

Chrome 141+ (or 128+ with chrome://flags#web-identity-digital-credentials).
The credential in the user's Data Wallet.
Bluetooth on both devices for cross-device.

Workflow

Presentation definition - protocol OpenID4VP, format IETF SD-JWT, responseMode: "dc_api". For the signed variant (openid4vp-v1-signed) also set expectedOrigins to your page origin (replay protection).
Verification request (v3) - requestByReference: true with the presentationDefinitionId. The response's verificationHistory.dcApiRequest + dcApiProtocol are the browser payload.
Invoke the wallet - navigator.credentials.get({ digital: ... }) with the backend-provided request object. Use the ready-made dcApi.ts helpers in igrantio-verifier-frontend (supportsDcApi, invokeWallet, buildReceivePayload) - they handle the Chrome request formats and the plain-vs-signed response shapes.
Post the response back through your backend proxy on an allow-listed receive path; the SSE stream still delivers the final result.
Verify - read verification history (v3): decode vpTokenResponse, check verified, isVerifiedWithTrustList, and trustServiceProvider.

Adjust for your deployment

Choose plain dc_api vs signed per your threat model; signed requires expectedOrigins to exactly match the serving origin(s).
Feature-detect and fall back to the QR flow (igrantio-verifier-frontend) when the DC API is unavailable.
Credential format and DCQL query are yours to set - compose with any igrantio-dcql-* workflow skill.

Cross-references

igrantio-dcapi-ios - the iOS variant (ISO 18013-7 Annex C, always signed).
igrantio-verifier-frontend - dcApi.ts reference implementation.

Source of truth

This workflow mirrors https://docs.igrant.io/docs/openID4vc-send-verify-credentials-dcapi-android/. Before implementing, fetch that page; if it disagrees with this skill (browser versions, response modes, endpoints), the documentation wins - follow it and report the drift so the skill can be updated.

---name: igrantio-dcapi-androiddescription: Same-device and cross-device credential verification on Android via the W3C Digital Credentials API (browser invokes the wallet, no QR scan needed on same device) using OpenID4VP on the iGrant.io Organisation Wallet Suite. Presentation definition with responseMode dc_api (or signed with expectedOrigins), verification request v3 with requestByReference, navigator.credentials.get invocation from Chrome 141+, then verify vpTokenResponse and trust-list status. For EUDI Wallet (EUDIW) and European Business Wallet (EUBW) relying parties under eIDAS 2.0.license: Apache-2.0---# DC API verification on Android## When to useVerify a credential in the browser on Android without a QR scan on the samedevice: the page calls the W3C Digital Credentials API and Chrome invokesthe wallet. Cross-device still works (Chrome shows a QR; Bluetooth must beon for the proximity check).**Before you build**: run the integrator intake in `igrantio-ows-overview` - environment, API key, tenancy, backend host, webhooks, frontend - one question at a time, a recommended default with each.## Prerequisites- Chrome 141+ (or 128+ with `chrome://flags#web-identity-digital-credentials`).- The credential in the user's Data Wallet.- Bluetooth on both devices for cross-device.## Workflow1. **Presentation definition** - protocol OpenID4VP, format IETF SD-JWT, `responseMode: "dc_api"`. For the signed variant (`openid4vp-v1-signed`) also set `expectedOrigins` to your page origin (replay protection).2. **Verification request (v3)** - `requestByReference: true` with the `presentationDefinitionId`. The response's `verificationHistory.dcApiRequest` + `dcApiProtocol` are the browser payload.3. **Invoke the wallet** - `navigator.credentials.get({ digital: ... })` with the backend-provided request object. Use the ready-made `dcApi.ts` helpers in `igrantio-verifier-frontend` (`supportsDcApi`, `invokeWallet`, `buildReceivePayload`) - they handle the Chrome request formats and the plain-vs-signed response shapes.4. **Post the response back** through your backend proxy on an allow-listed receive path; the SSE stream still delivers the final result.5. **Verify** - read verification history (v3): decode `vpTokenResponse`, check `verified`, `isVerifiedWithTrustList`, and `trustServiceProvider`.## Adjust for your deployment- Choose plain `dc_api` vs signed per your threat model; signed requires `expectedOrigins` to exactly match the serving origin(s).- Feature-detect and fall back to the QR flow (`igrantio-verifier-frontend`) when the DC API is unavailable.- Credential format and DCQL query are yours to set - compose with any `igrantio-dcql-*` workflow skill.## Cross-references- `igrantio-dcapi-ios` - the iOS variant (ISO 18013-7 Annex C, always signed).- `igrantio-verifier-frontend` - `dcApi.ts` reference implementation.## Source of truthThis workflow mirrors<https://docs.igrant.io/docs/openID4vc-send-verify-credentials-dcapi-android/>.Before implementing, fetch that page; if it disagrees with this skill(browser versions, response modes, endpoints), the documentation wins -follow it and report the drift so the skill can be updated.

Frequently asked questions