Stripe Radar (BYOK)

Stripe Radar (BYOK) — connector documentation

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

What Stripe Radar (BYOK) is for

Stripe Radar (BYOK) lets an AI assistant read your own Stripe Radar data through the Stripe Radar API with a key you supply (restricted API key with read permissions only (starts with rk_live_ or rk_test_)). Read-only: 6 tools (list_value_lists, get_value_list, list_early_fraud_warnings, get_early_fraud_warning, list_reviews, get_review). 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.stripe.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Stripe Radar. Stripe Radar 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:

• "Which Radar value lists do I have?"
• "What kind of values does Radar list rsl_1Nf3pq hold?"
• "Do I have any early fraud warnings to act on?"
• "What is early fraud warning issfr_1Nf3pq about?"
• "Which payments are waiting in my Radar review queue?"
• "Why was review prv_1Nf3pq opened?"

What it does

• list_value_lists: List your Radar value lists (allow lists, block lists and custom lists) with name, alias and the type of value each holds. List contents are not returned. Works with a restricted key that has read access to this resource only.
• get_value_list: Get one Radar value list by id: name, alias, item type, creator and creation time. The items are not returned. Works with a restricted key that has read access to this resource only.
• list_early_fraud_warnings: List early fraud warnings issued by card networks for your charges, with the fraud type, whether action is still possible, and the charge and payment intent ids. Works with a restricted key that has read access to this resource only.
• get_early_fraud_warning: Get one early fraud warning by id with fraud type, whether it is actionable, and the related charge and payment intent. Works with a restricted key that has read access to this resource only.
• list_reviews: List Radar reviews that are currently open, with the reason each was opened (rule or manual) and the charge and payment intent ids. IP address and ZIP code are not returned. Works with a restricted key that has read access to this resource only.
• get_review: Get one Radar review by id: open state, why it was opened and closed, and the related charge and payment intent. Works with a restricted key that has read access to this resource only.

BYOK key

You bring your own Stripe Radar restricted API key with read permissions only (starts with rk_live_ or rk_test_) (https://dashboard.stripe.com/apikeys). 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.stripe.com 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://docs.stripe.com/api/radar/value_lists (the API this connector calls, with a BYOK key)

Live from the Stripe Radar API (api.stripe.com) with a BYOK key; documentation: https://docs.stripe.com/api/radar/value_lists. 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 Stripe Radar. Stripe Radar 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 Stripe Radar account.

Built for: Worldwide. Languages: English.

Stripe Radar (BYOK) — Privacy Policy

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

What Stripe Radar (BYOK) is. Stripe Radar (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Stripe Radar data: Read your Stripe Radar value lists, early fraud warnings and manual reviews with a restricted read-only key. You bring your own Stripe Radar restricted API key with read permissions only (starts with rk_live_ or rk_test_); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Stripe Radar 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.stripe.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Stripe Radar 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 Stripe Radar receives. The request we make on your behalf, including the key and the arguments, under Stripe Radar's own terms and privacy policy. Stripe Radar acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Stripe Radar 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 Stripe Radar 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. Stripe Radar (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 Stripe Radar at any time to end all access.

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

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

Stripe Radar (BYOK) — Terms of Service

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

1. The Service. Stripe Radar (BYOK) provides: Read your Stripe Radar value lists, early fraud warnings and manual reviews with a restricted read-only 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 Stripe Radar credentials and only access data you are allowed to access. Stripe Radar's terms apply to your use of Stripe Radar; 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 Stripe Radar. Stripe Radar 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 Stripe Radar returns, lightly trimmed; it may be incomplete, delayed or changed by Stripe Radar. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Stripe Radar 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 Stripe Radar'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; Stripe Radar 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 Stripe Radar 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 Stripe Radar 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-stripe-radar

Stripe Radar (BYOK) support

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

• MCP endpoint: https://byok-stripe-radar.connectorbay.com/mcp
• REST API: https://byok-stripe-radar.connectorbay.com/openapi.json
• Live status: https://byok-stripe-radar.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. Stripe Radar (BYOK) never asks for them.