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

# Introduction

> How Revcenter's API is organized

Revcenter's API is the same Next.js app that serves the UI — there's no separate backend
service. Routes live under `app/api/`.

## Base URL

<CodeGroup>
  ```bash Local theme={null}
  http://localhost:3000
  ```

  ```bash Production theme={null}
  https://app.revcenter.ai
  ```
</CodeGroup>

## Authentication

Every route except `/api/auth/*` (which *is* the auth system) requires a valid
**session cookie** — the same cookie your browser holds after signing in. There is no
separate API-key auth for these routes; they're meant to be called from the app's own
frontend, not as a public API.

An unauthenticated request gets:

```json theme={null}
{ "error": "Sign in required" }
```

with HTTP status `401`.

## Errors

Routes return a JSON body with an `error` string on failure, and sometimes a `code`
field for errors the frontend needs to branch on (for example,
`anthropic_not_configured`). There's no single global error envelope beyond that — check
each endpoint's reference page for its specific error shapes.

## Endpoints

<CardGroup cols={2}>
  <Card title="Authentication" icon="lock" href="/api-reference/auth">
    Sign-up, sign-in, sessions, organizations, invitations — handled by better-auth.
  </Card>

  <Card title="Intake" icon="wand-magic-sparkles" href="/api-reference/intake">
    Extract structured search criteria from free text or a job description.
  </Card>

  <Card title="Credentials" icon="key" href="/api-reference/credentials">
    Manage encrypted API keys for downstream providers.
  </Card>
</CardGroup>