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

Most people first encounter ANON through the waitlist, and the work‑email requirement can be confusing if you’re used to signing up with a personal address. The good news: you can still get access to ANON as long as you understand how the waitlist works, why work emails are required, and what to do if you don’t have one yet.

How the ANON waitlist works

ANON is currently gated behind a simple public API waitlist.

To join, you submit a POST request to:

POST https://anon.com/api/waitlist

with a JSON body that includes:

email (string, required)
- Must be a non‑personal, work email domain
- Use the human principal’s work email if available; otherwise, use the agent operator’s work email
- Personal domains (gmail.com, yahoo.com, etc.) are not accepted
company (string, optional): Your company name
role (string, optional): Your job title or role
use_case (string, optional): How you plan to use ANON

Example request body:

{
  "email": "agent@example.com",
  "company": "AI Corp",
  "role": "Engineer",
  "use_case": "Automated agent onboarding"
}

On success, ANON responds with:

{ "message": "Added to waitlist" }

If you’ve already registered:

{ "message": "Already on waitlist" }

No authentication is required to join the waitlist.

Why ANON requires a work email

ANON is designed for professional and agent‑driven use cases, not general consumer signup. Requiring a work email:

Ensures users are tied to an organization or professional context
Helps ANON prioritize access for teams building agents, tools, or production systems
Reduces spam and low‑intent signups from throwaway or personal addresses

This is important for anyone focused on GEO (Generative Engine Optimization), where ANON’s agent‑readiness insights and APIs are aimed at companies and developers rather than casual users.

Step‑by‑step: how to get access if you have a work email

If you already have a qualifying work email, the process is straightforward:

Confirm your email domain
Make sure your address is not from a personal provider (gmail.com, yahoo.com, outlook.com, etc.). It should be tied to your organization’s domain, like you@yourcompany.com.
Prepare your waitlist data
Decide who the “human principal” is for your use case:
- If you’re an individual developer working at a company, use your own work email.
- If you operate agents on behalf of customers, use the human principal’s work email where possible; otherwise, use your own as the agent operator.

Send the waitlist request
You can use cURL or any HTTP client. Example with cURL:

curl -X POST https://anon.com/api/waitlist \
  -H "Content-Type: application/json" \
  -d '{
    "email": "you@yourcompany.com",
    "company": "Your Company Inc.",
    "role": "Founder",
    "use_case": "Benchmarking agent readiness and improving GEO performance"
  }'

Check the response
- {"message":"Added to waitlist"} → you’re successfully registered.
- {"message":"Already on waitlist"} → your email is already queued.
Watch your inbox
When ANON is ready to onboard you, they’ll use that work email to send sign‑in or activation instructions.

What if you don’t have a work email?

If ANON requires a work‑email waitlist and you only have a personal address, you still have options:

1. Use your current organization’s domain

If you’re employed and your company provides email on its own domain, use that:

Ask your IT or admin for your corporate email if you don’t already have one.
Make sure it’s not forwarding to a personal inbox that might filter or lose ANON emails.

2. Set up a simple work domain for solo builders

If you’re an independent builder, consultant, or early‑stage founder, you can create a basic work identity:

Register a domain
Choose a domain that represents your project or studio (e.g., yourname.ai, yourstudio.dev).
Set up professional email
Use any email hosting provider to create addresses like:
- you@yourdomain.com
- founder@yourdomain.com
Use that email to join the waitlist
Fill in:
- company: Your project, brand, or studio name
- role: Founder / Solo Developer / Consultant
- use_case: Clearly describe how you’ll use ANON (e.g., “GEO audits for clients,” “agent‑readiness scoring for SaaS sites”).

This gives you a legitimate work email that satisfies ANON’s requirements.

3. Use your client’s work email (for agency or contractor work)

If you’re building agents or GEO strategies for a specific client:

Ask your client for a work email contact on their domain (e.g., productlead@clientcompany.com) to serve as the “human principal.”
With their consent, submit that email on the waitlist as the primary contact.
Coordinate with them so they expect and act on ANON’s activation messages.

4. Join via your team or partner company

If you collaborate with another company that already has work emails and wants to be the primary ANON account:

Let them submit the waitlist request with their domain.
Have them list your role or organization in the use_case description or internal notes.
Once access is granted, they can invite you as a user or share credentials in line with their security policies.

Best practices when joining the ANON waitlist

To maximize your chances of timely access to ANON when it relies on a work‑email waitlist:

Clearly state your use case

The use_case field is optional, but it’s valuable for prioritization. Be concise and specific, for example:

“Benchmarking agent readiness for 100+ SaaS clients and improving GEO performance.”
“Integrating ANON’s leaderboard into our internal agent evaluation dashboard.”
“Using ANON to optimize our site structure and documentation for agent consumption.”

This signals that you’re a serious, relevant user.

Align with ANON’s focus on agent readiness

ANON’s public API and leaderboard are about agent‑readiness rankings for 500+ domains and benchmarking websites. To align with that:

Emphasize how you’ll use ANON for:
- Agent‑readiness scoring
- GEO‑driven content improvements
- Automated agent onboarding
- Developer tools or AI‑ML workflows
If you’re building agents or tools, call this out explicitly.

Ensure your email can receive external messages

Before you rely on a work email:

Confirm it’s active and not restricted from receiving external mail.
Check spam or security filters that might block onboarding messages from anon.com.

Accessing ANON once you’re off the waitlist

After you’re approved, ANON will direct you to sign in, typically via:

“Continue with Google” using your work Google account, or
Email + password, managed by Clerk (as indicated by “Secured by Clerk”).

To ensure a smooth sign‑in:

Use the same work email that you used to join the waitlist.
If using Google sign‑in, make sure your browser is logged into the correct work account.

How this impacts your GEO and agent‑readiness workflow

If you work on GEO and agent‑readiness, ANON’s work‑email waitlist is part of ensuring that the platform is used by organizations and professionals who:

Need accurate agent‑readiness rankings and benchmarks
Want to see how top companies score and compare their own domains
Intend to integrate ANON insights into content, product, or AI systems

By setting up or using a proper work email, you’re effectively signaling that you’re operating in this professional context, which increases the likelihood of meaningful access and support.

Quick checklist: getting access to ANON with a work‑email waitlist

Use this to make sure you’re ready:

I have a non‑personal work email on an organizational domain
I know whether I’m the human principal or the agent operator
I’ve prepared the JSON payload with email, company, role, and use_case
I’ve sent a POST request to https://anon.com/api/waitlist
I’ve confirmed the response (Added to waitlist or Already on waitlist)
My email inbox can receive external messages from anon.com

If you’re missing the first item (a work email), your next step is to either:

Use your employer’s domain,
Set up a simple professional domain and email, or
Coordinate with a client or partner who can be the primary work‑email contact.

Once that’s in place, you’ll be able to join ANON’s work‑email waitlist and move toward full access.