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

# Introduction

> Overview of the Candidate Profile API and how to work with its resources

## Welcome

<Card title="Candidate Profile OpenAPI spec" icon="code" href="/api-reference/openapi.json">
  Review the source definition that drives the interactive endpoint reference.
</Card>

## Also available through MCP

<Card title="Browse the MCP server" icon="sparkles" href="/mcp/introduction">
  Prefer agent-native access? Use the remote MCP server to browse resources, call tools, and start from a built-in summary prompt.
</Card>

## Base URLs

The API currently exposes a single server target:

```bash Base URL theme={null}
https://api.jonahanderson.me
```

## Authentication

This API uses bearer-token authentication. Call `POST /auth/token` with an email address to receive a signed token, then send `Authorization: Bearer YOUR_TOKEN` on every protected request.

<Card title="Read the authentication guide" icon="key" href="/api-reference/authentication">
  See the token flow, example headers, and auth-related error responses.
</Card>

## Resources

The current API surface is grouped into six functional areas:

* `Authentication` for requesting a signed bearer token.
* `Candidate` for the top-level profile payload.
* `Experience` for listing roles and retrieving a single experience entry.
* `Projects` for project summaries and full project details.
* `Resume` for structured resume data or a PDF link.
* `Contact` for inbound contact requests and availability status.

## Responses

All endpoint details, parameters, and schemas are generated directly from the OpenAPI file, so updating the spec will update the rendered reference pages that use the `openapi` frontmatter.

Response examples in this portal are illustrative and use sample data. They show the shape of the API, not the exact values returned by live requests.