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

# API reference

> How the PymtHouse HTTP APIs and OIDC surface fit together, and where to find endpoint-level documentation.

PymtHouse exposes a **unified OpenID Connect issuer** plus **REST-style Builder and billing APIs** under a single base URL. This tab will collect machine-readable **OpenAPI** definitions as they become available; the live **authorization, token, and user-management** paths are also listed in your tenant's [OIDC discovery](https://openid.net/specs/openid-connect-discovery-1_0.html) document so your client always tracks endpoint rotations.

## Base URL and discovery

* **Local development (issuer and APIs):** `http://localhost:3001/api/v1/oidc` as described on the [home page](/) — use discovery rather than hard-coding path suffixes.
* **Discovery (runtime source of truth):** `GET {issuer}/.well-known/openid-configuration` returns all authorization, token, and JWKS endpoints for your environment.

Always resolve OAuth and OIDC URLs from discovery in production. Hard-coded paths are brittle when routes or hostnames change.

## Where to find endpoint documentation

All endpoint guides currently live in the **Builder guides** tab:

| Need                                                     | Go to                                                                        |
| -------------------------------------------------------- | ---------------------------------------------------------------------------- |
| End-to-end auth flows, PKCE, device code, token exchange | [Builder guides](/quickstart) tab                                            |
| **Usage API** (aggregated usage, billing analytics)      | [Usage API](/integration/usage-api) in Builder guides                        |
| User management, app tokens, billing endpoints           | [Builder guides](/integration/user-management) and related pages in that tab |

## Next steps

<CardGroup cols={2}>
  <Card title="Usage API" icon="chart-bar" href="/integration/usage-api">
    `GET` aggregated usage and fees for your app (and optional per-user breakdown).
  </Card>

  <Card title="User management" icon="users" href="/integration/user-management">
    Create and manage end-users in your app tenant via the Builder API.
  </Card>
</CardGroup>