Skip to main content
Same data as the homepage agents hub. This page is the docs copy: install commands, OAuth discovery, and a longer FAQ. Agent-readable Markdown: agents.md · auth.md. Append .md to any docs URL (including this one: agents.md).

​
OAuth first

Do not register an OAuth app in the Clerk dashboard. Hosts discover Realie’s authorization server and register themselves (DCR).
1

Sign in with OAuth

Add https://app.realie.ai/api/mcp in your MCP host, or run realie login. Sign up or sign in in the browser (accounts.realie.ai). New accounts are created in that Clerk window.
2

Enable API access

If the Realie account is new, add a payment method in Billing. OAuth does not mint an API key. tools/call and realie lookup need a billed user. CI and REST keep using Authorization: YOUR_API_KEY.
OAuth discovery (on app.realie.ai, not clerk.com):
  • Resource: https://app.realie.ai/api/mcp
  • Protected resource metadata: https://app.realie.ai/.well-known/oauth-protected-resource/mcp
  • Authorization server metadata: https://app.realie.ai/.well-known/oauth-authorization-server
https://docs.realie.ai/mcp is Mintlify documentation search only. It cannot return property records. Use https://app.realie.ai/api/mcp for property data.

​
Pick how your agent talks to Realie

Same records behind every interface. Start with MCP OAuth unless you already have a key for CI or REST.

MCP

Live property tools for Cursor, Claude Code, and other MCP hosts. Add the URL with no API key. Host-specific install steps.

CLI

Terminal and shell workflows. realie login opens Clerk, then stores the existing API key. Prefer --json.

REST API

Address, parcel, owner, location, and comparables. API key in the Authorization header after OAuth and billing.

​
MCP

URL: https://app.realie.ai/api/mcp
Do not put an API key in the URL or in mcp.json. initialize and tools/list work without a token. tools/call returns HTTP 401 with WWW-Authenticate pointing at protected-resource metadata.

​
CLI

CI (non-interactive, after a key exists):
Or set REALIE_API_KEY.

​
REST API

Base: https://app.realie.ai/api
OpenAPI: openapi.json

​
Machine-readable resources

Prefer this page and auth.md for OAuth URLs. The generated skill may still mention the docs MCP until Mintlify rebuilds it.

​
FAQ

​
Account and OAuth

Yes. Add https://app.realie.ai/api/mcp or run realie login. Complete Clerk sign-up or sign-in in the browser. New accounts then add a payment method in Billing. OAuth does not mint an API key; billing does.
No. Hosts read protected-resource metadata, then Realie’s authorization server metadata, and register themselves (DCR). Creating a client at clerk.com is the wrong path and will not work.
No. OAuth identifies the Clerk user. MCP tools/call and the CLI map that user to the API key already on the Realie billing record. REST and CI still send Authorization: YOUR_API_KEY.
Property calls spend tokens on a billed account. A Clerk session without a payment method can list tools and still fail tools/call or realie lookup. Add a card in Billing. See the API FAQ for invoice recovery.
The Clerk window creates the user if they do not exist. Existing Realie users sign in to the same account. New users still need a payment method before property calls succeed. Existing billed users can call tools as soon as OAuth completes.
The same Clerk window as MCP, then the CLI stores the existing API key in ~/.realie/config.json. It does not persist the Clerk access token. MCP hosts keep the Clerk token themselves.

​
MCP, CLI, and REST

MCP when the IDE or harness speaks Model Context Protocol (OAuth, no API key in the config). CLI for terminal and shell workflows (prefer --json). REST when you are building an app or need full control over requests and pagination.
No. Add only https://app.realie.ai/api/mcp. An API key in the URL or config is the docs-MCP pattern and is wrong for product data. If a host supports a custom header, Authorization: Bearer YOUR_API_KEY still works, but OAuth is the path for a new session.
Mintlify’s documentation-search MCP. Auth is none. It cannot look up parcels, owners, or comparables. Property data is https://app.realie.ai/api/mcp.
Expected before OAuth. initialize and tools/list are unauthenticated. tools/call returns HTTP 401 with WWW-Authenticate pointing at the protected-resource metadata. Complete Clerk consent, then retry. A 401 after a finished login usually means the host is not sending the access token.
Yes. Each tool wraps the matching public REST handler (property_search → GET /api/public/property/search, and so on). Successful tool results contain live parcel data. Check isError for lookup or validation failures, which can still arrive with HTTP 200.
Do not run interactive realie login. After a key exists, use realie login --api-key YOUR_API_KEY or REALIE_API_KEY. REST: Authorization: YOUR_API_KEY.

​
Billing and errors

The Clerk user is signed in, but the Realie account is blocked for billing: unpaid invoices, inactive subscription, missing or unverified card, or overage cap. Read error.message in the MCP JSON-RPC response. REST API denials instead include code and action fields. Recovery: Billing and the API FAQ. Denied 403 requests do not spend tokens.
Temporary card verification hold, not a charge. It is released immediately. Details: API FAQ.
Yes. A successful property tools/call (200) spends one token, same as the REST endpoint it wraps. 401, 403, and empty 404 lookups do not. See What is a token?.

​
Docs and discovery

Start with auth.md, then agents.md or this page as Markdown. Full docs index: llms.txt. Individual docs pages are also available as Markdown (append .md to the URL).
Yes. Docs publish a skill at /.well-known/agent-skills/realie/skill.md. Prefer this page and auth.md for OAuth URLs if the skill still mentions the docs MCP.
www.realie.ai/agents is the marketing hub. This page is the same setup inside docs, with the extended FAQ. agents.md is that hub as clean Markdown for agents that prefer not to parse HTML.