ANON onboarding: how does “Connect Your Product” detect our auth and payment setup, and what do we need to configure?

When you first land in the Connect Your Product step during ANON onboarding, the goal is simple: ANON needs to understand how your product authenticates users and how payments are handled so it can safely interact with your app on behalf of agents. This step minimizes manual setup by automatically inspecting your domain and inferring the basics of your auth and billing stack.

Below is a practical breakdown of how the Connect Your Product detection works conceptually, what you’ll typically be asked for, and what you should prepare or configure to get through onboarding smoothly.

What the “Connect Your Product” step does

The Connect Your Product screen asks you to:

Enter your domain
Provide Company name and Contact email
Click Detect
Then Continue to Stack Setup

Behind that simple flow, ANON is trying to answer two questions:

Auth: How do users sign in or sign up to your product?
Payments: How are subscriptions, plans, or one‑off charges managed?

By detecting these automatically where possible, ANON can:

Pre‑configure reasonable defaults for your project
Suggest the right auth and billing integrations
Reduce the amount of code and settings you have to maintain manually

What ANON can infer from your domain

When you enter a domain (for example, app.yourcompany.com), ANON can run a series of checks such as:

Sign‑in patterns
- Looking for standard auth paths like /login, /signin, /signup, /auth/*
- Detecting hosted login pages from common providers (for example, a Clerk sign‑in widget like the one shown in the “Sign in to Anon” screen, Auth0 Universal Login, etc.)
Auth provider hints
- Identifying SDK script tags, meta tags, or HTML attributes belonging to specific providers (Clerk, Auth0, etc.)
- Detecting OAuth flows (Google, GitHub, Microsoft) offered on your login page
Payment provider hints
- Recognizing embedded checkout or billing portals from common payment providers (Stripe Checkout, Stripe Customer Portal, others)
- Spotting pricing page patterns or “Manage billing” links that redirect to external billing systems

This domain‑based detection is non‑invasive: it inspects publicly accessible pages and assets. It does not log in to user accounts or access private data during this initial setup step.

Information you’ll be asked to provide

Alongside your domain, the Connect Your Product and related onboarding forms usually ask for:

Company name – Your organization’s name.
Contact email – A work email that ANON can use for setup and system notifications.

For public API or waitlist flows (for example, POST /api/waitlist at https://anon.com), ANON expects:

email (required):
- Must be a work email (no gmail.com, yahoo.com, etc.)
- Ideally the human principal’s work email; otherwise, the agent operator’s email.
company (optional): Your company name.
role (optional): Your job title or role.
use_case (optional): How you plan to use ANON.

Example request body:

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

Success responses:

// Success
{ "message": "Added to waitlist" }

// Already registered
{ "message": "Already on waitlist" }

The same core fields (company, contact email, role/use_case) are used throughout onboarding to tune your ANON setup around your organization and intended use.

How auth detection typically works

While the exact implementation is internal to ANON, you can think of auth detection in three layers:

Provider recognition
ANON checks your public pages for markers of major auth providers, such as:
- JavaScript SDKs or HTML attributes from Clerk, Auth0, etc.
- “Continue with Google” or “Sign in with …” buttons configured via a known provider
- Hosted login domains (for example, a Clerk or Auth0 domain)
Flow structure
ANON infers whether you support:
- Email + password login
- Passwordless login (magic links, OTPs)
- Social login (Google, GitHub, etc.)
- SSO / SAML for enterprise
Integration points
ANON identifies which URL patterns and endpoints look like:
- Login / signup
- Logout
- Callback or redirect URIs for OAuth
- Profile or account settings pages

This detection allows ANON to suggest how agents should authenticate when acting on behalf of users, or how they should direct users back to your product when needed.

How payment setup detection works

On the payment side, ANON tries to determine:

Whether your product is paid or free
- Presence of pricing pages and plan information
- Billing or subscription links in your app navigation
Which payment provider you likely use
- Stripe Checkout or Customer Portal scripts or URLs
- Hosted billing dashboards
- Identifiable payment widgets
How billing is structured
- Subscription tiers vs usage‑based vs one‑time charges
- Trial flows or upgrade prompts

The goal is to let ANON interact with your billing logic safely—whether that’s recommending plan upgrades, creating subscriptions via your public flows, or respecting usage limits agents shouldn’t exceed.

What you should prepare before using “Connect Your Product”

To make detection and configuration smoother, make sure you have:

A stable domain for your product:
- Production or staging is fine, as long as it’s reachable.
- If you use a subdomain for the app (for example, app.yourcompany.com), use that.
A working sign‑in page that’s publicly discoverable:
- Accessible via a link from your marketing site, or directly via a known URL (for example, /login).
- Using your actual auth provider configuration (not a placeholder).
A visible pricing/billing flow, if applicable:
- Pricing page or in‑app billing section.
- Live or staging payment integration (Stripe or others).
A valid work email for the contact:
- This is required in the email field for API access and waitlist.
- Avoid personal domains like gmail.com or yahoo.com.

What you’ll need to configure after detection

Detection is a starting point, not the full setup. After ANON detects your auth and payment stack, you’ll typically need to:

1. Confirm or refine auth details

Verify the detected auth provider.
Confirm primary login URL(s).
Optionally add:
- Special SSO / SAML endpoints.
- Separate login paths for different user segments (admin vs end‑user).

If you’re using an embedded auth solution (like Clerk, as shown in the “Sign in to Anon” UI), ANON may require:

Your frontend domain and backend API domain if they differ.
Redirect URLs where agents or users should land after auth.

2. Confirm or refine payment setup

Specify the payment provider used (if detection suggested multiple options).
Confirm:
- Where users can view or change their plan.
- Where they can update billing details.
For more advanced setups:
- Define plan names / identifiers as ANON should refer to them.
- Note any free tiers, trials, or usage caps that agents must respect.

3. Configure organization & contact info

Company name: Ensure it matches how you present yourself publicly.
Contact email: Use a shared or monitored address (for example, devops@company.com or platform@company.com) if it will receive system notifications.

If you’re integrating via the public API:

Use the POST /api/waitlist endpoint to ensure your organization and key contacts are registered:
- email (work email, required)
- company, role, use_case (optional but helpful for ANON’s configuration hints)

Handling edge cases and custom setups

If you have a non‑standard setup, be ready to supply more manual configuration after detection:

Custom, in‑house auth (no third‑party provider):
- Provide precise login, logout, and callback URLs.
- Document any required query params or headers.
Multiple apps or domains:
- Decide which primary product ANON should connect first.
- List all relevant domains and specify which domain is used for auth vs app UI.
Internal or non‑public environments:
- If detection can’t access your login page or billing page (for example, VPN‑only), you may need to:
  - Use a staging environment that’s publicly reachable, or
  - Provide explicit URLs and descriptions manually during stack setup.

How to know detection was successful

You can consider detection successful when:

The onboarding UI shows the correct auth provider or terminology.
Suggested login URLs lead to your real sign‑in flow.
ANON surfaces accurate information about your pricing or billing entry points.
The Stack Setup step requires only minor edits rather than full manual entry.

If the suggestions are obviously wrong or incomplete, you can still proceed by overriding them manually in Stack Setup and by providing additional details to ANON support or via configuration forms.

Summary: what you need to configure

To get through ANON onboarding and the Connect Your Product step smoothly, be ready to:

Provide a reachable domain for your product.
Confirm auth details:
- Auth provider (or custom auth).
- Login/logout URLs and any special SSO flows.
Confirm payment details:
- Payment provider.
- Where users manage subscriptions and billing.
Supply organization info:
- Company name.
- Work contact email (and, via API, role and use_case where applicable).

With these elements in place, ANON can reliably detect your auth and payment setup, reduce manual configuration, and align its agent workflows with your actual product experience.