Cloudflare Radar (BYOK)

Cloudflare Radar (BYOK) — connector documentation

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

What Cloudflare Radar (BYOK) is for

Cloudflare Radar (BYOK) lets an AI assistant read your own Cloudflare Radar data through the Cloudflare Radar API with a key you supply (Cloudflare API token with Account > Radar > Read). Read-only: 12 tools (list_traffic_anomalies, list_internet_outages, get_asn, list_asns, get_ip_details, get_domain_rank, list_top_domains, list_bgp_hijack_events, list_bgp_route_leaks, get_bgp_routing_stats, get_speed_summary, list_tlds). 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.cloudflare.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Cloudflare Radar. Cloudflare 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:

• "Were there Internet traffic anomalies in Portugal in the last week?"
• "Which Internet outages happened recently and what caused them?"
• "What network is AS13335 and how many users does it have?"
• "Which are the biggest networks in Portugal by users?"
• "Which network owns the IP 1.1.1.1?"
• "How popular is example.com on Cloudflare Radar?"

What it does

• list_traffic_anomalies: List the latest Internet traffic anomalies detected by Cloudflare, with the affected country, network (AS) or origin, start and end time and verification status.
• list_internet_outages: List recent Internet outages and anomalies with cause, type, affected countries and networks, description and time span.
• get_asn: Get details of one Autonomous System (network): name, organization, country, website, estimated users and related networks.
• list_asns: List Autonomous Systems with name, organization, country, website and estimated users, ordered by ASN or population.
• get_ip_details: Look up an IP address: the network (ASN) and organization announcing it, plus its country and IP version.
• get_domain_rank: Get the Cloudflare Radar popularity rank of one domain with its content categories and optionally the top locations.
• list_top_domains: List the most popular or trending domains on Cloudflare Radar with rank, categories and rank change.
• list_bgp_hijack_events: List detected BGP hijack events with hijacker and victim ASNs, prefixes, confidence score, duration and tags.
• list_bgp_route_leaks: List detected BGP route leak events with the leaking ASN, number of prefixes, peers and origins, countries and timing.
• get_bgp_routing_stats: Get global BGP routing table statistics: routes, prefixes and origins for IPv4 and IPv6, with RPKI valid, invalid and unknown counts. Optionally for one AS.
• get_speed_summary: Get the global Internet speed test summary: download and upload bandwidth, idle and loaded latency, jitter and packet loss.
• list_tlds: List top-level domains with type (generic, country code and so on) and the organization managing each.

BYOK key

You bring your own Cloudflare Radar Cloudflare API token with Account > Radar > Read (https://dash.cloudflare.com/profile/api-tokens). 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.cloudflare.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://developers.cloudflare.com/radar/get-started/first-request/ (the API this connector calls, with a BYOK key)

Live from the Cloudflare Radar API (api.cloudflare.com) with a BYOK key; documentation: https://developers.cloudflare.com/radar/get-started/first-request/. 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 Cloudflare Radar. Cloudflare 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 Cloudflare Radar account.

Built for: Worldwide. Languages: English.

Cloudflare Radar (BYOK) — Privacy Policy

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

What Cloudflare Radar (BYOK) is. Cloudflare Radar (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Cloudflare Radar data: Read Internet outages, traffic anomalies, BGP events, network (ASN) and IP details, speed and domain rankings from Cloudflare Radar with your own API token. You bring your own Cloudflare Radar Cloudflare API token with Account > Radar > Read; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Cloudflare 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.cloudflare.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 Cloudflare 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 Cloudflare Radar receives. The request we make on your behalf, including the key and the arguments, under Cloudflare Radar's own terms and privacy policy. Cloudflare 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 Cloudflare 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 Cloudflare 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. Cloudflare 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 Cloudflare Radar at any time to end all access.

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

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

Cloudflare Radar (BYOK) — Terms of Service

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

1. The Service. Cloudflare Radar (BYOK) provides: Read Internet outages, traffic anomalies, BGP events, network (ASN) and IP details, speed and domain rankings from Cloudflare Radar with your own API token. 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 Cloudflare Radar credentials and only access data you are allowed to access. Cloudflare Radar's terms apply to your use of Cloudflare 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 Cloudflare Radar. Cloudflare 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 Cloudflare Radar returns, lightly trimmed; it may be incomplete, delayed or changed by Cloudflare Radar. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Cloudflare 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 Cloudflare 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; Cloudflare 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 Cloudflare 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 Cloudflare 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-cloudflare-radar

Cloudflare Radar (BYOK) support

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

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