Summary
Connects Claude to Cloudflare Radar's internet telemetry APIs for querying global traffic patterns, cyberattack data, BGP routing information, and network quality metrics. Hosted by Pipeworx as a streamable HTTP endpoint, so no local setup needed. The ask_pipeworx interface lets you query in natural language instead of calling specific tools directly. Useful when you need real-time or historical internet infrastructure data during analysis, like tracking DDoS trends, investigating routing anomalies, or comparing regional connectivity quality. Can be added standalone or as part of the full Pipeworx gateway that includes 600+ other data sources.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
Tools
Public tool metadata for what this MCP can expose to an agent.
68 tools
accounts_listList all accounts in your Cloudflare account
List all accounts in your Cloudflare account
No parameter schema in public metadata yet.
set_active_accountSet active account to be used for tool calls that require accountId1 params
Set active account to be used for tool calls that require accountId
Parameters* required
activeAccountIdParamstringThe accountId present in the users Cloudflare account, that should be the active accountId.
list_autonomous_systemsList Autonomous Systems4 params
List Autonomous Systems
Parameters* required
limitnumberoffsetnumberorderBystringOptional order by parameter: "ASN" or "POPULATION".one of
ASN · POPULATIONlocationstringFilters results by location. Specify a valid alpha-2 location code.
get_as_detailsGet Autonomous System details by ASN1 params
Get Autonomous System details by ASN
Parameters* required
asnnumberAutonomous System Number (ASN), must be a positive number.
get_ip_detailsGet IP address information including full ASN details (name, country, population estimates from APNIC).1 params
Get IP address information including full ASN details (name, country, population estimates from APNIC).
Parameters* required
ipstringIPv4 or IPv6 address in standard notation.
get_traffic_anomaliesGet traffic anomalies and outages7 params
Get traffic anomalies and outages
Parameters* required
asnnumberAutonomous System Number (ASN), must be a positive number.
limitnumberoffsetnumberdateEndstringEnd date in ISO 8601 format (e.g., 2023-04-30T23:59:59Z). Either use this parameter together with `dateStart`, or use `dateRange`.
locationstringFilters results by location. Specify a valid alpha-2 location code.
dateRangestringFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters).
dateStartstringStart date in ISO 8601 format (e.g., 2023-04-01T00:00:00Z). Either use this parameter together with `dateEnd`, or use `dateRange`.
get_internet_services_rankingGet top Internet services3 params
Get top Internet services
Parameters* required
datearrayFilters results by date.
limitnumberserviceCategoryarrayFilters results by Internet service category.
get_domains_rankingGet top or trending domains4 params
Get top or trending domains
Parameters* required
datearrayFilters results by date.
limitnumberlocationarrayFilters results by location. Specify a comma-separated list of alpha-2 location codes.
rankingTypestringThe ranking type.one of
POPULAR · TRENDING_RISE · TRENDING_STEADYget_domain_rank_detailsGet domain rank details2 params
Get domain rank details
Parameters* required
datearrayFilters results by date.
domainstringA valid domain name, e.g., example.com or sub.domain.co.uk. Must follow standard domain formatting rules without protocol or path.
get_http_dataRetrieve HTTP traffic trends.9 params
Retrieve HTTP traffic trends.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
geoIdarrayFilters results by Geolocation (ADM1 - administrative level 1, e.g., states/provinces). Provide an array of GeoNames IDs. Prefix with `-` to exclude. Example: ["2267056", "-360689"] includes Lisbon area but excludes another region. IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same region across time periods, repeat the GeoID (e.g., geoId: ["2267056", "2267056"] with dateRange: ["7d", "7dcontrol"]). Using a single geoId with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all regions.
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
continentarrayFilters results by continent. Provide an array of alpha-2 continent codes (e.g., "EU", "NA"). Prefix a code with `-` to exclude it (e.g., ["-EU", "NA"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: ["EU", "EU"] with dateRange: ["7d", "7dcontrol"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of HTTP data to retrieve.one of
timeseries · summary/adm1 · summary/as · summary/bot_class · summary/browser · summary/browser_familynormalizationstringNormalization method applied to results. timeseries accepts PERCENTAGE_CHANGE or MIN0_MAX; timeseries_groups accepts PERCENTAGE or MIN0_MAX. See https://developers.cloudflare.com/radar/concepts/normalization/one of
PERCENTAGE_CHANGE · MIN0_MAX · PERCENTAGEget_dns_queries_dataRetrieve trends in DNS queries to the 1.1.1.1 resolver.8 params
Retrieve trends in DNS queries to the 1.1.1.1 resolver.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
continentarrayFilters results by continent. Provide an array of alpha-2 continent codes (e.g., "EU", "NA"). Prefix a code with `-` to exclude it (e.g., ["-EU", "NA"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: ["EU", "EU"] with dateRange: ["7d", "7dcontrol"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of DNS data to retrieve.one of
timeseries · summary/as · summary/cache_hit · summary/dnssec · summary/dnssec_aware · summary/dnssec_e2enormalizationstringNormalization method applied to results. timeseries_groups accepts PERCENTAGE or MIN0_MAX. See https://developers.cloudflare.com/radar/concepts/normalization/one of
PERCENTAGE · MIN0_MAXget_l7_attack_dataRetrieve application layer (L7) attack trends.8 params
Retrieve application layer (L7) attack trends.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
continentarrayFilters results by continent. Provide an array of alpha-2 continent codes (e.g., "EU", "NA"). Prefix a code with `-` to exclude it (e.g., ["-EU", "NA"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: ["EU", "EU"] with dateRange: ["7d", "7dcontrol"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of L7 attack data to retrieve.one of
timeseries · summary/httpMethod · summary/httpVersion · summary/ipVersion · summary/managedRules · summary/mitigationProductnormalizationstringNormalization method applied to results. timeseries accepts PERCENTAGE_CHANGE or MIN0_MAX; timeseriesGroups accepts PERCENTAGE or MIN0_MAX; top/attacks accepts PERCENTAGE or MIN_MAX. See https://developers.cloudflare.com/radar/concepts/normalization/one of
PERCENTAGE_CHANGE · MIN0_MAX · PERCENTAGE · MIN_MAXget_l3_attack_dataRetrieve network layer (L3/DDoS) attack trends.8 params
Retrieve network layer (L3/DDoS) attack trends.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
continentarrayFilters results by continent. Provide an array of alpha-2 continent codes (e.g., "EU", "NA"). Prefix a code with `-` to exclude it (e.g., ["-EU", "NA"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: ["EU", "EU"] with dateRange: ["7d", "7dcontrol"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of L3 attack data to retrieve.one of
timeseries · summary/protocol · summary/ipVersion · summary/vector · summary/bitrate · summary/durationnormalizationstringNormalization method applied to results. timeseries accepts PERCENTAGE_CHANGE or MIN0_MAX; timeseriesGroups accepts PERCENTAGE or MIN0_MAX; top/attacks accepts PERCENTAGE or MIN_MAX. See https://developers.cloudflare.com/radar/concepts/normalization/one of
PERCENTAGE_CHANGE · MIN0_MAX · PERCENTAGE · MIN_MAXget_email_routing_dataRetrieve Email Routing trends.4 params
Retrieve Email Routing trends.
Parameters* required
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of Email Routing data to retrieve.one of
summary/ipVersion · summary/encrypted · summary/arc · summary/dkim · summary/dmarc · summary/spfget_email_security_dataRetrieve Email Security trends.4 params
Retrieve Email Security trends.
Parameters* required
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of Email Security data to retrieve.one of
summary/spam · summary/malicious · summary/spoof · summary/threatCategory · summary/arc · summary/dkimget_internet_speed_dataRetrieve summary of bandwidth, latency, jitter, and packet loss, from the previous 90 days of Cloudflare Speed Test.6 params
Retrieve summary of bandwidth, latency, jitter, and packet loss, from the previous 90 days of Cloudflare Speed Test.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
orderBystringSpecifies the metric to order the results by. Only allowed for top locations and ASesone of
BANDWIDTH_DOWNLOAD · BANDWIDTH_UPLOAD · LATENCY_IDLE · LATENCY_LOADED · JITTER_IDLE · JITTER_LOADEDlocationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
continentarrayFilters results by continent. Provide an array of alpha-2 continent codes (e.g., "EU", "NA"). Prefix a code with `-` to exclude it (e.g., ["-EU", "NA"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: ["EU", "EU"] with dateRange: ["7d", "7dcontrol"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dimensionstringDimension indicating the type and format of Internet speed data to retrieve.one of
summary · top/locations · top/asesget_internet_quality_dataRetrieves a summary or time series of bandwidth, latency, or DNS response time percentiles from the Radar Internet Quality Index (IQI).8 params
Retrieves a summary or time series of bandwidth, latency, or DNS response time percentiles from the Radar Internet Quality Index (IQI).
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
formatstringone of
summary · timeseriesGroupsmetricstringSpecifies which metric to return (bandwidth, latency, or DNS response time).one of
BANDWIDTH · DNS · LATENCYdateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
continentarrayFilters results by continent. Provide an array of alpha-2 continent codes (e.g., "EU", "NA"). Prefix a code with `-` to exclude it (e.g., ["-EU", "NA"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: ["EU", "EU"] with dateRange: ["7d", "7dcontrol"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
get_ai_dataRetrieves AI-related data, including traffic from AI user agents, as well as popular models and model tasks specifically from Cloudflare Workers AI.8 params
Retrieves AI-related data, including traffic from AI user agents, as well as popular models and model tasks specifically from Cloudflare Workers AI.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
continentarrayFilters results by continent. Provide an array of alpha-2 continent codes (e.g., "EU", "NA"). Prefix a code with `-` to exclude it (e.g., ["-EU", "NA"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: ["EU", "EU"] with dateRange: ["7d", "7dcontrol"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of AI data to retrieve.one of
bots/timeseries · bots/summary/user_agent · bots/summary/crawl_purpose · bots/summary/industry · bots/summary/vertical · bots/timeseries_groups/user_agentnormalizationstringNormalization method applied to results. bots/timeseries_groups accepts PERCENTAGE or MIN0_MAX. See https://developers.cloudflare.com/radar/concepts/normalization/one of
PERCENTAGE · MIN0_MAXget_bgp_hijacksRetrieve BGP hijack events. BGP hijacks occur when an AS announces routes it does not own, potentially redirecting traffic.14 params
Retrieve BGP hijack events. BGP hijacks occur when an AS announces routes it does not own, potentially redirecting traffic.
Parameters* required
limitnumberoffsetnumberprefixstringFilter by IP prefix (e.g., "1.1.1.0/24").
sortBystringSort results by specified field.one of
TIME · CONFIDENCE · IDdateEndstringEnd date in ISO 8601 format (e.g., 2023-04-30T23:59:59Z). Either use this parameter together with `dateStart`, or use `dateRange`.
dateRangestringFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters).
dateStartstringStart date in ISO 8601 format (e.g., 2023-04-01T00:00:00Z). Either use this parameter together with `dateEnd`, or use `dateRange`.
sortOrderstringSort order (ascending or descending).one of
ASC · DESCvictimAsnintegerFilter by the potential victim AS of a BGP hijack event.
hijackerAsnintegerFilter by the potential hijacker AS of a BGP hijack event.
involvedAsnnumberFilter by ASN involved (as hijacker or victim) in a BGP event.
maxConfidenceintegerFilter by maximum confidence score (1-4 low, 5-7 mid, 8+ high).
minConfidenceintegerFilter by minimum confidence score (1-4 low, 5-7 mid, 8+ high).
involvedCountrystringFilter by country code of the involved AS in a BGP event.
get_bgp_leaksRetrieve BGP route leak events. Route leaks occur when an AS improperly announces routes learned from one peer to another.10 params
Retrieve BGP route leak events. Route leaks occur when an AS improperly announces routes learned from one peer to another.
Parameters* required
limitnumberoffsetnumbersortBystringSort results by specified field.one of
TIME · CONFIDENCE · IDdateEndstringEnd date in ISO 8601 format (e.g., 2023-04-30T23:59:59Z). Either use this parameter together with `dateStart`, or use `dateRange`.
leakAsnnumberFilter by the leaking AS of a route leak event.
dateRangestringFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters).
dateStartstringStart date in ISO 8601 format (e.g., 2023-04-01T00:00:00Z). Either use this parameter together with `dateEnd`, or use `dateRange`.
sortOrderstringSort order (ascending or descending).one of
ASC · DESCinvolvedAsnnumberFilter by ASN involved (as hijacker or victim) in a BGP event.
involvedCountrystringFilter by country code of the involved AS in a BGP event.
get_bgp_route_statsRetrieve BGP routing table statistics including number of routes, origin ASes, and more.2 params
Retrieve BGP routing table statistics including number of routes, origin ASes, and more.
Parameters* required
asnnumberAutonomous System Number (ASN), must be a positive number.
locationstringFilters results by location. Specify a valid alpha-2 location code.
get_bots_dataRetrieve bot traffic data including trends by bot name, operator, category, and kind. Covers AI crawlers, search engines, monitoring bots, and more.13 params
Retrieve bot traffic data including trends by bot name, operator, category, and kind. Covers AI crawlers, search engines, monitoring bots, and more.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
botarrayFilter results by bot name.
botKindarrayFilter results by bot kind (AGENT or BOT).
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
continentarrayFilters results by continent. Provide an array of alpha-2 continent codes (e.g., "EU", "NA"). Prefix a code with `-` to exclude it (e.g., ["-EU", "NA"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: ["EU", "EU"] with dateRange: ["7d", "7dcontrol"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of bot data to retrieve.one of
timeseries · summary/bot · summary/bot_kind · summary/bot_operator · summary/bot_category · timeseries_groups/botbotCategoryarrayFilter results by bot category.
botOperatorarrayFilter results by bot operator (e.g., Google, Microsoft, OpenAI).
limitPerGroupintegerLimits the number of items per group. Extra items appear grouped under "other".
botVerificationStatusarrayFilter results by bot verification status.
get_certificate_transparency_dataRetrieve Certificate Transparency (CT) log data. CT provides visibility into SSL/TLS certificates issued for domains, useful for security monitoring.13 params
Retrieve Certificate Transparency (CT) log data. CT provides visibility into SSL/TLS certificates issued for domains, useful for security monitoring.
Parameters* required
caarrayFilter results by certificate authority.
tldarrayFilter results by top-level domain (e.g., "com", "org").
caOwnerarrayFilter results by certificate authority owner.
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
durationarrayFilter results by certificate duration.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of Certificate Transparency data to retrieve.one of
timeseries · summary/ca · summary/ca_owner · summary/duration · summary/entry_type · summary/expiration_statusentryTypearrayFilter results by entry type (certificate vs. pre-certificate).
limitPerGroupintegerLimits the number of items per group. Extra items appear grouped under "other".
normalizationstringNormalization method applied to results. timeseries_groups accepts RAW_VALUES or PERCENTAGE; summary accepts RAW_VALUES or PERCENTAGE. See https://developers.cloudflare.com/radar/concepts/normalization/one of
RAW_VALUES · PERCENTAGEvalidationLevelarrayFilter results by validation level (DV, OV, EV).
publicKeyAlgorithmarrayFilter results by public key algorithm.
get_netflows_dataRetrieve NetFlows traffic data showing network traffic patterns. Supports filtering by ADM1 (administrative level 1, e.g., states/provinces) via geoId.11 params
Retrieve NetFlows traffic data showing network traffic patterns. Supports filtering by ADM1 (administrative level 1, e.g., states/provinces) via geoId.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
geoIdarrayFilters results by Geolocation (ADM1 - administrative level 1, e.g., states/provinces). Provide an array of GeoNames IDs. Prefix with `-` to exclude. Example: ["2267056", "-360689"] includes Lisbon area but excludes another region. IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same region across time periods, repeat the GeoID (e.g., geoId: ["2267056", "2267056"] with dateRange: ["7d", "7dcontrol"]). Using a single geoId with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all regions.
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
productarrayFilter results by network traffic product type.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
continentarrayFilters results by continent. Provide an array of alpha-2 continent codes (e.g., "EU", "NA"). Prefix a code with `-` to exclude it (e.g., ["-EU", "NA"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: ["EU", "EU"] with dateRange: ["7d", "7dcontrol"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of NetFlows data to retrieve.one of
summary/adm1 · summary/as · summary/location · summary/product · timeseries · timeseries_groups/adm1limitPerGroupintegerLimits the number of items per group. Extra items appear grouped under "other".
normalizationstringNormalization method applied to results. timeseries accepts PERCENTAGE_CHANGE or MIN0_MAX; timeseries_groups accepts PERCENTAGE or MIN0_MAX. See https://developers.cloudflare.com/radar/concepts/normalization/one of
PERCENTAGE_CHANGE · MIN0_MAX · PERCENTAGElist_originsList cloud provider origins (hyperscalers) available in Cloud Observatory. Returns Amazon (AWS), Google (GCP), Microsoft (Azure), and Oracle (OCI) with their available regions.2 params
List cloud provider origins (hyperscalers) available in Cloud Observatory. Returns Amazon (AWS), Google (GCP), Microsoft (Azure), and Oracle (OCI) with their available regions.
Parameters* required
limitnumberoffsetnumberget_origin_detailsGet details for a specific cloud provider origin, including all available regions.1 params
Get details for a specific cloud provider origin, including all available regions.
Parameters* required
slugstringThe cloud provider origin to query. Supported values: AMAZON (AWS), GOOGLE (GCP), MICROSOFT (Azure), ORACLE (OCI).one of
AMAZON · GOOGLE · MICROSOFT · ORACLEget_origins_dataRetrieve cloud provider (AWS, GCP, Azure, OCI) performance metrics. Supports timeseries, summaries grouped by region/success_rate/percentile, and grouped timeseries.9 params
Retrieve cloud provider (AWS, GCP, Azure, OCI) performance metrics. Supports timeseries, summaries grouped by region/success_rate/percentile, and grouped timeseries.
Parameters* required
metricstringThe performance metric to retrieve. Only valid when dimension is timeseries or percentile. CONNECTION_FAILURES: Number of failed connections. REQUESTS: Total request count. RESPONSE_HEADER_RECEIVE_DURATION: Time to receive response headers (ms). TCP_HANDSHAKE_DURATION: TCP handshake time (ms). TCP_RTT: TCP round-trip time (ms). TLS_HANDSHAKE_DURATION: TLS handshake time (ms).one of
CONNECTION_FAILURES · REQUESTS · RESPONSE_HEADER_RECEIVE_DURATION · TCP_HANDSHAKE_DURATION · TCP_RTT · TLS_HANDSHAKE_DURATIONoriginarrayArray of cloud provider origins to query. At least one origin must be specified.
regionarrayFilters results by cloud provider region. Example regions: us-east-1, eu-west-1, ap-southeast-1.
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of origins data to retrieve. timeseries: Raw time series data. Requires setting the metric parameter.summary/*: Aggregated data grouped by dimension. timeseriesGroups/*: Time series grouped by dimension. REGION: Group by cloud provider region (e.g., us-east-1). SUCCESS_RATE: Group by connection success rate. PERCENTILE: Group by performance percentiles (p50, p90, p99). Requires setting the metric parameter.one of
timeseries · summary/REGION · summary/SUCCESS_RATE · summary/PERCENTILE · timeseriesGroups/REGION · timeseriesGroups/SUCCESS_RATElimitPerGroupintegerLimits the number of items per group. Extra items appear grouped under "other".
normalizationstringNormalization method applied to results. timeseries_groups accepts PERCENTAGE or MIN0_MAX. See https://developers.cloudflare.com/radar/concepts/normalization/one of
PERCENTAGE · MIN0_MAXget_robots_txt_dataRetrieve robots.txt analysis data. Shows how websites configure crawler access rules, particularly for AI crawlers. Useful for understanding web crawler policies across domains.12 params
Retrieve robots.txt analysis data. Shows how websites configure crawler access rules, particularly for AI crawlers. Useful for understanding web crawler policies across domains.
Parameters* required
datearrayFilters results by date.
limitnumberdateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
patternstringFilter by pattern matching type (FULLY or PARTIALLY matched).one of
FULLY · PARTIALLYdateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of robots.txt data to retrieve.one of
summary/user_agent · timeseries_groups/user_agent · top/domain_categories · top/user_agents/directivedirectivestringFilter by robots.txt directive type (ALLOW or DISALLOW).one of
ALLOW · DISALLOWlimitPerGroupintegerLimits the number of items per group. Extra items appear grouped under "other".
normalizationstringNormalization method applied to results. timeseries_groups accepts PERCENTAGE. See https://developers.cloudflare.com/radar/concepts/normalization/one of
PERCENTAGEdomainCategoryarrayFilter by domain categories.
userAgentCategorystringFilter by user agent category (currently only AI is supported).one of
AIget_bots_crawlers_dataRetrieve web crawler HTTP request data. Shows crawler traffic patterns by client type, user agent, referrer, and industry. Useful for analyzing crawler behavior and traffic distribution.10 params
Retrieve web crawler HTTP request data. Shows crawler traffic patterns by client type, user agent, referrer, and industry. Useful for analyzing crawler behavior and traffic distribution.
Parameters* required
formatstringFormat for crawler data: summary or time series grouped data.one of
summary · timeseries_groupsdateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
industryarrayFilter by industry classification.
verticalarrayFilter by industry vertical.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension for crawler data. CLIENT_TYPE: crawler type, USER_AGENT: crawler user agent, REFERER: referrer analysis, CRAWL_REFER_RATIO: crawl to referrer ratio, VERTICAL: industry vertical, INDUSTRY: industry classification.one of
CLIENT_TYPE · USER_AGENT · REFERER · CRAWL_REFER_RATIO · VERTICAL · INDUSTRYclientTypearrayFilter by client type.
botOperatorarrayFilter results by bot operator (e.g., Google, Microsoft, OpenAI).
limitPerGroupintegerLimits the number of items per group. Extra items appear grouped under "other".
list_botsList known bots with their details. Includes AI crawlers, search engines, monitoring bots, and more. Filter by category, operator, kind, or verification status.6 params
List known bots with their details. Includes AI crawlers, search engines, monitoring bots, and more. Filter by category, operator, kind, or verification status.
Parameters* required
kindstringFilter by bot kind.one of
AGENT · BOTlimitnumberoffsetnumberbotCategorystringFilter by bot category.one of
SEARCH_ENGINE_CRAWLER · SEARCH_ENGINE_OPTIMIZATION · MONITORING_AND_ANALYTICS · ADVERTISING_AND_MARKETING · SOCIAL_MEDIA_MARKETING · PAGE_PREVIEWbotOperatorstringFilter by bot operator name.
botVerificationStatusstringFilter by verification status.one of
VERIFIEDget_bot_detailsGet detailed information about a specific bot by its slug identifier.1 params
Get detailed information about a specific bot by its slug identifier.
Parameters* required
botSlugstringThe bot slug identifier (e.g., "googlebot", "bingbot").
get_leaked_credentials_dataRetrieve trends in HTTP authentication requests and compromised credential detection. Shows distribution by compromised status and bot class.9 params
Retrieve trends in HTTP authentication requests and compromised credential detection. Shows distribution by compromised status and bot class.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
botClassarrayFilter by bot class.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
continentarrayFilters results by continent. Provide an array of alpha-2 continent codes (e.g., "EU", "NA"). Prefix a code with `-` to exclude it (e.g., ["-EU", "NA"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: ["EU", "EU"] with dateRange: ["7d", "7dcontrol"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of leaked credentials data to retrieve.one of
timeseries · summary/compromised · summary/bot_class · timeseries_groups/compromised · timeseries_groups/bot_classcompromisedarrayFilter by compromised status.
get_as112_dataRetrieve AS112 DNS sink hole data. AS112 handles reverse DNS lookups for private IP addresses (RFC 1918). Useful for analyzing DNS misconfiguration patterns.9 params
Retrieve AS112 DNS sink hole data. AS112 handles reverse DNS lookups for private IP addresses (RFC 1918). Useful for analyzing DNS misconfiguration patterns.
Parameters* required
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
protocolarrayFilter by DNS protocol (UDP/TCP).
continentarrayFilters results by continent. Provide an array of alpha-2 continent codes (e.g., "EU", "NA"). Prefix a code with `-` to exclude it (e.g., ["-EU", "NA"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: ["EU", "EU"] with dateRange: ["7d", "7dcontrol"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringDimension indicating the type and format of AS112 data to retrieve. AS112 is a DNS sink hole for reverse DNS lookups of private IP addresses.one of
timeseries · summary/dnssec · summary/edns · summary/ip_version · summary/protocol · summary/query_typequeryTypearrayFilter by DNS query type.
responseCodearrayFilter by DNS response code.
list_geolocationsList available geolocations (ADM1 - administrative divisions like states/provinces). Use this to find GeoNames IDs for filtering HTTP and NetFlows data by region.4 params
List available geolocations (ADM1 - administrative divisions like states/provinces). Use this to find GeoNames IDs for filtering HTTP and NetFlows data by region.
Parameters* required
geoIdstringFilter by specific GeoNames ID.
limitnumberoffsetnumberlocationstringFilters results by location. Specify a valid alpha-2 location code.
get_geolocation_detailsGet details for a specific geolocation by its GeoNames ID.1 params
Get details for a specific geolocation by its GeoNames ID.
Parameters* required
geoIdstringGeoNames ID for the geolocation (e.g., "2267056" for Lisbon).
get_tcp_resets_timeouts_dataRetrieve TCP connection quality metrics including resets and timeouts. Useful for understanding connection reliability across networks and locations.7 params
Retrieve TCP connection quality metrics including resets and timeouts. Useful for understanding connection reliability across networks and locations.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
continentarrayFilters results by continent. Provide an array of alpha-2 continent codes (e.g., "EU", "NA"). Prefix a code with `-` to exclude it (e.g., ["-EU", "NA"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: ["EU", "EU"] with dateRange: ["7d", "7dcontrol"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
dimensionstringFormat for TCP resets/timeouts data: summary or time series grouped data.one of
summary · timeseries_groupsget_annotationsRetrieve annotations including Internet events, outages, and anomalies from various Cloudflare data sources.9 params
Retrieve annotations including Internet events, outages, and anomalies from various Cloudflare data sources.
Parameters* required
asnnumberAutonomous System Number (ASN), must be a positive number.
limitnumberoffsetnumberdateEndstringEnd date in ISO 8601 format (e.g., 2023-04-30T23:59:59Z). Either use this parameter together with `dateStart`, or use `dateRange`.
locationstringFilters results by location. Specify a valid alpha-2 location code.
dateRangestringFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters).
dateStartstringStart date in ISO 8601 format (e.g., 2023-04-01T00:00:00Z). Either use this parameter together with `dateEnd`, or use `dateRange`.
eventTypestringFilter annotations by event type.one of
EVENT · GENERAL · OUTAGE · PARTIAL_PROJECTION · PIPELINE · TRAFFIC_ANOMALYdataSourcestringFilter annotations by data source.one of
ALL · AI_BOTS · AI_GATEWAY · BGP · BOTS · CONNECTION_ANOMALYget_outagesRetrieve Internet outages and anomalies. Provides information about detected connectivity issues across ASes and locations.7 params
Retrieve Internet outages and anomalies. Provides information about detected connectivity issues across ASes and locations.
Parameters* required
asnnumberAutonomous System Number (ASN), must be a positive number.
limitnumberoffsetnumberdateEndstringEnd date in ISO 8601 format (e.g., 2023-04-30T23:59:59Z). Either use this parameter together with `dateStart`, or use `dateRange`.
locationstringFilters results by location. Specify a valid alpha-2 location code.
dateRangestringFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters).
dateStartstringStart date in ISO 8601 format (e.g., 2023-04-01T00:00:00Z). Either use this parameter together with `dateEnd`, or use `dateRange`.
list_ct_authoritiesList Certificate Authorities (CAs) tracked in Certificate Transparency logs.2 params
List Certificate Authorities (CAs) tracked in Certificate Transparency logs.
Parameters* required
limitnumberoffsetnumberget_ct_authority_detailsGet details for a specific Certificate Authority by its SHA256 fingerprint.1 params
Get details for a specific Certificate Authority by its SHA256 fingerprint.
Parameters* required
caSlugstringThe Certificate Authority SHA256 fingerprint (64 hexadecimal characters).
list_ct_logsList Certificate Transparency logs.2 params
List Certificate Transparency logs.
Parameters* required
limitnumberoffsetnumberget_ct_log_detailsGet details for a specific Certificate Transparency log by its slug.1 params
Get details for a specific Certificate Transparency log by its slug.
Parameters* required
logSlugstringThe Certificate Transparency log slug identifier.
get_bgp_timeseriesRetrieve BGP updates time series data. Shows BGP announcement and withdrawal patterns over time.6 params
Retrieve BGP updates time series data. Shows BGP announcement and withdrawal patterns over time.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
prefixarrayFilter by IP prefix(es).
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
updateTypearrayFilter by BGP update type (ANNOUNCEMENT or WITHDRAWAL).
get_bgp_top_asesGet top Autonomous Systems by BGP update count.7 params
Get top Autonomous Systems by BGP update count.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
limitnumberprefixarrayFilter by IP prefix(es).
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
updateTypearrayFilter by BGP update type (ANNOUNCEMENT or WITHDRAWAL).
get_bgp_top_prefixesGet top IP prefixes by BGP update count.6 params
Get top IP prefixes by BGP update count.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
limitnumberdateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
updateTypearrayFilter by BGP update type (ANNOUNCEMENT or WITHDRAWAL).
get_bgp_moasGet Multi-Origin AS (MOAS) prefixes. MOAS occurs when a prefix is announced by multiple ASes, which can indicate hijacking or legitimate anycast.3 params
Get Multi-Origin AS (MOAS) prefixes. MOAS occurs when a prefix is announced by multiple ASes, which can indicate hijacking or legitimate anycast.
Parameters* required
originintegerFilter by origin ASN.
prefixstringFilter by IP prefix (e.g., "1.1.1.0/24").
invalidOnlybooleanOnly return invalid MOAS prefixes.
get_bgp_pfx2asGet prefix-to-ASN mapping. Useful for looking up which AS announces a given IP prefix.4 params
Get prefix-to-ASN mapping. Useful for looking up which AS announces a given IP prefix.
Parameters* required
originintegerFilter by origin ASN.
prefixstringFilter by IP prefix (e.g., "1.1.1.0/24").
rpkiStatusstringFilter by RPKI validation status.one of
VALID · INVALID · UNKNOWNlongestPrefixMatchbooleanWhether to use longest prefix match.
get_bgp_ip_space_timeseriesRetrieve announced IP address space time series data. Shows the count of announced IPv4 /24s and IPv6 /48s over time. Essential for monitoring BGP route withdrawals, IPv6 address space changes, and detecting significant routing events by ASN or country.6 params
Retrieve announced IP address space time series data. Shows the count of announced IPv4 /24s and IPv6 /48s over time. Essential for monitoring BGP route withdrawals, IPv6 address space changes, and detecting significant routing events by ASN or country.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
dateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
ipVersionarrayFilters results by IP version (IPv4 vs. IPv6). Useful for monitoring IPv6 address space specifically.
get_bgp_routes_realtimeGet real-time BGP routes for a specific IP prefix using public route collectors (RouteViews and RIPE RIS). Shows current routing state including AS paths, RPKI validation status, and visibility across peers. Useful for troubleshooting routing issues and verifying route announc...1 params
Get real-time BGP routes for a specific IP prefix using public route collectors (RouteViews and RIPE RIS). Shows current routing state including AS paths, RPKI validation status, and visibility across peers. Useful for troubleshooting routing issues and verifying route announc...
Parameters* required
prefixstringFilter by IP prefix (e.g., "1.1.1.0/24").
get_as_setGet IRR AS-SETs that an Autonomous System is a member of. AS-SETs are used in routing policies.1 params
Get IRR AS-SETs that an Autonomous System is a member of. AS-SETs are used in routing policies.
Parameters* required
asnnumberAutonomous System Number (ASN), must be a positive number.
get_as_relationshipsGet AS-level relationships for an Autonomous System. Shows peer, upstream, and downstream relationships with other ASes.2 params
Get AS-level relationships for an Autonomous System. Shows peer, upstream, and downstream relationships with other ASes.
Parameters* required
asnnumberAutonomous System Number (ASN), must be a positive number.
asn2integerOptional second ASN to check specific relationship.
list_tldsList top-level domains (TLDs) including generic, country-code, and sponsored TLDs. Filter by type or manager.5 params
List top-level domains (TLDs) including generic, country-code, and sponsored TLDs. Filter by type or manager.
Parameters* required
tldstringFilters results by top-level domain. Specify a comma-separated list of TLDs.
limitnumberoffsetnumbermanagerstringFilters results by TLD manager (e.g., "VeriSign Global Registry Services").
tldTypestringFilters results by TLD type.one of
GENERIC · COUNTRY_CODE · GENERIC_RESTRICTED · INFRASTRUCTURE · SPONSOREDget_tld_detailsGet detailed information about a specific top-level domain (TLD).1 params
Get detailed information about a specific top-level domain (TLD).
Parameters* required
tldstringTop-level domain (e.g., "com", "org", "net").
get_domains_ranking_timeseriesGet domain ranking timeseries data. Track how specific domains rank over time.7 params
Get domain ranking timeseries data. Track how specific domains rank over time.
Parameters* required
limitnumberdateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
domainsarrayFilters results by domain name. Specify an array of domain names to track.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
domainCategoryarrayFilters results by domain category (e.g., "News & Media", "Technology").
get_speed_histogramGet speed test histogram data. Shows distribution of speed test results for bandwidth, latency, or jitter.6 params
Get speed test histogram data. Shows distribution of speed test results for bandwidth, latency, or jitter.
Parameters* required
asnarrayFilters results by ASN. Provide an array of ASN strings. Prefix with `-` to exclude (e.g., ["-174", "3356"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: ["13335", "13335"] with dateRange: ["7d", "7dcontrol"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.
metricstringMetrics to be returned in the histogram. Defaults to BANDWIDTH.one of
BANDWIDTH · LATENCY · JITTERdateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
locationarrayFilters results by location. Provide an array of alpha-2 country codes (e.g., "US", "PT"). Prefix a code with `-` to exclude it (e.g., ["-US", "PT"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., ["7d", "7dcontrol"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: ["PT", "PT"] with dateRange: ["7d", "7dcontrol"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
continentarrayFilters results by continent. Provide an array of alpha-2 continent codes (e.g., "EU", "NA"). Prefix a code with `-` to exclude it (e.g., ["-EU", "NA"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: ["EU", "EU"] with dateRange: ["7d", "7dcontrol"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.
bucketSizeintegerSpecifies the width for every bucket in the histogram.
get_internet_services_timeseriesTrack internet service ranking changes over time. Useful for monitoring how services like ChatGPT, Google, etc. rank over time.5 params
Track internet service ranking changes over time. Useful for monitoring how services like ChatGPT, Google, etc. rank over time.
Parameters* required
limitnumberdateEndarrayEnd of the date range. Either use this parameter together with `dateStart`, or use `dateRange`.
dateRangearrayFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: ["7d", "7dcontrol"] and location: ["PT", "PT"], the first period uses PT and the control period also uses PT. If you only provide location: ["PT"], only the first period is filtered by PT while the control period defaults to worldwide data.
dateStartarrayStart of the date range. Either use this parameter together with `dateEnd` or use `dateRange`.
serviceCategoryarrayFilters results by Internet service category.
get_outages_by_locationGet outage counts aggregated by location. Useful for identifying which countries have the most Internet outages.4 params
Get outage counts aggregated by location. Useful for identifying which countries have the most Internet outages.
Parameters* required
limitnumberdateEndstringEnd date in ISO 8601 format (e.g., 2023-04-30T23:59:59Z). Either use this parameter together with `dateStart`, or use `dateRange`.
dateRangestringFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters).
dateStartstringStart date in ISO 8601 format (e.g., 2023-04-01T00:00:00Z). Either use this parameter together with `dateEnd`, or use `dateRange`.
get_traffic_anomalies_by_locationGet traffic anomalies aggregated by location. Shows which countries have the most detected outage signals, automatically detected by Radar.5 params
Get traffic anomalies aggregated by location. Shows which countries have the most detected outage signals, automatically detected by Radar.
Parameters* required
limitnumberstatusstringFilter by anomaly verification status.one of
VERIFIED · UNVERIFIEDdateEndstringEnd date in ISO 8601 format (e.g., 2023-04-30T23:59:59Z). Either use this parameter together with `dateStart`, or use `dateRange`.
dateRangestringFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters).
dateStartstringStart date in ISO 8601 format (e.g., 2023-04-01T00:00:00Z). Either use this parameter together with `dateEnd`, or use `dateRange`.
get_bgp_routing_table_asesList all ASes in global routing tables with routing statistics (prefix counts, IPv4/IPv6 address count, RPKI validation status). Data comes from public BGP MRT archives.4 params
List all ASes in global routing tables with routing statistics (prefix counts, IPv4/IPv6 address count, RPKI validation status). Data comes from public BGP MRT archives.
Parameters* required
limitnumbersortBystringSort ASes by: cone (customer cone size), pfxs (total prefixes), ipv4/ipv6 (address count), or rpki_* (RPKI validation status).one of
cone · pfxs · ipv4 · ipv6 · rpki_valid · rpki_invalidlocationstringFilters results by location. Specify a valid alpha-2 location code.
sortOrderstringSort order (ascending or descending).one of
ASC · DESCget_bgp_top_ases_by_prefixesGet top ASes ordered by announced prefix count. Useful for understanding which networks have the largest routing footprint. Data comes from public BGP MRT archives and updates every 2 hours.2 params
Get top ASes ordered by announced prefix count. Useful for understanding which networks have the largest routing footprint. Data comes from public BGP MRT archives and updates every 2 hours.
Parameters* required
limitnumbercountrystringFilter by country (alpha-2 code).
get_bgp_rpki_aspa_snapshotRetrieve a snapshot of current or historical RPKI ASPA (Autonomous System Provider Authorization) objects. ASPA objects define which ASNs are authorized upstream providers for a customer ASN, helping prevent route leaks and hijacks.9 params
Retrieve a snapshot of current or historical RPKI ASPA (Autonomous System Provider Authorization) objects. ASPA objects define which ASNs are authorized upstream providers for a customer ASN, helping prevent route leaks and hijacks.
Parameters* required
rirstringFilter by Regional Internet Registry (RIR).one of
AFRINIC · APNIC · ARIN · LACNIC · RIPE_NCCdatestringDate for historical ASPA snapshot (ISO 8601 format, e.g. 2024-01-15).
pageintegerPage number for paginated ASPA results.
sortBystringSort ASPA results by specified field.one of
customerAsn · providerAsnlocationstringFilter by country (alpha-2 code).
per_pageintegerNumber of results per page for ASPA queries (1-100).
sortOrderstringSort order (ascending or descending).one of
ASC · DESCcustomerAsnintegerFilter by customer ASN (the ASN that authorizes upstream providers).
providerAsnintegerFilter by provider ASN (the authorized upstream provider ASN).
get_bgp_rpki_aspa_changesRetrieve RPKI ASPA changes over time, including additions, removals, and modifications of ASPA objects.12 params
Retrieve RPKI ASPA changes over time, including additions, removals, and modifications of ASPA objects.
Parameters* required
rirstringFilter by Regional Internet Registry (RIR).one of
AFRINIC · APNIC · ARIN · LACNIC · RIPE_NCCpageintegerPage number for paginated ASPA results.
sortBystringSort ASPA results by specified field.one of
customerAsn · providerAsndateEndstringEnd date in ISO 8601 format (e.g., 2023-04-30T23:59:59Z). Either use this parameter together with `dateStart`, or use `dateRange`.
locationstringFilter by country (alpha-2 code).
per_pageintegerNumber of results per page for ASPA queries (1-100).
dateRangestringFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters).
dateStartstringStart date in ISO 8601 format (e.g., 2023-04-01T00:00:00Z). Either use this parameter together with `dateEnd`, or use `dateRange`.
sortOrderstringSort order (ascending or descending).one of
ASC · DESCchangeTypestringFilter by type of ASPA change.one of
addition · removal · modificationcustomerAsnintegerFilter by customer ASN (the ASN that authorizes upstream providers).
providerAsnintegerFilter by provider ASN (the authorized upstream provider ASN).
get_bgp_rpki_aspa_timeseriesRetrieve a timeseries of RPKI ASPA object counts over time.5 params
Retrieve a timeseries of RPKI ASPA object counts over time.
Parameters* required
rirstringFilter by Regional Internet Registry (RIR).one of
AFRINIC · APNIC · ARIN · LACNIC · RIPE_NCCdateEndstringEnd date in ISO 8601 format (e.g., 2023-04-30T23:59:59Z). Either use this parameter together with `dateStart`, or use `dateRange`.
locationstringFilter by country (alpha-2 code).
dateRangestringFilters results by date range. For example, use `7d` and `7dcontrol` to compare this week with the previous week. Use this parameter or set specific start and end dates (`dateStart` and `dateEnd` parameters).
dateStartstringStart date in ISO 8601 format (e.g., 2023-04-01T00:00:00Z). Either use this parameter together with `dateEnd`, or use `dateRange`.
search_url_scansSearch URL scans using ElasticSearch-like query syntax. Examples: 'page.domain:example.com', 'verdicts.malicious:true', 'page.asn:AS24940 AND hash:xxx', 'apikey:me AND date:[2025-01 TO 2025-02]'2 params
Search URL scans using ElasticSearch-like query syntax. Examples: 'page.domain:example.com', 'verdicts.malicious:true', 'page.asn:AS24940 AND hash:xxx', 'apikey:me AND date:[2025-01 TO 2025-02]'
Parameters* required
sizeintegerLimit the number of results (1-100, default 10).default: 10
querystringElasticSearch-like query to filter scans. Examples: 'page.domain:example.com', 'verdicts.malicious:true', 'page.asn:AS24940', 'date:[2025-01 TO 2025-02]'
create_url_scanSubmit a URL to scan. Returns the scan UUID which can be used to retrieve results.3 params
Submit a URL to scan. Returns the scan UUID which can be used to retrieve results.
Parameters* required
urlstringA valid URL including protocol (e.g., "https://example.com").
visibilitystringScan visibility. Public scans appear in search results. Unlisted scans require the scan ID to access.one of
Public · Unlisteddefault: PublicscreenshotResolutionstringScreenshot resolution/device type.one of
desktop · mobile · tabletdefault: desktopget_url_scanGet the results of a URL scan by its UUID. Returns detailed information including verdicts, page info, requests, cookies, and more.1 params
Get the results of a URL scan by its UUID. Returns detailed information including verdicts, page info, requests, cookies, and more.
Parameters* required
scanIdstringThe UUID of the scan.
get_url_scan_screenshotGet the screenshot URL for a completed scan.2 params
Get the screenshot URL for a completed scan.
Parameters* required
scanIdstringThe UUID of the scan.
resolutionstringScreenshot resolution/device type.one of
desktop · mobile · tabletdefault: desktopget_url_scan_harGet the HAR (HTTP Archive) data for a completed scan. Contains detailed network request/response information.1 params
Get the HAR (HTTP Archive) data for a completed scan. Contains detailed network request/response information.
Parameters* required
scanIdstringThe UUID of the scan.
mcp-cloudflare-radar
Cloudflare Radar MCP — internet observatory (traffic, attacks, BGP, quality)
Part of Pipeworx — an MCP gateway connecting AI agents to 673+ live data sources.
Tools
| Tool | Description |
|---|
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"cloudflare-radar": {
"url": "https://gateway.pipeworx.io/cloudflare-radar/mcp"
}
}
}
Or connect to the full Pipeworx gateway for access to all 673+ data sources:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English:
ask_pipeworx({ question: "your question about Cloudflare Radar data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
