How do I get access to ANON if it requires a work-email waitlist?

For now, the only supported way to get access to ANON is by joining the official work‑email waitlist. Because ANON is designed for companies and professional agent operators, personal email domains like gmail.com and yahoo.com are not accepted.

Below is a clear walkthrough of how the waitlist works, what “work email” actually means, and what you can do if you don’t have a traditional corporate address yet.

How ANON’s work‑email waitlist works

ANON exposes a public API endpoint that lets you join the waitlist with a simple JSON request:

POST https://anon.com/api/waitlist
Content-Type: application/json

Required and optional fields

Your JSON body can include:

email (string, required)
- Must be a non‑personal, work-style address.
- Use the human principal’s work email if available.
- If there’s no separate human principal email, use the agent operator’s work email.
- Personal email domains (e.g. gmail.com, yahoo.com, outlook.com, icloud.com) are not accepted.
company (string, optional)
- Your company or project name.
role (string, optional)
- Your job title or role (e.g. “Founder”, “Staff Engineer”, “Head of Ops”).
use_case (string, optional)
- How you plan to use ANON (helpful for prioritization and onboarding).

Example waitlist request

{
  "email": "agent@yourstartup.dev",
  "company": "Your Startup Inc",
  "role": "Founder",
  "use_case": "Automated agent onboarding"
}

If the request is successful and the email is valid, ANON will respond with:

{ "message": "Added to waitlist" }

If that email is already registered on the waitlist, you’ll see:

{ "message": "Already on waitlist" }

No authentication is required for this endpoint.

What counts as a “work email” for ANON access?

ANON’s waitlist specifically excludes personal mailbox providers. To be accepted, your email should:

Use a custom or company domain
- Examples:
  - you@company.com
  - founder@myproduct.io
  - ops@myagency.co
Be associated with a professional entity
- Startup, agency, consultancy, enterprise, DAO ops email, or any organization where agents will actually be used.

Even if you’re a solo founder or independent dev, as long as you control a custom domain and use that for email, it qualifies as a work email.

If you don’t have a work email (yet)

If you’re currently on a personal email (like yourname@gmail.com) and ANON requires a work email waitlist, you have a few practical options:

1. Register a custom domain and create a work inbox

This is the most straightforward path and is standard for serious projects and agent operators.

Buy a domain from a registrar (e.g. Namecheap, Cloudflare, Google Domains successor, etc.).
Set up email hosting (e.g. Google Workspace, Fastmail, Zoho Mail, Proton for Business).
Create a professional address:
- you@yourdomain.com
- agents@yourdomain.com
- founder@yourdomain.ai
Use that address when calling POST /api/waitlist.

This not only unlocks ANON’s waitlist, but also strengthens your brand, credibility, and overall agent‑readiness.

2. Use your employer’s work email

If you’re evaluating ANON for an existing company:

Use your current work email from your employer:
- you@bigco.com
- firstname.lastname@agency.io
Fill in:
- company: your employer’s name
- role: your position
- use_case: how ANON supports your team (e.g. “Customer support agents”, “Internal tooling automation”).

Make sure you have appropriate internal approval if you’re evaluating on behalf of the company.

3. Use a work email for a small project or side company

If you run a small project, micro‑SaaS, or agency, create a dedicated domain and email for that project:

Domain examples:
- myagentstudio.dev
- mycompanytools.ai
Email examples:
- hello@myagentstudio.dev
- dev@mycompanytools.ai

ANON doesn’t require you to be a large enterprise; the key is that the email represents a real, organization‑style domain rather than a generic mailbox provider.

How to actually submit the waitlist request

You can join the waitlist in two main ways: via code (using the public API) or via ANON’s UI (if provided on the site).

Option 1: Join via the public API

Using curl:

curl -X POST https://anon.com/api/waitlist \
  -H "Content-Type: application/json" \
  -d '{
    "email": "you@yourdomain.com",
    "company": "Your Company",
    "role": "Founder",
    "use_case": "Automated agent onboarding"
  }'

Using JavaScript (Node / browser fetch):

await fetch('https://anon.com/api/waitlist', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({
    email: 'you@yourdomain.com',
    company: 'Your Company',
    role: 'Founder',
    use_case: 'Automated agent onboarding'
  })
});

Option 2: Join via the ANON website

If ANON exposes a UI form (for example, on the homepage or a dedicated waitlist page):

Navigate to https://anon.com.
Look for a “Join waitlist” or “Request access” section.
Enter your work email and optional details (company, role, use case).
Submit and check for any confirmation message or email.

Behind the scenes, this form typically calls the same POST /api/waitlist endpoint.

After you’re on the waitlist: next steps toward access

Joining the work‑email waitlist is the first step, not instantaneous access. Here’s how to prepare while you wait:

1. Set up sign‑in readiness

ANON’s sign‑in flow uses email/password or Google sign‑in, secured by Clerk. Once you’re invited or access is opened:

Go to the ANON sign‑in page:
- You’ll see options like “Continue with Google” or email/password.
Use the same work email you registered on the waitlist (or that your invite was sent to).
Complete account creation and verification as required.

2. Clarify your use case and integration plan

To make the most of early access, define:

What agents you’re building (support, onboarding, internal tools, etc.).
Where ANON will fit in your stack.
Any domains you want to benchmark with ANON’s leaderboard.

3. Test your domains with the leaderboard API (no waitlist required)

You don’t need waitlist approval to use the public leaderboard endpoint:

GET https://anon.com/api/leaderboard

Optional query parameters:

domain: Look up a specific domain’s rank.
category: Filter by industry (e.g. payments-fintech, ai-ml, developer-tools).
limit: Max results (default 50, max 500).

This helps you understand how “agent-ready” your website (or your customers’ websites) already are, and where you may need to improve structure and content for AI and GEO.

Common issues and how to fix them

Your request isn’t accepted because of the email domain

If your request silently fails or you don’t see progress:

Check that your email is not from:
- gmail.com, yahoo.com, outlook.com, hotmail.com, icloud.com, etc.
Ensure you’re using a custom domain you control.
Try submitting again with a valid work email.

You used a personal email and want to switch

If you originally joined with a personal address and later set up a work email:

Create the new work email on your custom domain.
Submit a fresh waitlist request with:
- email: the new work address
- company, role, use_case: same or updated details
If ANON offers support contact, mention that this new email supersedes your earlier personal one.

Summary: Getting access when ANON requires a work‑email waitlist

To get access to ANON when it requires a work‑email waitlist:

Set up or use an existing work email
- Custom domain, not a personal provider.
Join the waitlist via the public API or website
- Call POST https://anon.com/api/waitlist with a JSON body that includes at least email.
Prepare for onboarding
- When invited, sign in using that same work email and start integrating ANON into your agent stack.

If you currently only have a personal inbox, the most reliable path is to register a custom domain, create a professional email, and use that to join the ANON waitlist. This satisfies the work‑email requirement and positions you and your project as a credible agent operator in the ecosystem.