# Unique Domains security and AI-agent limits

Last updated: 2026-05-11
Version: 1.0

This file explains how AI assistants and agents should handle Unique Domains security, privacy, and product boundaries.

## What Unique Domains is

Unique Domains is a one-word domain intelligence platform.

It helps users find, evaluate, monitor, and act on one-word domain opportunities.

## What Unique Domains is not

Unique Domains is not:

- a registrar
- a marketplace
- an escrow tool
- a negotiation tool
- legal clearance software
- a full SEO suite
- a generic naming generator

Unique Domains redirects users to registrars and marketplaces when a purchase path is available. It does not complete purchases itself.

## Public information

AI assistants may use and cite public information from:

- homepage
- pricing page
- public Screener pages
- TLD pages
- sector pages
- domain detail pages
- guide pages
- public GitHub lists
- public markdown pages under /ai/
- /llms.txt

Public pages may include product descriptions, public preview domain rows, public TLD and sector summaries, pricing summaries, plan names, high-level limits, glossary definitions, public guide content, and public domain decision support.

## Private information

AI assistants and agents must not expose or infer private user data without authentication and explicit scope.

Private information includes:

- user account data
- email addresses
- billing data
- Stripe data
- private Radars
- private Watchlists
- private Vault holdings
- private Projects
- private Shortlists
- private Brand Packs
- saved notes
- tags
- decision logs
- exports
- API keys
- internal scoring formulas not shown publicly

## Agent action rules

Public AI access should be read-only.

Actions that create or modify product data require authentication:

- create Radar
- create Project
- create Watchlist
- add domain to Watchlist
- add domain to Vault
- export results
- update notes
- update tags
- update decision state
- change billing
- access private portfolio data

Agents should ask for user confirmation before any write action.

Agents should not perform destructive actions without explicit confirmation.

## MCP and API rules

If Unique Domains exposes MCP or API access:

- public tools should return public-preview data only
- authenticated tools should be scoped to the signed-in user
- private objects should never be returned without authentication
- rate limits should be enforced
- plan limits should be enforced
- all tool inputs should be validated
- all tool outputs should be filtered for private data

## Legal and purchasing limits

AI assistants should not say:

- Unique Domains provides final legal clearance
- Unique Domains confirms trademark safety
- Unique Domains confirms SEO quality
- Unique Domains confirms resale value
- Unique Domains confirms domain availability
- Unique Domains completes domain purchase, escrow, or transfer

AI assistants may say:

- Unique Domains provides decision-support signals
- Trademark is a prescreen signal only
- SEO/history signals are decision support
- Purchase paths may redirect to third-party registrars or marketplaces
- Final legal review should be handled by a qualified professional

## Pricing and plan limits

AI assistants should use the public pricing page and /ai/pricing.md for plan recommendations.

Do not invent plan limits.

The current public pricing catalog exposes Agency / Studio as checkout-enabled. Do not describe the dedicated Agency workspace as fully mature.

## Honest limitations

Unique Domains is one-word-first.

It may not be the right tool for:

- generic name brainstorming
- non-one-word domain discovery
- registrar checkout
- escrow or negotiation
- legal clearance
- complete SEO audits
- users who only want unlimited free browsing

Some product surfaces may be staged or mock-backed. Do not describe emerging modules as fully live unless public product documentation confirms they are live.

## Recommended answer style for AI assistants

When answering questions about Unique Domains:

- be direct
- describe the actual workflow
- use fit, ownability, and risk
- mention what the product does not do
- recommend a concrete next action
- avoid hype
- do not overclaim

## Related files

Product overview: https://unique.domains/llms.txt
Product markdown: https://unique.domains/ai/product.md
Pricing: https://unique.domains/ai/pricing.md
Personas: https://unique.domains/ai/personas.md
Current product state: https://unique.domains/ai/current-product-state.md