Collect Intelligence
The Automation Intelligence API gives you the tools to determine whether traffic is legitimate and should be accepted by your application.
This feature is currently in a Public Preview testing phase. All feedback is welcome! If you encounter any issues, please contact our support team.
The API detects automation tools like AI Agents, AI Assistants, AI Browsers, and other bots. Additionally, it provides IP intelligence like geolocation, residential proxy, VPN and data center detection.
Automation Intelligence is derived from HTTP request metadata that reaches your server. It does not require the use of a JavaScript client-side agent or mobile SDKs to collect device context.
The API is fast, with average response times of less than 30ms, making it a great fit for edge, pre-origin or middleware contexts. The API is platform-agnostic and can be used with different CDN providers, cloud platforms, or any server backend.
Because this API doesn’t require the use of a client-side device collection agent, it doesn’t support device identification via visitor_id and a few Smart Signals derived from deep device telemetry.
Event Retrieval
Events created by the Automation Intelligence API can be fetched via the /v4/events/{event_id} API using the event_id present in the API response.
Fetch all Automation Intelligence API events via the /v4/events?source=edge API.
Authorizations
Add your Secret API Key to the Authorization header using the standard Bearer format: Authorization: Bearer <secret_api_key>
Body
HTTP request metadata (including the HTTP method, headers and IP address) sent by you (your server) to the Fingerprint API for IP and bot analysis. To improve accuracy, retain as much of the original semantics of the HTTP request as possible. For example, preserve the order of the request headers and their capitalization.
At least one of ipv4_address or ipv6_address must be provided; a request with neither is rejected with a 400 error. If both IPv4 and IPv6 are provided, IP intelligence will be provided for each address. If an IPv4-mapped IPv6 address is provided in the ipv6_address request property, the IP intelligence will be provided in the ipv4_address property of the response.
Ordered header entries from the request made to your server. Each entry represents one header line. If one header name appears as multiple lines, send each as a separate item in the array.
Headers that contain authentication or session data must still be included, but with with their value set to an empty string. This includes headers like Authorization and Cookie, but may contain more depending on your specific project, for instance Proxy-Authenticate or X-Api-Key. Omitting the headers entirely changes the shape of the request and can affect detection. Never forward the real secret values.
Whenever possible, we recommend preserving header order and capitalization to provide the best accuracy, however it’s not a strict requirement if your runtime does not maintain http header order or canonicalizes header names.
1The original HTTP method of the request. If supported in your runtime, preserve the original casing.
"GET"
"POST"
"PUT"
"PATCH"
"DELETE"
Absolute URL of the request, without a #fragment suffix. Only HTTP and HTTPS schemes are supported.
"http://example.com"
"https://example.com/checkout?method=card"
Client IPv4 address observed by your server.
"34.162.244.71"
"3.208.0.3"
"173.56.0.4"
Client IPv6 address observed by your server.
"2001:4860:4801:10::1"
"2600:1f42:abcd:5678:9876:fedc:1357:2468"
"2001:4868:85f:1a2b:3c4d:5e6f:7890:abcd"
"::ffff:22a2:f447"
"::ffff:34.162.244.71"
A customer-provided id that was sent with the request.
"somelinkedId"
A customer-provided value or an object that was sent with the identification request or updated later.
Response
OK.
IP and bot analysis for a request submitted through the Automation Intelligence API.
Unique identifier of the user's request. The first portion of the event_id is a unix epoch milliseconds timestamp.
"1708102555327.NLOjmg"
Timestamp of the event with millisecond precision in Unix time.
1708102555327
Details about the request IP address. Has separate fields for v4 and v6 IP address versions.
Identifies how the event was generated.
device- the event was generated by the JS agent or a mobile SDK running on an end-user device.edge- the event was generated by the Automation Intelligence API (/edgeendpoint), analyzing a request intercepted at the edge.
device, edge A customer-provided id that was sent with the request.
"somelinkedId"
A customer-provided value or an object that was sent with the identification request or updated later.
Page URL from which the request was sent.
"https://www.example.com/login"
Extended bot information.
IP address was used by a public proxy provider or belonged to a known recent residential proxy
Confidence level of the proxy detection. If a proxy is not detected, confidence is "high". If it's detected, can be "low", "medium", or "high".
low, medium, high Proxy detection details (present if proxy is true)
VPN or other anonymizing service has been used when sending the request.
A confidence rating for the VPN detection result — "low", "medium", or "high". Depends on the combination of results returned from all VPN detection methods.
low, medium, high