---
title: "Identity and auth"
description: "Agent identity and future access"
status: "preview"
canonical_url: "https://fairwayrent.ai/docs/agents/identity-and-auth"
last_updated: "2026-11-18"
related:
  - "/agents"
  - "/docs/agents/tools"
audience: "agents, developers"
---

> For AI agents: This page describes the Fairway preview. The MCP endpoint is coming soon.

# Identity and auth

The MCP endpoint is coming soon. Search access is planned to be open with a tighter anonymous limit. Registered access is planned for higher limits. Exact limits and credential handling are pending.

## Agent identity

The proposed convention is an agent profile URL in `meta.agent.profile` and `User-Agent: Agent/<name>`. A profile can identify the agent name, operator, contact, homepage, and optional webhook URL. These fields are a preview, not a request format to use yet.

## Renter information

Do not send renter identifiers or private preferences for search. Keep the user's conversation and ranking in your agent. Future booking will need explicit renter consent and an authorization design that is still open.

## Registration

[Register](/agents/register) for launch updates. Key registration is planned as Preview REST `POST /keys`: send an agent label, receive a key once, then use `Authorization: Bearer <key>`. In the service in development, a key must carry the `mcp:search` scope. An invalid key gets a JSON-RPC error with `error.data.error` set to `invalid_api_key`. Its `WWW-Authenticate` header says `invalid_token`. A key without that scope gets `error.data.error` set to `insufficient_scope`, and its header says the same. Check `error.data.error` or `error.code`, not the header text. Each [tool page](/docs/agents/tools) lists the JSON-RPC error codes. The service has no OAuth flow. Rotation and revocation instructions will be published with the service.
