# AwarioSmartBot

> Awario's brand-monitoring crawler. It documents one request per three seconds, honours Crawl-delay, and states it does not use consecutive IP blocks so identification is by user-agent only.

| field | value |
|---|---|
| operator | Awario |
| category | Corpus and dataset builders |
| robots.txt token | `AwarioSmartBot` |
| user-agent contains | `AwarioSmartBot` |
| robots.txt | obeys robots.txt (documented) |
| verify by | no published verification method |
| published IP ranges | none published |
| prefixes mirrored | 0 IPv4 / 0 IPv6 |
| operator docs | https://awario.com/bots.html |
| last reviewed | 2026-09-14 |

## What blocking it costs you

Mentions of brands on your pages stop being surfaced to the people monitoring them — including, quite possibly, your own.

## Full user-agent string

```
AwarioSmartBot/1.0 (+https://awario.com/bots.html; bots@awario.com)
```

## Block it

```
User-agent: AwarioSmartBot
Disallow: /
```

## Allow it

```
User-agent: AwarioSmartBot
Allow: /
```

## Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

- **How do I prove a request really is AwarioSmartBot?**  
  `curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=awariosmartbot&s=client-dossiers'`  
  The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error.

JSON: https://www.pathwren.workers.dev/crawler/awariosmartbot.json · index: https://www.pathwren.workers.dev/llms.txt