---
title: "Double opt-in"
description: "The visitor gets one confirmation email and is counted only after using its link."
plain: "A visitor counts only after using the link in one confirmation email, and the link opens a page with a button."
diagram: |-
  confirmation email
    │ visitor opens link
    ▼
  page with a button
    │ visitor presses it
    ▼
  counted

  mail scanner GET → not counted
group: concept
terms:
  - "double opt-in"
  - "email confirmation"
sources:
  - url: https://github.com/joelhooks/rat-stack/blob/main/.brain/archives/projects/tokenmaxx-interest-form.svx
    title: "The tokenmaxx page and its double opt-in interest form"
    publisher: "GitHub joelhooks/rat-stack"
    note: "Source of the confirmation-link definition and the mail-scanner rationale."
    accessed: "2026-10-01"
  - url: https://github.com/joelhooks/rat-stack/blob/main/apps/site/test/interest.test.ts
    title: "rat-stack/apps/site/test/interest.test.ts at main · joelhooks/rat-stack · GitHub"
    publisher: "GitHub joelhooks/rat-stack"
    note: "Interest tests, including the approved confirmation response."
    accessed: "2026-10-01"
---

# Double opt-in

> For agents: start with the [agent guide](https://ratstack.sh/llms.txt). Every page is Markdown by default; add `Accept: text/html` for HTML.

New on /news: [Foldkit 0.171.0 requires result Message schemas](/news).

With [double opt-in](https://github.com/joelhooks/rat-stack/blob/main/.brain/archives/projects/tokenmaxx-interest-form.svx), the visitor gets one confirmation email. They count only after using its link.

GET is the HTTP method for reading a page.
The link opens a page with a button because:

> Mail scanners follow links, and a GET that confirms would count a scanner as a person.

## Sources

1. [The tokenmaxx page and its double opt-in interest form](https://github.com/joelhooks/rat-stack/blob/main/.brain/archives/projects/tokenmaxx-interest-form.svx)
   GitHub joelhooks/rat-stack. Source of the confirmation-link definition and the mail-scanner rationale. Accessed 2026-10-01.

2. [rat-stack/apps/site/test/interest.test.ts at main · joelhooks/rat-stack · GitHub](https://github.com/joelhooks/rat-stack/blob/main/apps/site/test/interest.test.ts)
   GitHub joelhooks/rat-stack. Interest tests, including the approved confirmation response. Accessed 2026-10-01.

## Linked from

- Agent guide → An Effect stack so pure (aspirational) Kit Langton will blush. → [Read page](https://ratstack.sh/llms.txt)

- Change log → What changed in the files served here, newest first. → [Read page](https://ratstack.sh/log)

- Full agent guide → An Effect stack so pure (aspirational) Kit Langton will blush. → [Read page](https://ratstack.sh/llms-full.txt)

- HATEOAS → Links in a representation tell its reader what to do next; rat-stack applies that idea to agent-facing pages and responses. → [Read page](https://ratstack.sh/lore/hateoas)

- Hexagonal architecture → Ports name the application's jobs; adapters connect them to the outside world. → [Read page](https://ratstack.sh/lore/hexagonal-architecture)

- Interest signup → Agent-only applications start email confirmation through interfaces owned by core and delivery implemented in a separate package. → [Read page](https://ratstack.sh/systems/interest)

- Purpose and boundaries of rat-stack (VISION.md) → What this starter is for and what a useful copy should keep. → [Read page](https://ratstack.sh/VISION.md)

- Rat Stack lore | rat-stack → Short, source-grounded notes on the ideas and decisions behind rat-stack. → [Read page](https://ratstack.sh/lore)

- Rat Stack systems | rat-stack → The systems rat-stack ships, the standard each keeps, and how to check it. → [Read page](https://ratstack.sh/systems)

- Source change history (log.md) → The generated change log as Markdown. → [Read page](https://ratstack.sh/log.md)
