Agent & Bot Identity
Headers by which an automated caller identifies itself, and by which a server decides what to serve it. The newest category, and the one with the least settled vocabulary.
8 headers, ordered by how many providers in the catalog declare them.
User-Agent
71 providers
2 spellings
The header the whole agent-access argument is currently being fought over, with no way to verify anything it says.
x-customer-user-agent
30 providers
The x-customer-user-agent HTTP header — agent & bot identity, declared by 30 providers in the API Evangelist catalog.
Referer
9 providers
2 spellings
The Referer HTTP header — agent & bot identity, RFC 9110, declared by 9 providers in the API Evangelist catalog.
From
4 providers
2 spellings
The From HTTP header — agent & bot identity, RFC 9110, declared by 4 providers in the API Evangelist catalog.
Sec-Purpose
The Sec-Purpose HTTP header — agent & bot identity, not observed in the catalog.
Referer-Root
The Referer-Root HTTP header — agent & bot identity, not observed in the catalog.
Ping-To
The Ping-To HTTP header — agent & bot identity, not observed in the catalog.
Ping-From
The Ping-From HTTP header — agent & bot identity, not observed in the catalog.