> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fitsociety.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer Docs

> Start here when integrating with FITsociety developer APIs.

FITsociety developer documentation is split into three integration surfaces:

| Surface        | Use it for                                                                                                                                                                               | Authentication                                    |
| :------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------ |
| Public API     | Server-to-server REST integrations for clients, bookings, finance, progress, forms, reporting, and webhooks.                                                                             | OAuth client credentials and Bearer access tokens |
| MCP            | AI-assistant access through controlled company-scoped tools. Use [Agent Setup](/mcp/agent-setup) or the [agent prompt](/mcp/agent-setup-prompt.md) to let an AI client configure itself. | MCP API keys or MCP OAuth                         |
| Access Devices | QR gates, badge readers, and door-controller validation.                                                                                                                                 | Dedicated access-device keys                      |

## Recommended path

1. Read the Public API overview to understand route families and company
   scoping.
2. Configure OAuth credentials in FITsociety and request a Bearer token.
3. Read the contracts page before writing production code. It defines response
   envelopes, validation behavior, idempotency, pagination, rate limits, and
   field stability.
4. Use the API Reference tab for endpoint-level request and response details.
5. Use the domain guides for extra validation rules, privacy notes, and
   business guardrails.

## Sections

* **Docs** contains conceptual guides, validation rules, output contracts, and
  product-specific integration notes.
* **API Reference** is generated from the Public API OpenAPI contract and is the
  source for endpoint-level method, path, parameter, request body, and response
  details.
* **MCP** documents the AI tool interface and keeps its grants, OAuth metadata,
  and runtime endpoint separate from the REST Public API.
* **Changelog** lists externally relevant developer API documentation and
  contract changes.

## Versioning

The current REST developer surface is `/public/v1`. Existing fields remain
stable for the lifetime of v1. New fields may be added in a backward-compatible
way, but sensitive or internal model fields are not automatically exposed just
because they exist in backend models.