User-Agent
Declared by 82 providers across 5930 published specification files in the APIs.io network.
Spelled 2 ways
HTTP field names are case-insensitive (RFC 9110 §5.1), so every spelling below is the same header on the wire. A contract is not the wire: generated clients key off the string, and a developer reading two of these sees two different headers.
User-Agentuser-agent
The registry
| Status | permanent |
|---|---|
| Reference | RFC 9110, Section 10.1.5: HTTP Semantics |
Providers declaring it (82)
adobe-suite affirm amplitude apifreaks-api-hub-for-developers apis-io balad-corp bancontact bazaarvoice brewpage bright-pattern brightcove cash-app chargebee cliniko clover coinme contentstack contextdev databento decart deliverect depict depictai eclipse engineering-platform expedia-group figure-technology-solutions finos github gocardless have-i-been-pwned helika helpscout hevn-inc intercom ipgeolocation jira just-eat keap keycorp klarna koala-io leonardo-ai lightspeed-pos line mailgun microsoft-azure moloco moogsoft mtn-group mycarrier national-weather-service noaa noaa-gov okta open-food-facts optimizely paystack plausible podcastindex postman punchh pydantic-ai ramp razorpay ringcentral sageox shutterstock small-improvements snowflake soveren spaitial-ai squarespace thingsboard todoist tollbit transmit-security ubuntu viator viridi-parente weather-gov worldpay
Explore
All headers Agent & Bot Identity Guidance on headers.apievangelist.com
Work with this as data
Every header here is available over the APIs.io API and to AI agents over MCP. HTTP Headers is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.