Issues credentials over OpenID4VC and DIDComm, raises verification requests, maintains credential templates, and manages DIDComm connections.
69actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro sends a custom DIDComm message to establish verifiable communication. Agents conduct identity verification exchanges securely.
Ayro creates a self-signed X.509 certificate for project authentication. Agents provision security credentials without IT involvement.
Ayro creates a DIDComm connection invitation to establish peer relationships. Agents initiate verifiable identity connections instantly.
Each card is one request a support team gets, and the Paradym actions Ayro runs to close it.
Ayro issues an SD-JWT VC directly, or raises an offer the holder claims over OpenID4VC or DIDComm, so a credential reaches the person while the request is still open.
Ayro defines what the presentation has to contain, raises the verification request against it, and reads the session back to report whether the proof actually satisfied it.
Ayro lists the templates in the project, updates the one whose claims have changed, and archives a format that is no longer issued so nobody builds on it by accident.
Ayro creates the invitation a holder scans, lists the connections already established, and sends a message over one when a credential exchange needs a follow-up.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Paradym actions it has and picks the ones a request needs.
Authorize the Paradym account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Paradym actions that close it and chains as many as the request needs.
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 freeParadym · Ayro
What can you do in Paradym without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Paradym.
Three, each with its own template actions: SD-JWT VC through Create SD-JWT VC Credential Template, AnonCreds through Create AnonCreds Credential Template, and mDoc through Get mDoc Credential Template and Update mDoc Credential Template. Each format also has a JSON Schema action, so Ayro can check the shape a template expects before writing one.
All 69 actions your agent can call on Paradym, straight from the live MCP connection.
Activate a certificate for use in a project.
Archive an AnonCreds credential template in a project.
Archive an mDoc credential template.
Archive a presentation template in a project.
Archive an SD-JWT VC credential template in a project.
Create a new AnonCreds credential template.
Create a new self-signed X.509 certificate for a project.
Create a DIDComm connection invitation.
Create a DIDComm credential issuance offer.
Create an OpenID4VC credential offer.
Create an OpenID4VC verification request.
Create a new presentation template.
Create a new webhook for a project.
Create a new SD-JWT VC credential template with selective disclosure capabilities.
Create a new trusted entity for a project.
Deactivate a certificate in a project.
Delete a DIDComm connection from a project.
Delete a DIDComm invitation from a project.
Delete a trusted entity from a project.
Delete a webhook endpoint from a project.
Retrieve a specific AnonCreds credential template by ID.
Retrieve the JSON schema for an AnonCreds credential template.
Retrieve a specific DIDComm connection by ID.
Retrieve a list of DIDComm connections for a project.
Retrieve a specific DIDComm invitation by ID.
Retrieve a specific DIDComm issuance session by ID.
Retrieve a list of Decentralized Identifiers (DIDs) for a specific project.
Retrieve a specific mDoc credential template by ID.
Retrieve the JSON schema for an mDoc credential template.
Retrieve a specific OpenID4VC issuance session by ID.
Same connection, same setup. Pick the next one your team already uses.
Apiflash is a website screenshot API for programmatically capturing web pages.
Explains why a job failed, triggers a pipeline rerun, manages contexts and environment variables, and reports flaky tests and credit spend.
Verifies credentials and presentations, resolves DID documents, reports what an account holds, and manages API keys, webhooks, and tags.
Checks domain availability and ownership, spins up free subdomains, manages VPS SSH keys, and reports on DNS, orders, and renewals.
Searches cached URLs, fetches prerendered snapshots, recaches pages after a deploy, schedules wildcard cache clears, and tracks the job.
Creates uptime, page speed and heartbeat checks, reports alert and downtime history, maintains alert contact groups, and retunes or retires checks.

Authorize the account and your agent has all 69 actions from the first conversation.
