> ## Documentation Index
> Fetch the complete documentation index at: https://agent-traffic.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Contributing

> Add or fix an agent in the dataset.

Agents change their fetchers often. If you see one that's missing or wrong, open a pull request against [`data/agents.json`](https://github.com/mintlify/agent-traffic/blob/main/data/agents.json).

**1. Pick the category**

Follow [Categories](https://agent-traffic.mintlify.site/concepts/categories.md). If you're unsure, ask whether a person is waiting on this request right now. If one is, it's an `agent`.

**2. Write an anchored pattern**

Patterns are case-insensitive regular expressions anchored on the product token. Bare words like `Cursor` or `Code` aren't accepted, because they match unrelated software.

**3. Add real examples**

Include at least one real user agent from traffic or the operator's documentation. Don't invent one, but replace anything that identifies a customer, like tenant or scan IDs, with a placeholder.

**4. Link verification sources**

Only list sources the operator publishes: IP range JSON, reverse DNS domains or a Web Bot Auth key directory. Use `"runsOn": "user"` for products that fetch from the user's machine.

**5. Run the tests**

```bash theme={null}
pnpm install
pnpm test
```

The tests check that every example classifies as its own entry and matches no other.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.