Developers
Build on Greenfinch
What you can build
- CRM sync. Push qualified leads into Salesforce, HubSpot or your own system as they happen, and write deal outcomes back.
- Prospecting inside your tools. Look up a building by address from your quoting tool, see who manages it, and reveal the right contact.
- AI agents. Give Claude, ChatGPT or your own agent the same search, research and pipeline actions a rep has, with credits, daily limits and your territory enforced on every call.
- Reporting. Monitor credit balance, export allowance and coverage, and pull pipeline analytics into a dashboard.
Two ways in
Both surfaces use the same API keys, the same account, and the same rules — a refusal on one is a refusal on the other.
| REST API | MCP connector | |
|---|---|---|
| Best for | Your own code: search, unlock and reveal, CRM integrations, webhooks, sync jobs | AI assistants and agents, plus research, lists, pipeline and account tools |
| Base URL | https://app.greenfinch.ai/api/v1 | https://app.greenfinch.ai/api/v1/mcp |
| Shape | Resource endpoints, JSON envelope | JSON-RPC 2.0 over HTTPS — tools/list, tools/call |
| Coverage | 25 endpoints | 77 tools |
| Plan | Team; search, unlock and reveal need Enterprise | Enterprise |
curl -X POST "https://app.greenfinch.ai/api/v1/properties/search" \
-H "Authorization: Bearer $GREENFINCH_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"query": "1200 Commerce Pkwy, Plano, TX",
"limit": 5
}'MCP is an ordinary HTTPS API too
MCP (Model Context Protocol) is how AI assistants call tools, but nothing about it requires an AI: any program that can send a JSON POST with an API key can call a tool and get JSON back. Use it for what REST does not cover yet — research, pipeline changes, saved searches and account tools.
Plans
| Plan | What your API keys can do |
|---|---|
| Team | The integration scopes: receive qualified leads by webhook, read single lead bundles, write back deal outcomes, sync customer accounts, read events, notes, lists and property records, and manage lists. 120 requests per minute per key. |
| Enterprise | Everything in Team, plus data:read and data:unlock (search, read, unlock and reveal properties, contacts and organizations over REST) and the mcp scope (the full tool surface for AI agents) — and 300 requests per minute per key. |
Access is checked against your organization's live plan on every call, so an upgrade or downgrade takes effect on the next request. See Authentication for what each plan includes and the full scope list.
API and connector access is bounded by limits that scale with the size of your Enterprise plan. Alongside the request rates and daily limits, an Enterprise order states a records allowance — how many distinct records your programs may take per billing period, counted once per record across every door, with looking in the app unaffected. Your order states the numbers, and the app and the API both show what is left.
From nothing to useful data
A typical integration follows the same path, whichever surface it uses:
- 1
Find
Search properties by address or by criteria (
greenfinch_search_properties), find people by name or employer (greenfinch_find_contacts,greenfinch_browse_contacts), or browse the firms that own and manage buildings (greenfinch_browse_organizations). - 2
Keep the IDs
Every result carries a Greenfinch ID — a UUID for a property, contact, organization or list. Store it next to your own record; every other call takes it.
- 3
Read and reveal
Read detail (
GET /properties/{id}/detail), unlock a property and all its contacts for 10 credits (POST /properties/{id}/unlock), or reveal one contact for 5 (POST /contacts/{id}/reveal). Each has an MCP tool twin for AI agents. - 4
Organize
Put what you found on a saved list (
POST /lists/{id}/items,greenfinch_add_to_list) and qualify the leads worth pursuing (greenfinch_qualify_lead). - 5
Export
Pull a CRM-ready lead bundle one property at a time (
GET /leads/{id}), a page of a list at a time (greenfinch_get_lead_bundles), or receive one automatically when a lead is qualified (webhooks). - 6
Write back
Report won and lost deals from your CRM (
POST /leads/{id}/status) and keep Greenfinch in step with who your customers are (POST /customer-accounts/sync).
The Quickstart walks through finding, reading, unlocking and revealing with real requests.
Explore the docs
Quickstart
Authentication
REST API
MCP connector
MCP tool reference
Webhooks
Lead bundles
Limits and errors