---
title: "Agent Authentication & OAuth 2.0 Discovery Walkthrough"
description: "Step-by-step authentication specification for autonomous agents interacting with Into Nature Arctic Booking APIs, MCP server, and UCP checkout."
url: "https://booking.intonaturearctic.com/auth.md"
---

# Into Nature Arctic — Agent Authentication Guide (`agent_auth`)

Public catalog, pricing, availability, and MCP discovery routes are readable without authentication. Write operations and UCP cart mutations use OAuth 2.0 Bearer tokens advertised via RFC 9728 and RFC 8414 `agent_auth` metadata.

## 1. Discover

Probe `https://booking.intonaturearctic.com/agent/identity` or `https://booking.intonaturearctic.com/api/ucp/v1/carts`. Unauthenticated requests return HTTP `401 Unauthorized` with a `WWW-Authenticate` header pointing to `resource_metadata="https://booking.intonaturearctic.com/.well-known/oauth-protected-resource"`:

```http
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer realm="into-nature-arctic-booking", resource_metadata="https://booking.intonaturearctic.com/.well-known/oauth-protected-resource", error="invalid_token"
Content-Type: application/problem+json
```

Then fetch `https://booking.intonaturearctic.com/.well-known/oauth-protected-resource` and `https://booking.intonaturearctic.com/.well-known/oauth-authorization-server` to inspect the `agent_auth` endpoints and supported scopes (`catalog:read`, `booking:quote`, `ucp:cart`).

## 2. Pick a Method

- **Public Read-Only Discovery**: No token required for `/llms.txt`, `/llms-full.txt`, `/pricing.md`, `/openapi.json`, and `POST /api/mcp` read-only tools.
- **OAuth 2.0 Client Credentials / PKCE (`S256`)**: Recommended for autonomous booking agents creating UCP cart quotes.
- **RFC 9421 HTTP Message Signatures (`web-bot-auth`)**: Verify crawler identity against `/.well-known/http-message-signatures-directory`.

## 3. Register

Submit a dynamic client registration payload to `POST https://booking.intonaturearctic.com/api/oauth/register` (advertised under `agent_auth.registration_endpoint`):

```bash
curl -sS -X POST https://booking.intonaturearctic.com/api/oauth/register \
  -H "Content-Type: application/json" \
  -d '{"client_name":"arctic-booking-agent","grant_types":["client_credentials"],"scope":"catalog:read booking:quote ucp:cart"}'
```

## 4. Claim

Bind your registered `client_id` to an Ed25519 key or sandbox tenant claim via the `agent_auth` claim verification descriptor.

## 5. Exchange

Exchange your credentials at `POST https://booking.intonaturearctic.com/api/oauth/token` (`agent_auth.token_endpoint`) for a scoped Bearer access token:

```bash
curl -sS -X POST https://booking.intonaturearctic.com/api/oauth/token \
  -H "Content-Type: application/json" \
  -d '{"grant_type":"client_credentials","scope":"catalog:read booking:quote ucp:cart"}'
```

## 6. Use

Supply the issued token in the `Authorization` header (replace `<ucp_sbx_token>` with your issued token) when calling `/agent/identity` or `/api/ucp/v1/carts`:

```bash
curl -sS https://booking.intonaturearctic.com/agent/identity \
  -H "Accept: application/json"
```

## 7. Errors

All protected JSON routes return structured RFC 9457 Problem Details (`application/problem+json`) with `type`, `title`, `status`, `error`, `error_description`, and `message` fields alongside the `WWW-Authenticate` challenge header.

## 8. Revocation

Revoke active agent tokens at any time by calling `POST https://booking.intonaturearctic.com/api/oauth/revoke` with `{"token":"<ucp_sbx_token>"}`.
