Traffic Health has two tiers. Both tools work on any network with Traffic Health enabled, but some resources and includes need Traffic Health Premium, marked below and listed in full under Free vs. Premium. A Premium request on a network without Premium does not error: it returns
available: false with reason not_on_plan and a note, and no items or counts, because nothing was checked. If Traffic Health is not enabled at all, both tools return INVALID_ARGUMENT: Traffic Health is not enabled for this network. On a network without Premium, the premium-only types and includes are not listed in the tool descriptions at all, so the model only sees the baseline set. The description a model sees is chosen when it lists tools and is cached by clients; a request for a Premium type on a network without Premium always returns the not_on_plan result.Blocklist reputation covers premium-monitored domains. With Premium, each monitored domain is
basic or premium, up to the plan’s premium_monitored_domain_quota, and blocklist reputation is checked only for the premium ones. reputation_checked on domains, the domain situation and the summary says whether reputation covers them. When it is false, the flag and blocklist fields are omitted: absent means not checked, never “not flagged”.list_traffic_health
Lists Traffic Health resources network-wide, or scoped to a single domain. Settype to choose the resource; omit domain for a network-wide list, or pass it to scope to one domain.
Requires: Traffic Health (Read Only)
Ask for it: “Which of my tracking domains have open remediation tasks?” · “Is any ISP’s traffic to my domains dropping?”
Parameters
Example
Returns
Every list type returns a uniform wrapper:
A Premium type, or
kind=third_party, on a network without Premium returns { "available": false, "reason": "not_on_plan", "note": "..." } in place of this wrapper. See Free vs. Premium.
Gotchas
- Only
uptime_incidentsanddomain_reputationstruly paginate.hostingandssl_certificatesreturn a single page of 50 rows: they reporttotal/has_moreso you can tell the set is truncated, but they neither accept nor returnpage/page_size. Whenhas_moreistrueon one of these, narrow withdomain; there is no page to request.domains,tasksandisp_trendsreturn the full set and omit those fields.ip_reputationsreturns at most 100 incidents and omits them too. Whenhas_moreistrueon a paginated type, page withpageor narrow withdomain,status, orfrom/to. - Parameters that don’t apply to the chosen
typereturn an error, not silence. Passingpage(above 1) orpage_sizeto a non-paginated type,domainto a type that isn’t domain-scoped, orexpires_within_daysto anything butdomains/ssl_certificatesreturnsINVALID_ARGUMENTnaming the types that do accept it. - An empty
isp_trendsresult means no US pair with at least 100 clicks (30 days back) is declining, not that there is no traffic. Only declining pairs are returned, and only when yesterday’s clicks are down against all three comparison days (conversions and revenue are reported but not tested). - Unknown
includenames, an invalidtype, and dates not inYYYY-MM-DDform returnINVALID_ARGUMENTlisting the valid values. Passdomainwithout a scheme (track.acme.com);includeis case-insensitive. - Timestamps are UTC and say so: formatted strings,
YYYY-MM-DD HH:MM:SS UTC(e.g.2026-12-22 14:08:06 UTC). The one exception is theassignments→usagewindow on the other tool, which follows the network timezone and has no suffix. Fields are omitted when unset. - Expiry comes with a countdown.
registration_expires_in_daysandcertificate_expires_in_daysare whole days from now until the matching_expires_at; a negative value means already expired. - For a domain’s identity and config (ID lookup, primary/assignable flags, redirect settings) rather than its health, use
get_entity/list_entitieswithtype=tracking_domain— that works on networks without Traffic Health too.
summary
summary
A single object — not wrapped in the list envelope.
The blocklist counts cover premium-monitored domains only.
domains
domains
tasks
tasks
uptime_incidents
uptime_incidents
hosting and ssl_certificates
hosting and ssl_certificates
hostingssl_certificatesget_traffic_health_domain
Returns the full Traffic Health picture for one domain in a single call — its current situation, plus on request its incidents, tasks, reputation, and configuration. Requires: Traffic Health (Read Only) Ask for it: “What’s going on with track.acme.com, and what’s at risk if it goes down?” Parameters
Example
include="uptime_incidents,tasks,configuration" returns the same.
Includes
Returns
The situation summary is always returned, with or without
include:
www. is resolved for you. Monitored domains are stored under one exact URL. If acme.com is not monitored but www.acme.com is (or the reverse), the lookup retries the other spelling once, and every response carries resolved_domain, the spelling that matched. Compare domains on resolved_domain, not on what you passed in, or one domain can look like two.include is added under its own key:
On a network without Premium, each Premium include comes back as
{ "available": false, "reason": "not_on_plan", "note": "..." } under its key.
An include that cannot be loaded comes back as { "note": "..." } under its key without failing the call (Could not load <include>.). assignments and mismatches apply only to tracking domains: for a URL that is not one of the network’s tracking domains, assignments returns the note Assignments apply only to tracking domains; this URL is not a tracking domain for the network. and mismatches returns No tracking domain found for this URL. usage is omitted when the domain has no traffic row or the lookup fails. The uptime_incidents, domain_reputation and ip_reputation includes return page 1 at the default page size of 100 rows and cannot be paged (no page or page_size is passed through).
The assignments → usage object reports the domain’s traffic and revenue over the trailing 90 days — the practical blast radius if the domain goes down:
Gotchas
- Only monitored domains resolve here. A domain that appears in
list_traffic_health(type=domains)but isn’t monitored returnsINVALID_ARGUMENT: Domain with url … is not present in list of monitored domains. - The
usagewindow follows the network timezone, unlike the UTC timestamps everywhere else in Traffic Health. It carries its owntimezonefield so the two can’t be confused.
Free vs. Premium
A Premium-only request on a network without Premium returns an unchecked result rather than an error. It has no
items or counts, so it cannot be read as a clean, empty list:
reason domain_not_premium_monitored.
Learn more about Traffic Health
See the Everflow Helpdesk for what Traffic Health monitors, when to use it, and how to act on domain incidents and tasks.
