Skip to content
Back to skills

Didit Connect

ASecurity

Connects to the person's Didit account, picks the right organization and application, and sets the rules for every Didit action. Use when the user starts working with Didit from chat, asks "which apps do I have", "is this sandbox or live", "am I signed in to Didit", "do you need my API key", cannot find a Didit tool, gets a permission or read-only error, or asks how something works in Didit.

  • 28 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agentsgogitapidatabasebackend

Works with

  • claude code
  • cli
  • api
  • mcp

Security analysis

A100/100

Scanned November 18, 2026

npx -y skills add didit-protocol/skills --skill didit-connect --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Didit Connect?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Didit Connect
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/didit-protocol-didit-connect/badge)](https://www.skillsdirectory.com/skills/didit-protocol-didit-connect)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: didit-connect
description: Connects to the person's Didit account, picks the right organization and application, and sets the rules for every Didit action. Use when the user starts working with Didit from chat, asks "which apps do I have", "is this sandbox or live", "am I signed in to Didit", "do you need my API key", cannot find a Didit tool, gets a permission or read-only error, or asks how something works in Didit.
---

# Didit: connect and route

The Didit MCP server acts as the signed-in person, with the permissions of their role. These rules apply to every Didit skill in this plugin.

## Sign-in

- Sign-in is OAuth ("Log in with Didit"). The host opens it the first time a Didit tool is used, or through `/mcp` in Claude Code.
- Never ask the person for a password, an API key or a one-time code to sign in. If a tool answers that the person is not signed in, tell them to reconnect the "didit" server from their client's connector or MCP settings.
- A person without an account can create one at https://business.didit.me.

## Always start with the context

1. Call `didit_context_get` first. It returns the organizations and applications the person can use with their ids, each application's `mode` (`sandbox` or `live`) when the server knows it, and `default_organization_id` and `default_application_id`. A default is present only when there is exactly one; an organization whose applications could not be listed leaves `default_application_id` out.
2. Without `default_application_id`, establish the target before any change or billable action: use the application the person named, or ask which one.
3. Scope ids follow each tool's schema. Always send the ids a tool requires. Send an optional `organization_id` or `application_id` only when the context shows several organizations or applications, or when it returned no default for that id: then ask the person which organization or application to use and pass the one they name. Never send an id the tool does not declare. Through a discovery proxy (`didit_tool_call_read` or `didit_tool_call_write`), put the target's arguments, ids included, inside `arguments`, never next to `name`.
   - For example `didit_org_list_api_keys` requires `application_id`; read ids from `didit_context_get`.
   - `didit_docs_search` and `didit_session_get_decision` take neither id; `didit_org_get_balance` and the member tools take only `organization_id`.
4. Read sandbox or live from `mode` only. Never decide it from an application's name. If `mode` is missing, say the environment is unknown and treat the application as live (billable) until the person confirms otherwise.
5. If `didit_context_get` shows `connection.type: api_key`, this connection is one application with no person: member, role, API key, billing-detail (plan, payment methods, receipts), compliance and audit-log tools are not available; the credit balance (`didit_org_get_balance`) still is. Say so and point the person to sign in with OAuth for the missing ones.
6. If `didit_context_get` shows an organization with zero applications, do not conclude there are none. Today only the Owner and Admin roles can list applications; for other roles (Reader, Developer, Compliance Officer) the context comes back with none even when the person can work in several. Read the person's own row in `didit_org_list_members`: `accessible_applications` gives the application ids and names. The `mode` is not in that row, so treat each application as live (billable) until the person says which one is the sandbox, and send the ids each tool's schema declares. A call the person's role does not allow is refused with `forbidden` (sometimes `missing_scope`): say the role does not allow it and that an organization admin can change the role. After a role change the person must reconnect Didit, because a connection keeps the permissions it was approved with.

## Calling tools

- If a tool is in your tool list, call it directly.
- If it is not listed, use the discovery tools, but only when they are themselves in your tool list: `didit_tool_search` to find it, `didit_tool_describe` to read its arguments, then `didit_tool_call_read` for a read or `didit_tool_call_write` for a change.
- The discovery tools are listed only when the connection does not load every toolset (for example `?toolsets=core`). A full connection lists every tool directly.
- A tool can also be missing because the connection is read-only. On a read-only connection that loads every toolset, no write tool and no discovery tool is listed. Tell the person to reconnect without `read_only` to make changes.
- The list is the same for every role; a call your role does not allow is refused, with the missing permission in the error. Name that permission and tell the person to ask an organization admin for a role that allows it.
- In both cases never attempt a proxy call through another tool to get around it.
- The hosted server also lists tool groups no skill here covers in depth: Travel Rule (23 tools, for example `didit_travel_rule_get_settings`), Compliance (9, for example `didit_compliance_requirements`), Marketplace (3, for example `didit_marketplace_list_catalog`) and Networks (3, for example `didit_network_list`). Call them by name when they are listed, or find them with `didit_tool_search`, and read each schema before the first call. The same rules apply: context first, agreement before any change.

## Confirmations

- Every change (status updates, deletions, invitations, webhooks, exports) needs the person's agreement first: describe what will change and wait for a clear yes before calling the tool. Say plainly when a change cannot be undone (overwriting a decision, deleting a webhook or a member).
- An instruction given in advance or with a condition ('if it is only X, approve') is not agreement. Report what you found, say exactly what you would change and in which application (sandbox or live), then wait for a yes.
- Send `confirm: true` only to a tool whose schema declares `confirm`, and only after the person agreed to that exact action. In this plugin's recipes those tools are: `didit_case_manage` (filing a SAR), `didit_session_delete` and `didit_org_create_api_key`. Any other tool you reach by name or through discovery follows its own schema: if it declares `confirm`, the same rule applies. Rule, webhook and list deletions take none.

## Billable actions

- Sandbox applications are free to test in.
- In a live application this can use your Didit credits: creating a verification session, running a standalone check, submitting a transaction and screening a wallet. Which charges apply depends on the feature and the plan. In a live application, or one whose mode is unknown, say so before the call and wait for the person to agree.
- Never state a price. For pricing, link https://didit.me/pricing. To see what is left, use `didit_org_get_balance` (see didit-reports).

## How-to questions

For any question about how Didit works, a feature, a webhook payload or an SDK, call `didit_docs_search` and cite the link it returns. Do not answer from memory.

## Lighter connections (optional)

The server URL accepts two query parameters. The person adds them when they connect:

- `https://mcp.didit.me/mcp?toolsets=core` loads a shorter list of tools. The rest stays reachable through the discovery tools.
- `read_only=true` lists only tools that read data, for example `https://mcp.didit.me/mcp?toolsets=core&read_only=true`. Nothing can be changed on such a connection.

## Integration code is a different job

If the person wants backend code that calls the Didit REST API with an API key, these tools are the wrong fit. Point them to the developer skills (the `didit-api` plugin, or the `skills/` folder of github.com/didit-protocol/skills) and to https://docs.didit.me.

## Which skill handles what

| Request | Skill |
|---|---|
| Create a verification workflow or link, read a decision, test in sandbox | didit-verify-people |
| Sessions in review, approve or decline, add notes, work cases | didit-review-queue |
| One-off checks: AML, document, address, database, face, phone code (email through a session) | didit-run-checks |
| Verify a company (KYB), look up existing business records | didit-verify-businesses |
| Transactions, monitoring rules, back-tests, wallet screening, Travel Rule | didit-monitor-transactions |
| Analytics, balance, plan, exports | didit-reports |
| Members, roles, webhooks, lists, branding, questionnaires | didit-workspace-admin |

## What good output looks like

- The organization and application in use, and whether it is sandbox, live or unknown, stated once at the start.
- The tool that was called, or the exact reason a tool is not available and what the person can change.
- A clear question before any billable or irreversible action.

## Do not

- Never ask for a password, an API key or a one-time code.
- Never fall back to raw HTTP calls (curl/REST) for a task these tools cover.
- Never invent an organization, application, session or workflow id. Read ids from tool results.
- Never state prices. Link https://didit.me/pricing.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.