Nationwide U.S. property records through MCP, CLI, or REST. Sign in with OAuth. Machine-readable docs.
Add the MCP URL or run realie login. The browser is Clerk on accounts.realie.ai. Do not register a client in the Clerk dashboard — hosts read our protected-resource metadata and register themselves.
Connect https://app.realie.ai/api/mcp in your MCP host, or run realie login. Sign up or sign in in the browser. New accounts are created in that Clerk window.
MCP URL and install commands →If the Realie account is new, add a payment method at the dashboard. OAuth does not mint an API key. tools/call and realie lookup need a billed user. CI and REST keep using Authorization: Bearer.
Open dashboard →Same data behind every interface. Start with MCP OAuth unless you already have a key for CI or REST.
Live property data for Cursor, Claude Code, Codex, and other MCP hosts. Add the URL with no API key. The host registers itself and opens Clerk OAuth.
MCP docs →MCP server URL
https://app.realie.ai/api/mcpOAuth protected resource
https://app.realie.ai/.well-known/oauth-protected-resource/mcpClaude Code
claude mcp add --transport http realie https://app.realie.ai/api/mcpUniversal installer
npx add-mcp https://app.realie.ai/api/mcpQuery property data from the terminal. `realie login` opens Clerk OAuth, then stores the existing API key. Every command supports --json.
CLI docs →Install
curl -fsSL https://app.realie.ai/api/cli/install | bashSign in (OAuth)
realie loginCI (after a key exists)
realie login --api-key YOUR_API_KEYLook up a property
realie lookup --address "504 LAVACA ST" --state TX --county TRAVIS --jsonAddress, parcel, owner, location, and comparables endpoints. Bearer API key after OAuth and billing. One schema across 3,100+ counties.
API docs →Example request
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://app.realie.ai/api/public/property/address?address=504%20LAVACA%20ST&state=TX"Point agents here before they scrape HTML.
This page as clean Markdown — OAuth, MCP, CLI, and REST without HTML.
OAuth resource, protected-resource metadata, and sign-in steps for agents.
Protected-resource metadata hosts read after a 401. Do not register a Clerk app.
When-to-use guidance, endpoint table, and CLI cheat sheet for coding agents.
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 at https://app.realie.ai/developer. OAuth does not mint an API key; billing does.
Use MCP when the IDE or harness speaks Model Context Protocol (OAuth, no API key in the config). Use the CLI for terminal and shell workflows (prefer --json). Use REST when you are building an app or need full control over requests and pagination.
Start with https://www.realie.ai/auth.md, then https://www.realie.ai/agents.md. Full docs index: https://docs.realie.ai/llms.txt. Individual docs pages are also available as Markdown (append .md to the URL). Do not connect https://docs.realie.ai/mcp for property data — that server searches documentation only.
Yes. Docs publish a Realie skill at /.well-known/agent-skills/. Prefer this page and auth.md for OAuth URLs — the skill may still mention the docs MCP.
Connect MCP or run realie login, complete Clerk in the browser, then add billing if the account is new.