Use Truvera from Claude
Add the Truvera connection to a Space that runs Claude, then use it from every channel in that Space.
Create a Truvera connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Truvera connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Truvera connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Truvera lets a team issue, verify, and revoke digital credentials and identities instead of relying on paper documents or manual checks. With a Truvera connection in a type.com Space, the agent can set up a new API key, register a webhook for credential events, or remove old credentials and tags, keeping the identity workflow current without a developer logging into the console each time.
Connect Truvera once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Have the agent generate a Truvera API key with an alias and IP restriction, so a new integration gets scoped access without manual console clicks.
Create a new Truvera API key for our verification service, limited to our office IP range.
Register a webhook so your team learns the moment a credential is issued, verified, or revoked, instead of checking the dashboard.
Create a Truvera webhook that posts to our events endpoint whenever a credential is revoked.
Remove credentials or tags that are no longer valid, keeping the Truvera account clean as your identity program grows.
Delete the Truvera credential issued to the pilot batch from March, it has expired.
Generates a new Truvera API key, optionally with an alias and an IP allowlist for scoped access.
Sets up a webhook endpoint so Truvera can push event notifications to your own service.
Removes a specific Truvera API key once you have confirmed its ID.
Deletes a verifiable credential that is no longer needed.
Permanently removes a specific tag once you have its ID.
Truvera provides REST APIs for decentralized identity and verifiable credentials. Integrations can create and manage DIDs, issue, verify, revoke, and manage credentials, configure schemas/templates, use webhooks or polling, and authenticate with API keys against production or testnet endpoints.
Yes. Once a Truvera connection is shared with a Space, the agent can create API keys, set up webhooks, or delete old credentials and tags right from a thread.
Truvera uses an API key. An admin adds it once while creating the connection, then decides which Spaces can use it, so the key stays out of prompts and threads.
Yes. You can turn a recurring task, such as checking for expired credentials each week, into a type.com automation that reports what it found to a channel.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect Borneo to Claude in type.com to start cloud data scans, check scan status, and manage discovered recipients from a shared thread.
Connect Digicert to Claude in type.com to tag certificates, check permissions, and create API keys or IP rules from a shared security thread.
Connect Bitwarden to Claude in type.com to manage organization members, groups, and subscription details without leaving a shared thread.
Connect Cloudflare to Claude in type.com to add DNS records, manage WAF lists, and create zones from a shared infrastructure thread.