Build on sourced property records.

What you can use

Site MCP server

RemotePOST https://blbestate.com/mcp. MCP over Streamable HTTP (JSON-RPC 2.0). No registration, no credentials. Stay under one request per second; over-limit clients get HTTP 429.

curl https://blbestate.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Server card: /.well-known/mcp/server-card.json · Credentials: /auth.md · OpenAPI for the agent endpoints: /openapi.json. Setup for Claude, ChatGPT, Cursor and VS Code is on Integrations.

Public-records MCP (in the Mac app)

LocalThe Mac app includes an MCP server named blbestate. It runs on your Mac over stdio, so Claude Desktop, Claude Code, Cursor and VS Code can launch it. Nothing about it sends your pipeline, leads or deals to us. Every tool is read-only: none writes, harvests, deploys or spends.

Open the app, go to Settings → Claude / MCP and copy the configuration. The app fills in the exact path of its bundled Node.js runtime and server, and shows no configuration if the server is missing from the build. The block has this shape:

{
  "mcpServers": {
    "blbestate": {
      "command": "<node path shown in the app>",
      "args": ["<server.mjs path shown in the app>"]
    }
  }
}

The server reads https://api.blbestate.com (/v1/search and /v1/property-audit). Without a token it runs at the public preview tier. To read at your plan's tier, set BLBESTATE_TOKEN_FILE in the server's environment to a file that holds your subscriber token; it is read at call time and never logged or returned.

Public-records REST API

Base URL https://api.blbestate.com · JSON · OpenAPI: /agent/estate-api-openapi.json

curl "https://api.blbestate.com/v1/search?state=AZ&county=Maricopa&per_page=25"

• Anonymous (preview tier): no header; 25 rows per page, 240 expensive reads per minute per client.
• Subscriber token (pro and founder tiers): buy the app at /buy/mac or /buy/windows; the token is delivered to your app. Send Authorization: Bearer <token>.
• There is no self-serve key endpoint for agents. Details: /auth.md.

Connect your other apps

Property research rarely ends here. The shared Black Label platform behind Integrations gives you one key for 1,609 apps: CRMs such as HubSpot and Salesforce, Google Sheets, Gmail and Outlook, Slack and more. You connect each app once by signing in to it; the same connections then work from the REST API, the MCP server and the SDKs.

Get an API key (you sign in on the platform) · Connect your apps

REST API

Base URL https://tryacee.com/api/v1 · Authorization: Bearer ace_sk_… (or x-api-key) · JSON in and out · errors are {"error":{"code","message"}} · 120 requests a minute per key · spec: tryacee.com/openapi.json

curl -X POST https://tryacee.com/api/v1/tools/find \
  -H "Authorization: Bearer ace_sk_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"task":"add a row to a Google Sheet"}'

The full list, including disconnect, trigger types and event history, is in the OpenAPI spec.

MCP for every app you connect

Remote MCP server at https://tryacee.com/mcp (Streamable HTTP) with Authorization: Bearer <key>, or the URL-only form https://tryacee.com/mcp/k/<key> for clients that take a single link. Six tools: search_apps, connect_app, list_connections, find_tools, get_tool, run_tool. The link form carries your key; treat it like a password.

claude mcp add --transport http ace https://tryacee.com/mcp \
  --header "Authorization: Bearer ace_sk_YOUR_KEY"

Add it next to the blbestate MCP and one chat can pull parcels here and write them to your CRM or a sheet. Client-by-client setup is on Integrations.

SDKs

No dependencies. JavaScript runs in Node 18+, Deno, Bun, Workers and browsers; Python needs only the standard library. Both read ACE_API_KEY.

JavaScript

npm install https://tryacee.com/sdk/tryacee-sdk-1.0.0.tgz

import { Ace } from "@tryacee/sdk";
const ace = new Ace({ apiKey: process.env.ACE_API_KEY });

// 1. Connect an app (send your user to the link once)
const { url } = await ace.apps.connect("slack");
// 2. Find the tool for a task, in plain words
const { tools } = await ace.tools.find("post a message in #sales on Slack");
// 3. Run it
const result = await ace.tools.run("SLACK_SEND_MESSAGE", {
  channel: "#sales",
  markdown_text: "New teardown lead in Maricopa",
});

Python

pip install https://tryacee.com/sdk/tryacee-1.0.0-py3-none-any.whl

from tryacee import Ace
ace = Ace()  # reads ACE_API_KEY
link = ace.apps.connect("hubspot")["url"]       # send the user here once
found = ace.tools.find("create a contact in HubSpot")
result = ace.tools.run("HUBSPOT_CREATE_CONTACT", {"email": "pat@example.com"})

ace.tools.definitions() returns OpenAI or Anthropic tool definitions so your own model can call every connected app; pass its tool call back to ace.tools.run().

Limits and support

• Site MCP and agent endpoints: under one request per second per client.
• Public-records API preview tier: 25 rows per page, 240 expensive reads per minute per client.
• Platform REST API: 120 requests a minute per key. Keys can be revoked any time.
• Removal of a public record: see Contact. Security reports: Contact.

Questions: michael@blbestate.com.