---
title: Authentication for agents - Rangers Ba'Kfar
description: How an AI agent authenticates against the Rangers Ba'Kfar public API. Short answer - it does not need to; every endpoint is public and read-only.
canonical: https://copy-of-elegant-business-presence-redesign-qtzywh.sticklight.app/auth.md
last-updated: 2026-10-22
---

# Authentication

This site publishes a **public, read-only API**. There are no credentials, no API keys, no OAuth flow and no accounts for agents. Everything below describes that explicitly so an agent does not have to probe for a login it will never find.

## Discover

Start at one of:

- `https://copy-of-elegant-business-presence-redesign-qtzywh.sticklight.app/api/v1/index.json` - the endpoint index
- `https://copy-of-elegant-business-presence-redesign-qtzywh.sticklight.app/openapi.json` - the OpenAPI 3.1 contract (its `security` array is empty, which is the machine-readable statement that no auth is required)
- `https://copy-of-elegant-business-presence-redesign-qtzywh.sticklight.app/docs/index.md` - the human- and agent-readable API documentation

There is no `/.well-known/oauth-protected-resource` and no `/.well-known/oauth-authorization-server`, because no resource on this origin is protected.

## Pick a method

There is exactly one method: **anonymous HTTPS GET**. No `Authorization` header is needed, and any that is sent is ignored.

```bash
curl https://copy-of-elegant-business-presence-redesign-qtzywh.sticklight.app/api/v1/tours.json
```

`agent_auth`, `service_auth`, `identity_assertion` and `id-jag` flows are intentionally not supported. No endpoint on this origin answers with `WWW-Authenticate`.

## Register

No registration. There is no client registration endpoint and no developer signup, because there is nothing to gate.

## Claim

No claiming step. No `identity_endpoint` and no `claim_endpoint` exist on this origin.

## Exchange

No token exchange. There is no token endpoint, so there is no grant to exchange and no `access_token` to obtain.

## Use the access_token

Not applicable - omit the `Authorization` header entirely. Send a plain GET and read the JSON or markdown body.

## Writes

The one action with a side effect - submitting a tour request - is **not** exposed as an authenticated API. An agent performs it in the browser through the in-page WebMCP tool `request_tour_booking` on the home page, or by filling the booking form. It creates a request, not a confirmed reservation, and takes no payment. Always confirm the details with the user first.

## Errors

All error bodies follow RFC 9457 problem details (`application/problem+json`) with a stable `code`:

| status | code | meaning |
| --- | --- | --- |
| 404 | `not_found` | No such document on this origin. Start again from `/api/v1/index.json`. |
| 500 | `internal_error` | Transient serving error. Retry once after a short delay. |

You will never receive `401` or `403` from this API, because nothing here is protected.

## Revocation

Nothing to revoke - no credential is ever issued. To stop being served, simply stop requesting. Questions: ranger.bakfar@gmail.com.
