Truvera, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Truvera account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Security & Identity Tools
- Connects with a key
- 15 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Truvera is
Truvera is a platform that enables organizations and developers to issue, manage, and verify verifiable credentials and decentralized identities, making data fraud-proof and instantly verifiable.
You paste in a key from your own Truvera account. It is kept encrypted, and you can withdraw it from inside Truvera whenever you like.
One message in, the work done in Truvera.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Truvera. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Truvera account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Truvera
These are the ready-made tools your AI employee already has in Truvera. It is not limited to them, but it never has to be taught these.
- Create API KeyTool to create an API key. Use when you need to generate a new API key with optional alias and IP allowlist.
- Create WebhookTool to create a webhook endpoint. Use when you need Dock.io to push event notifications to your service.
- Delete API KeyTool to delete a specific API key. Use after confirming the API key's ID via listapikeys.
- Delete CredentialTool to delete a verifiable credential. Use after confirming the credential is no longer needed.
- Delete TagTool to delete a specific tag. Use when you have a tag ID and want to permanently remove it.
- Delete WebhookTool to delete a specific webhook. Use after confirming the webhook's ID via listwebhooks.
- Retrieve API KeyTool to retrieve details of an API key. Tries single-key endpoint first, then falls back to listing and filtering.
- Retrieve API KeysTool to list all API keys. Use when you need to retrieve all API keys for the authenticated account.
- Retrieve CredentialTool to retrieve a verifiable credential by its unique ID. If a password was used to persist it, include the same password to decrypt and return the full credential. Otherwise, onl
- Retrieve CredentialsTool to retrieve a list of credential metadata. Use when you need to collect credential details with optional pagination or filtering after authentication.
- Retrieve DID DocumentTool to retrieve a DID Document by its DID. Use after you have a valid DID to resolve and inspect its DID Document.
- Retrieve Revocation RegistriesTool to retrieve a list of revocation registries. Use when you need to list all registries created by the authenticated account with optional pagination and filtering.
- Retrieve WebhookTool to retrieve a specific webhook's details. Use after confirming you have a valid webhook ID.
- Retrieve WebhooksTool to list configured webhooks. Use when you need to retrieve all webhook endpoints configured for your account.
- Verify Credential or PresentationTool to verify a verifiable credential or presentation. Use after receiving a credential or presentation from an issuer.
You stay the boss of your Truvera account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Truvera account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Truvera is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Truvera and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Truvera
- Can an AI employee really work inside Truvera?
- Yes. It signs in to your own Truvera account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Truvera?
- No. Nothing moves and nothing is replaced. Your records stay in Truvera, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Truvera account?
- You paste in a key from your own Truvera account. It is kept encrypted, and you can withdraw it from inside Truvera whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Truvera?
- It has 15 ready-made tools in Truvera today, among them Create API Key, Create Webhook and Delete API Key. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Truvera and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Truvera and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Truvera?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Truvera is written down with what it did and when.