Can Lyro issue a new credential in Truvera?

No. The toolkit covers verification and lifecycle - Verify Credential or Presentation, Retrieve Credential, Retrieve Revocation Registries, and Delete Credential - but exposes no issue action, so minting a credential stays in Truvera. Lyro handles the questions that come after issuance.

Does Lyro see the contents of a credential?

Only when it is entitled to. Retrieve Credential returns metadata by default; if a password was used to persist the credential, that same password must be supplied to decrypt and return the full credential, so a protected credential stays closed without it.

Is it safe to let Lyro create API keys?

Create API Key accepts an optional alias and an IP allowlist, so a key it provisions can be restricted to the addresses that should use it, and Delete API Key revokes it once the request is done. Retrieve API Keys lists what already exists before anything new is created.

How do we check a credential has not been revoked?

Retrieve Revocation Registries lists the registries created by the authenticated account, with pagination and filtering, and Verify Credential or Presentation performs the check itself. Lyro can run both so a stale credential is caught rather than accepted on its face.

Truvera MCP integration

Verifies submitted credentials and presentations, resolves DID documents, and provisions the API keys and webhooks around them.

Connect Truvera See all integrations

15actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Retrieve did document
Lyro retrieves a DID Document by its DID identifier. Support staff access verified credential information instantly.
Retrieve revocation registries
Lyro lists all revocation registries configured in the system. Teams check credential revocation status without manual queries.
Delete tag
Lyro removes a specific tag from the system. Administrators manage metadata cleanly without direct system access.

See all 15 actions

How businesses use Truvera + Lyro

Each card is one request a support team gets, and the Truvera actions Lyro runs to close it.

Verify a credential someone presents
Lyro verifies the credential or presentation as it is submitted, resolves the DID document behind the issuer, and retrieves the credential record so the answer rests on the cryptography rather than a screenshot.
Verify Credential Or PresentationRetrieve DID DocumentRetrieve Credential
Audit what has been issued and revoked
Lyro lists credential metadata with filtering and pagination, checks the revocation registries created by the account, and deletes a credential that is genuinely finished with.
Retrieve CredentialsRetrieve Revocation RegistriesDelete Credential
Provision and revoke API access
Lyro creates an API key with an alias and an IP allowlist scoped to who should use it, lists the keys already in place, and deletes the one that has outlived its purpose.
Create API KeyRetrieve API KeysDelete API Key
Confirm event notifications are actually wired up
Lyro registers a webhook endpoint, lists the endpoints already configured, and removes a stale one, so a missing event is diagnosed before anyone starts reading logs.
Create WebhookRetrieve WebhooksDelete Webhook

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Truvera actions it has and picks the ones a request needs.

01
Connect Truvera
Authorize the Truvera account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Truvera actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Truvera · Lyro

Everything else about Truvera

Setup, permissions, and the limits of what Lyro can do inside Truvera.

No. The toolkit covers verification and lifecycle - Verify Credential or Presentation, Retrieve Credential, Retrieve Revocation Registries, and Delete Credential - but exposes no issue action, so minting a credential stays in Truvera. Lyro handles the questions that come after issuance.

Every action available in Truvera

All 15 actions your agent can call on Truvera, straight from the live MCP connection.

Create API key
Create an API key.
Create webhook
Create a webhook endpoint.
Delete API key
Delete a specific API key.
Delete credential
Delete a verifiable credential.
Delete tag
Delete a specific tag.
Delete webhook
Delete a specific webhook.
Retrieve API key
Retrieve details of an API key.
Retrieve API keys
List all API keys.
Retrieve credential
Retrieve a verifiable credential by its unique ID.
Retrieve credentials
Retrieve a list of credential metadata.
Retrieve did document
Retrieve a DID Document by its DID.
Retrieve revocation registries
Retrieve a list of revocation registries.
Retrieve webhook
Retrieve a specific webhook's details.
Retrieve webhooks
List configured webhooks.
Verify credential or presentation
Verify a verifiable credential or presentation.