OpenSanctions (BYOK)

OpenSanctions (BYOK) — connector documentation

• MCP endpoint: https://byok-opensanctions.connectorbay.com/mcp
• REST API: POST https://byok-opensanctions.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-opensanctions.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own OpenSanctions OpenSanctions API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-opensanctions.connectorbay.com/health · Tool schemas: https://byok-opensanctions.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-opensanctions · agent@connectorbay.com

What OpenSanctions (BYOK) is for

OpenSanctions (BYOK) lets an AI assistant read your own OpenSanctions data through the OpenSanctions API with a key you supply (OpenSanctions API key). Read-only: 7 tools (search_entities, screen_entity, get_entity, list_adjacent_entities, list_adjacent_by_property, list_datasets, list_matching_algorithms). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.opensanctions.org. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by OpenSanctions. OpenSanctions and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Is there a sanctions or PEP entry for Ilham Aliyev?"
• "Screen the person Jane Doe born 1970-01-01 from Russia against sanctions lists"
• "Show the full OpenSanctions record for entity Q7747"
• "What entities are linked to entity Q7747?"
• "List the sanctions entries attached to entity Q7747"
• "Which sanctions datasets does OpenSanctions cover?"

What it does

• search_entities: Full-text search for people, companies and other entities in sanctions, PEP and watchlist datasets. Good for lookups by name; use screen_entity for screening decisions.
• screen_entity: Screen a person or company against a dataset by describing it (name, birth date, country). Returns scored candidate matches with a match flag and score. Only asks a question of the database.
• get_entity: Get the full record of one entity by ID: names, birth data, countries, topics, datasets that mention it and, if nested is true, related sanctions, ownership and family entities.
• list_adjacent_entities: List entities linked to a given entity (sanctions, ownership, family, passports), grouped by relationship, with a count for each group.
• list_adjacent_by_property: Page through the entities linked to a given entity through one property, for example 'sanctions', 'ownershipOwner' or 'familyPerson'.
• list_datasets: List the datasets the API can search (sanctions lists, PEP lists and others) with title, publisher summary, entity counts and last update.
• list_matching_algorithms: List the scoring algorithms screen_entity can use, with the default and best-quality choice and a description of each.

BYOK key

You bring your own OpenSanctions OpenSanctions API key (https://www.opensanctions.org/api/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.opensanctions.org over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://www.opensanctions.org/docs/api/ (the API this connector calls, with a BYOK key)

Live from the OpenSanctions API (api.opensanctions.org) with a BYOK key; documentation: https://www.opensanctions.org/docs/api/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by OpenSanctions. OpenSanctions and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your OpenSanctions account.

Built for: Worldwide. Languages: English.

OpenSanctions (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What OpenSanctions (BYOK) is. OpenSanctions (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own OpenSanctions data: Search and screen people, companies and vessels against sanctions lists, politically exposed persons and other watchlists with your own OpenSanctions API key. You bring your own OpenSanctions OpenSanctions API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one OpenSanctions call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.opensanctions.org, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If OpenSanctions rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What OpenSanctions receives. The request we make on your behalf, including the key and the arguments, under OpenSanctions's own terms and privacy policy. OpenSanctions acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer OpenSanctions gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your OpenSanctions data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. OpenSanctions (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at OpenSanctions at any time to end all access.

Children. OpenSanctions (BYOK) is a general-audience service operated by the adult using the assistant, under OpenSanctions's own age rules.

Changes. We will post changes here with a new effective date.

OpenSanctions (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the OpenSanctions (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. OpenSanctions (BYOK) provides: Search and screen people, companies and vessels against sanctions lists, politically exposed persons and other watchlists with your own OpenSanctions API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own OpenSanctions credentials and only access data you are allowed to access. OpenSanctions's terms apply to your use of OpenSanctions; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by OpenSanctions. OpenSanctions and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data OpenSanctions returns, lightly trimmed; it may be incomplete, delayed or changed by OpenSanctions. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your OpenSanctions account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent OpenSanctions's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; OpenSanctions may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your OpenSanctions key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action OpenSanctions takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-opensanctions

OpenSanctions (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-opensanctions.connectorbay.com/mcp
• REST API: https://byok-opensanctions.connectorbay.com/openapi.json
• Live status: https://byok-opensanctions.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. OpenSanctions (BYOK) never asks for them.