Traffic by client class

Our own request counters, split by what made the request — AI agent, crawler or browser — with MCP tool calls alongside web hits so the two can be compared. These are counts of visits to us, not index data, so no citation block is attached. available is false when the store backing the daily series is not configured, and error then says so.

get/api/traffic

Request

  • Base URL: https://agentdeals.dev
  • URL: https://agentdeals.dev/api/traffic
  • Auth: none required

Response

Traffic counters over several windows

web_vs_mcpobject

Web hits, AI-agent hits and MCP tool calls per window, with the ratios between them. A ratio is null when the denominator is zero.

availableboolean

Whether the daily series has a store behind it. False means only the since-boot counters are meaningful.

errorstring

Why the daily series is unavailable, when it is.

since_boot_by_classobject
since_boot_not_foundinteger
since_boot_redirectsinteger
ai_agent_trigger_familiesobject

Which user agents we read as user-initiated, as search indexing, and as training crawls.

notesstring[]

What each figure does and does not count, including how much of it is our own crawling.

storageobject

Whether the counters are being persisted, and the failures if not.

vendor_seriesobject

State of the per-vendor daily series.

Changes

No recorded changes to this operation across all 1 revision of this API.