agentsclimarketplace

Igrantio dcapi ios

Skill L3-iGrant/skills/workflows/igrantio-dcapi-ios

Agent Skills for EUDI Wallet and European Business Wallet integrations: credential issuance (OpenID4VCI), verification (OpenID4VP + DCQL), DC API and consent management on the iGrant.io Organisation Wallet Suite

Install
npx -y skills add L3-iGrant/skills --skill igrantio-dcapi-ios

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Same-device and cross-device credential verification on iOS/iPadOS via the W3C Digital Credentials API using ISO 18013-7 Annex C request/response with ISO/IEC 18013-5 mdoc/mDL credentials on the iGrant.io Organisation Wallet Suite. On iOS the DC API runs over Annex C only and the request must be signed (expectedOrigins required). Presentation definition, verification request v3 with requestByReference, wallet invocation from the browser, then verify vpTokenResponse and trust-list status. For EUDI Wallet (EUDIW) relying parties under eIDAS 2.0.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.5 KB, as published. Nobody here has run it

DC API verification on iOS

When to use

Verify a credential in the browser with the wallet on an iPhone/iPad. Key platform difference vs Android: on iOS the Digital Credentials API runs over ISO 18013-7 Annex C only, with ISO/IEC 18013-5 mdoc/mDL credentials, and the request is always signed - expectedOrigins is mandatory.

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

  • A DC-API-capable browser (Chrome 141+, or flag-enabled earlier builds).
  • The mdoc credential (e.g. age verification) in the user's Data Wallet.
  • Bluetooth on both devices for cross-device (QR) flows.

Workflow

  1. Presentation definition - protocol ISO 18013-7 Annex C, format ISO/IEC 18013-5 mdoc/mDL, response mode DC API signed, with expectedOrigins set to your page origin (replay protection).
  2. Verification request (v3) - requestByReference: true with the presentationDefinitionId; read verificationHistory.dcApiRequest / dcApiProtocol from the response.
  3. Invoke the wallet from the page. Use dcApi.ts from igrantio-verifier-frontend - getPlatformRequest picks the Safari request variant, invokeWallet calls the API, buildReceivePayload returns the { response: <JWE> } shape a signed exchange needs.
  4. Post the response back via your backend proxy; SSE delivers the verified result as usual.
  5. Verify - read verification history (v3): decode vpTokenResponse, check verified, isVerifiedWithTrustList, trustServiceProvider.

Adjust for your deployment

  • expectedOrigins must list every origin serving the page (www and bare domain are different origins).
  • Detect the platform and route Android to igrantio-dcapi-android (OpenID4VP / SD-JWT) and iOS here (Annex C / mdoc); keep the QR flow as the universal fallback.
  • Compose the credential query with igrantio-dcql-* workflow skills where DCQL applies.

Cross-references

  • igrantio-dcapi-android - the Android variant (OpenID4VP, plain or signed).
  • igrantio-eu-age-verification - a natural mdoc use case for this flow.
  • igrantio-verifier-frontend - dcApi.ts reference implementation.

Source of truth

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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.