Build on LenDb.

What you get

• Read API at /api/v1: ranked loan officers for a situation and place (/match?q=), profiles by NMLS ID, lenders, and the specialty taxonomy. Described by an OpenAPI 3.1 document.
• MCP server at https://lendb.ai/mcp (streamable HTTP): find_loan_officers, get_loan_officer, get_lender, list_specialties, explain_specialty, plus request_api_key and claim_api_key.
• Every answer is sourced and carries a canonical_url to cite. Phone numbers and email addresses are never in the API or MCP, with or without a key.

Limits

Over a limit you get HTTP 429 with Retry-After. Keyed responses carry X-LenDb-Key-Prefix, RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset for the minute window, and X-LenDb-Daily-Limit and X-LenDb-Daily-Remaining for the day. Up to 5 active keys per account. Need more? Tell us.

Quick start

Without a key:

curl 'https://lendb.ai//api/v1/match?q=VA%20loan%20in%20San%20Diego'

With a key, send it as a bearer token (preferred). ?api_key= also works where you cannot set headers.

curl -i 'https://lendb.ai//api/v1/match?q=duplex%20in%20Austin,%20self-employed' \
  -H 'Authorization: Bearer ldb_live_...'

Connect the MCP server

Claude Code

claude mcp add --transport http lendb https://lendb.ai/mcp \
  --header "Authorization: Bearer ldb_live_..."

Claude (claude.ai and Claude Desktop)

Add a custom connector in Settings, Connectors, with the URL https://lendb.ai/mcp, or https://lendb.ai/mcp?api_key=ldb_live_... for your key's limits. No OAuth needed.

ChatGPT

Turn on developer mode, then add a custom connector (MCP server) with the same URL, with ?api_key= if you have a key, and no authentication.

Cursor

In ~/.cursor/mcp.json:

{
  "mcpServers": {
    "lendb": {
      "url": "https://lendb.ai/mcp",
      "headers": { "Authorization": "Bearer ldb_live_..." }
    }
  }
}

Any other MCP client: {"lendb": {"url": "https://lendb.ai/mcp"}}.

Agents can ask for a key

An agent can request a key for its person, who approves it by email. Nobody else sees the key: it is shown once to the person who approves, and handed once to the agent that asked.

1. POST /api/v1/keys/request with {"email": "...", "use_case": "...", "name": "optional"}, or the MCP tool request_api_key. The answer has a request_id, a one-time claim_secret and a poll_url.
2. We email a link to that address. The person reviews the request, accepts the terms and approves it.
3. The agent polls GET /api/v1/keys/request/{request_id} with Authorization: Bearer <claim_secret> (or the MCP tool claim_api_key) every 10 seconds or slower, and receives the key once.

curl -X POST https://lendb.ai//api/v1/keys/request \
  -H 'content-type: application/json' \
  -d '{"email":"you@example.com","use_case":"Find VA loan officers for my clients","name":"my-agent"}'

Requests are limited per email address and per network, and expire after 24 hours.

The rules, briefly

• Cite the canonical_url and pass along the reasons we return.
• Keep keys secret. Do not put them in public code or client-side apps; revoke a leaked key in your dashboard.
• Using a key means you accept the Terms of Use, including the API section. Verify licenses at NMLS Consumer Access↗ (opens in a new tab).

More for machines: llms.txt, the guide for bots, and the OpenAPI document.