Paradym
Paradym is an API-first platform that simplifies the issuance, verification, and management of verifiable credentials, supporting standards like SD-JWT VCs over OpenID4VC and AnonCreds over DIDComm.
Verdict
Common use cases
- Issue event attendance badges from Slack
- Verify employment credentials during onboarding
- Audit credential issuance history for compliance
- Revoke compromised credentials in real time
- Generate proof-of-training certificates after workshops
Integration
- Vendor
- Paradym
- Category
- other
- Auth
- API_KEY
- Composio slug
paradym
Tools
Setup
Setup guide
- 11. Open your Switchy workspace settings and navigate to the MCP Integrations tab. 2. Click 'Add Integration' and select Paradym from the list. 3. Log into your Paradym dashboard, navigate to Settings > API Keys, and generate a new key with read/write permissions. 4. Paste the API key into Switchy's connection form and click 'Connect'. 5. Switchy will test the connection by fetching your credential templates — if it succeeds, you'll see a green checkmark. 6. Open any Space, type '@Paradym list my credential templates' and send the message. 7. If the MCP responds with a list of templates, the integration is live and ready for your team to use.
What teammates see: by default, memories from Paradym are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Credential Templates
@Paradym show me all the credential templates we have configured in our accountOpen in a Space →
Issue Event Badge
@Paradym issue an event attendance badge for jane.doe@example.com using the 'Conference 2024' templateOpen in a Space →
Verify Credential
@Paradym verify the credential with ID cred_abc123xyz and tell me if it's still activeOpen in a Space →
Revoke Credential
@Paradym revoke the credential with ID cred_def456uvw and log the reason as 'employment terminated'Open in a Space →
Audit Issuance History
@Paradym show me all credentials we issued in the last 30 days, grouped by template typeOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Paradym check the status of credential issuance for project ID proj_abc123 and list any pending verifications
Based on the project data, three credentials were issued in the last 24 hours. Two have been accepted by holders and are now active. One credential (ID: cred_xyz789) is pending holder acceptance, issued 6 hours ago to holder DID did:key:z6Mk... The project has no pending verification requests at this time. All issued credentials use the EmployeeBadge schema v2.1.
This example shows read-only monitoring of credential lifecycle state. Requires API key with read access to the project scope. Paradym's credential issuance is asynchronous — the MCP reports current state, but acceptance timing depends on holder action outside your control.
@Paradym issue a new verifiable credential using the CustomerLoyalty schema to holder DID did:web:alice.example.com with tier set to Gold
Credential issuance initiated. The CustomerLoyalty credential has been prepared with tier attribute 'Gold' and sent to holder did:web:alice.example.com. Issuance ID: iss_def456. The holder will receive an offer via their configured delivery method. Once accepted, the credential will move to 'issued' status. You can track progress by checking issuance ID iss_def456.
This demonstrates the core write operation: creating and offering a credential. The holder must accept the offer for issuance to complete — this can take seconds or days depending on holder availability. Ensure your API key has credential issuance permissions and the schema exists in your Paradym project before running this prompt.
@Paradym review all credential revocations from the past 30 days and summarize the most common reasons given in the metadata
In the past 30 days, 47 credentials were revoked across your projects. The most frequent reason (28 occurrences) was 'employment_terminated', followed by 'credential_expired' (12 occurrences) and 'data_correction_required' (7 occurrences). The revocations span three schemas: EmployeeBadge (31), ContractorAccess (10), and PartnerCertification (6). All revocations were processed successfully with no failed transactions.
This synthesis example pairs Paradym's revocation log data with AI reasoning to surface patterns. Useful for compliance audits or operational reviews. Note that revocation reasons are freeform metadata you set during revocation — the MCP can only summarize what your team has recorded. Requires read access to revocation history.
Use-case deep-dives
When verifiable credentials replace manual audit trails
A 6-person compliance team at a fintech startup needs to issue and verify employee certifications for SOC 2 audits. Paradym handles the cryptographic signing and verification without the team learning zero-knowledge proofs or managing a blockchain node. The MCP requires an API key but no tools are exposed yet, so you're limited to whatever the vendor's REST endpoints support directly. This works if your use case is straightforward credential lifecycle management—issue a cert, verify it later, revoke if needed. If you need custom workflows or want to query credential metadata in Slack threads, you'll hit the wall fast until Paradym ships MCP tool definitions. The buy: you get decentralized identity infrastructure without hiring a cryptographer, but only for the narrow paths the API already paves.
Verifiable claims for B2B partner vetting
A 12-person SaaS company onboards enterprise partners who must prove compliance status without sharing raw audit documents. Paradym lets the partner issue a verifiable claim ('we passed ISO 27001 in Q4 2024') that your team verifies cryptographically. The partner never uploads PDFs; you never store their sensitive data. API key auth keeps setup simple, but the missing MCP tools mean you can't automate verification inside your CRM or trigger workflows when a claim expires. This is a fit if onboarding happens in a dedicated portal and you're okay with manual API calls for now. If you need to pipe verification results into HubSpot or send Slack alerts on expiry, wait for tool support or build your own wrapper. The buy: privacy-preserving partner vetting that scales better than email attachments and NDA-signed spreadsheets.
When NFT tickets need enterprise guardrails
A 3-person events team wants to issue conference passes as verifiable credentials—attendees can prove ownership without a centralized ticket database, and transfers leave an audit trail. Paradym gives you the credential plumbing (issue, verify, revoke) with API key auth, but zero MCP tools means no way to query 'who transferred their ticket in the last hour' from a Slack command or auto-revoke no-shows during check-in. This works if your ticketing flow is batch-oriented: issue 500 credentials Monday, verify them at the door Friday, reconcile transfers afterward. If you need real-time visibility or want to integrate with Eventbrite webhooks, the missing tooling forces you back to raw API calls. The buy: you get cryptographic ticket integrity without running your own blockchain, but only if your workflow tolerates blind spots until tooling arrives.
Frequently asked
What does the Paradym MCP do in Switchy?
The Paradym MCP connects Switchy to Paradym's verifiable credential platform, letting your AI agents read credential schemas, issue credentials, and verify presentations without leaving the workspace. Since tool definitions aren't captured yet, expect basic read/write operations on credential workflows. You'll authenticate once with an API key, then any team member can invoke Paradym actions through natural language prompts.
Do I need admin access to connect Paradym?
You need an API key from your Paradym account, which typically requires admin or developer permissions to generate. The key lives in Switchy's secure vault and gets reused across all team sessions. If your Paradym instance restricts key creation to specific roles, coordinate with whoever manages your credential infrastructure before connecting.
Can the Paradym MCP issue credentials directly from a chat?
Yes, assuming Paradym's API supports issuance and the MCP exposes that tool. You'd describe the credential type and recipient in a prompt, and the agent calls Paradym to mint and deliver it. Without tool definitions loaded yet, confirm with Switchy support which Paradym endpoints are wired up—schema management and verification are usually prioritised over bulk issuance.
How does this compare to calling Paradym's API directly?
Direct API calls give you full control and custom error handling, but require writing code for every credential operation. The MCP trades that flexibility for speed—your team describes what they want in plain English, and Switchy translates it into the right API sequence. Use the MCP for ad-hoc credential checks and schema exploration; stick with direct integration for high-volume issuance pipelines.
Who on the team should connect the Paradym MCP?
Whoever manages your verifiable credential infrastructure or holds API keys for Paradym. Once connected, any Switchy user can invoke Paradym tools without needing their own key. If you're experimenting with decentralised identity for the first time, have your security or compliance lead review the scopes before enabling it workspace-wide.