Module Registration
Credo uses a modular architecture where functionality is provided through modules. Modules are registered when creating the agent.Basic Module Registration
Default Modules
These APIs are always available on the agent without explicit module registration:dids
DID operations (resolve, create, update, deactivate).DidsApi
w3cCredentials
W3C Verifiable Credentials 1.1 operations.W3cCredentialsApi
w3cV2Credentials
W3C Verifiable Credentials 2.0 operations.W3cV2CredentialsApi
sdJwtVc
SD-JWT Verifiable Credentials operations.SdJwtVcApi
mdoc
Mobile document (mdoc/ISO 18013-5) operations.MdocApi
x509
X.509 certificate operations.X509Api
kms
Key Management System operations.KeyManagementApi
genericRecords
Generic storage for custom records.GenericRecordsApi
Optional Modules
These modules must be explicitly registered and have special top-level access:didcomm
DIDComm protocol support (connections, credentials, proofs). Registered viaDidCommModule.
DidCommApi | undefined
openid4vc
OpenID for Verifiable Credentials support. Registered viaOpenId4VcModule.
OpenId4VcApi | undefined
Custom Modules
Custom modules are accessed via theagent.modules property: