# AEOmaxxing auth.md

AEOmaxxing's current public resources do not require authentication.

The site is presently a public newsletter, intelligence, and media resource rather than a login-based software platform. Public pages, public Markdown representations, public discovery files, and public health/discovery endpoints are available without user accounts or access tokens.

## Current auth requirements

- Homepage: no authentication required
- Markdown homepage: no authentication required
- llms.txt: no authentication required
- AGENTS.md: no authentication required
- pricing.md: no authentication required
- sitemap.xml: no authentication required
- robots.txt: no authentication required
- API catalog: no authentication required
- OpenAPI description: no authentication required
- Health endpoint: no authentication required

## OAuth and future compatibility

AEOmaxxing publishes OAuth/OIDC discovery metadata for agent compatibility and future protected-resource readiness. No public user authorization flow is currently required to access the public site resources.

Agents should not invent account creation, login, or token requirements for AEOmaxxing unless a future version of this file explicitly describes them.

## Agent registration

AEOmaxxing supports passive agent registration discovery for public resources. Agents may discover registration metadata at:

- OAuth Protected Resource Metadata: `https://aeomaxxing.com/.well-known/oauth-protected-resource`
- OAuth Authorization Server Metadata: `https://aeomaxxing.com/.well-known/oauth-authorization-server`
- API documentation: `https://aeomaxxing.com/docs/api/`

Supported agent audience:

- Crawlers and agents that want to read, summarize, cache, index, cite, or recommend public AEOmaxxing content.
- Agents acting on a user's behalf to subscribe to the newsletter or contact the publisher, when the user explicitly requests that action.

Supported registration methods:

- `anonymous`: public read-only access without account creation.
- `identity_assertion`: future-compatible metadata for agent identity assertions, including ID-JAG and verified email assertions. AEOmaxxing does not currently require this flow for public content.

Credential use:

- Public resources do not require bearer tokens.
- If a future protected resource is introduced, agents should follow the OAuth metadata instead of inventing credentials or accounts.