> For the complete documentation index, see [llms.txt](https://docs.seedata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seedata.io/features/seeds/url.md).

# URL

## Format

A unique and trackable URL that is structured to appear as a legitimate link but is specifically designed for monitoring purposes. Issued as a string of text and delivered within a CSV file. Example: <https://sub.domain.com/path>

## Capabilities

1. **Event Raising for Clicks**: The platform will raise an event for any clicks or visits to the seeded URL. Each event includes detailed threat analysis of the visitor’s IP address, user agent, and other metadata.
2. **Observation on the Web**: The platform monitors the open web, deep web, and dark web for mentions or observations of the seeded URL, providing threat analysis on the domain or source where the observation occurs.

## Usage

Plant our URL seeds within your marketing emails, documents, or web pages to detect unauthorized access or malicious activity. It helps in identifying potential threats early by monitoring interactions with these URLs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.seedata.io/features/seeds/url.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.