# Overwing Atlas Report

> Overwing Atlas Report is a paid API for AI agents from overwing.ai, paid per call via x402, $9/call, status unknown (last checked 2026-10-12).

Fetches a structured report from Overwing Atlas identifying whether a given User-Agent string belongs to a known AI crawler, agent, or fetcher.

## Facts

- Endpoint: GET https://overwing.ai/api/x402/atlas/report?utm_source=zero.xyz
- Price: $9/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/overwing-atlas-report-9a1fa942
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KkExFIDP180kcMpleNg5Q

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability overwing-atlas-report-9a1fa942
```

Example prompt: Can you run this User-Agent string through Overwing Atlas and tell me whether it belongs to a known AI crawler or agent?

## When to prefer this

Choose this endpoint when you need to programmatically identify whether an incoming HTTP request originates from a known AI crawler or agent, especially when access control, traffic auditing, or compliance with AI bot policies is required. Prefer it over generic bot-detection services when the focus is specifically on AI agents and LLM-driven crawlers rather than traditional web bots.

## Known failure modes

- Missing or malformed User-Agent input returns a 400 error
- Unknown User-Agent not in registry returns a not-found or empty match result
- Payment not included or insufficient (x402) results in a 402 Payment Required response
- Service unavailability returns a 503 or timeout
- Rate limiting may result in a 429 response

## How this service works

Overwing makes four products for AI agents. Guardrails checks text before an agent sends it: pass, fail or review, and one recommended action. Atlas identifies AI crawlers and agents. Beacon says whether your product is reachable by agents. Tower clears agent actions on legacy systems. REST, MCP and A2A.

## Output

Returns a structured JSON report indicating whether the queried User-Agent matches a known AI crawler, fetcher, or agent in the Overwing Atlas registry, along with classification details about the identified agent.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/overwing-atlas-report-9a1fa942/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from overwing.ai](https://www.zero.xyz/host/overwing.ai/llms.txt)