Build discovery into wallets, applications, AI agents and digital trust platforms.
The FIDES API provides programmatic access to data in the FIDES Ecosystem Explorer. It enables wallets, applications, platforms and AI agents to dynamically discover organizations, wallets, issuers, credential types, schemas and trust ecosystems.
Instead of hardcoding issuer endpoints, credential definitions, schemas or other ecosystem information, applications can use the FIDES API as a discovery layer for digital trust.
GET /api/public/catalogs — Discover configured catalogsThe FIDES API is designed around the principles of data ownership, federated publication and federated discovery.
Organizations remain in control of their own information and are responsible for publishing and maintaining it. Rather than creating a centralized registry owned by a single organization, FIDES enables ecosystem information to be published and discovered through an open, distributed architecture.
The architecture is intentionally designed to avoid vendor lock-in. Although the FIDES Ecosystem Explorer is one implementation of this discovery layer, the same open specifications can be implemented by other organizations, communities and ecosystem operators, enabling multiple interoperable discovery services.
Support for the TS11 Schema Discovery specification from the European Digital Identity Wallet Architecture and Reference Framework (ARF) is currently under development and will be added to the FIDES API in the coming weeks.
This will enable EUDI Wallet providers and relying parties to discover standardized credential types, attestation schemas and related metadata through a standardized interface.
Beyond TS11, the FIDES API provides broader discovery capabilities for organizations, issuers, wallets, trust ecosystems and other ecosystem metadata, making it easier to build interoperable digital trust solutions across multiple ecosystems worldwide.
Personal and business wallet providers can use the FIDES API to support wallet-initiated credential discovery and credential request flows.
Instead of hardcoding issuer endpoints, wallets can dynamically discover available credential types, trusted issuers and the information required to request credentials.
This becomes increasingly important as wallets need to support multiple issuers, credential types and ecosystems across countries and regions.
Business wallet providers that offer issuer functionality can discover and reuse existing credential types, schemas and metadata instead of creating new templates from scratch.
Reusing established credential models reduces fragmentation, improves interoperability and simplifies integration for wallets, issuers, verifiers and relying parties.
Business wallet providers that offer verifier functionality can dynamically discover credential types, schemas and metadata when configuring credential requests, including DCQL queries.
This enables applications to support new credential types and ecosystems without continuously updating hardcoded definitions.
Applications can discover organizations based on ecosystem roles, identifiers, supported standards, certifications, trust marks, countries or other metadata.
This enables users to find issuers, relying parties, wallet providers, identity verification providers, conformity assessment bodies, certification bodies, scheme owners and many other participants in the digital trust ecosystem.
Issuers, verifiers and relying parties can discover wallet providers based on supported credential formats, interoperability protocols, ecosystems, certifications and other capabilities.
This helps organizations determine which wallets they want to integrate with, recommend or support.
Applications can discover digital trust ecosystems, interoperability frameworks, trust schemes and their associated governance, participants and trust establishment mechanisms.
This helps organizations understand how ecosystems relate to one another and which standards, governance models and trust anchors they rely on.
Applications can search for organizations, products, certificates, conformity credentials, trust marks, trusted issuers and certification schemes.
This supports use cases where trust is established not only through identity credentials, but also through certifications, conformity assessments and qualified trust services.
The FIDES API continues to expand. Live endpoints are listed below with links to OpenAPI specs and Swagger UI.
GET /api/public/credentialtype/{id}GET /api/public/organization/{id}GET /api/public/issuer/{id}Filters: subjectType, tags, country, vcFormat, orgId, ...GET /api/public/wallet/{orgId}/{walletId}GET /api/public/rp/{id}Filters: readiness, status, country, sector, vcFormat, orgId, ...GET /api/public/usecase/{id}Filters: country, sector, vcFormat, interactionMode, tag, productionDeployment, ...
Add the catalogs as an "app"/connector in ChatGPT, Claude, and other
MCP clients. One Streamable HTTP endpoint exposes tools for every
configured catalog, plus generic search/fetch.
POST /api/mcp (Streamable HTTP)search_wallets, search_credential_types, search_organizations, search_issuers, search_relying_parties, search_use_cases (+ get_*)