# auth.md — agent access and registration for Infinite Arcade

This document is the single source of truth for how autonomous agents
authenticate with Infinite Arcade. It follows the Auth.md convention so that
scanners and agent operators can discover the access model without probing
the service.

## Agent audience

Autonomous agents that read the public game catalog: search assistants,
recommendation agents, moderation tooling, and MCP-based chat agents. Every
documented endpoint serves read-only public data.

## Endpoints and authentication requirements

| Endpoint | Method | Authentication |
| --- | --- | --- |
| `https://infinitearcade.cc/api/search` | GET | none |
| `https://infinitearcade.cc/api/games/lookup` | GET | none |
| `https://infinitearcade.cc/mcp` (Streamable HTTP, JSON-RPC 2.0) | POST (+ GET for 405/GET-stream rejection) | none |
| `https://infinitearcade.cc/.well-known/*` discovery files | GET | none |

## Registration and provisioning

No registration, API keys, tokens, or account provisioning are required. The
HTTP catalog API and the MCP tools are open; rate limits are the only guard.

## Credential use

Infinite Arcade does not currently issue or accept credentials: no OAuth
bearer tokens, no API keys, no signed identities. If that ever changes, the
`agent_auth` block and OAuth Protected Resource Metadata
(`/.well-known/oauth-protected-resource`) will be published here first, and
this file will remain the discovery pointer for scanners.

## Related discovery files

- Service and API description: `/.well-known/api-catalog` (RFC 9727 linkset),
  `/.well-known/openapi.json`, `/docs/`
- Agent interfaces: `/.well-known/agent-card.json` (A2A),
  `/.well-known/mcp/server-card.json` (MCP)
- Skills: `/.well-known/agent-skills/index.json`
- Content preferences: `Content-Signal` in `/robots.txt`
