Key facts

Auth
Authorization: Bearer <key>, one key per business
Spec
OpenAPI JSON
Resources
businesses, client intake applications, projects and matchmaking, deals and deal applications, people, lenders
Webhooks
business, application, autofill, matchmaking and deal events
Format
JSON over HTTPS, cursor pagination on list endpoints

What resources does the API expose?

The resources map one to one onto the MCP tool groups. Businesses hold the profile and people. Client intake applications hold answers, answer files and autofill runs. Projects hold the funding request and matchmaking (criteria, match runs, results and selections). Deals hold a submitted application, its terms and the conversation with the lender. Lenders is a read only directory of who is on the network and their published criteria.

Every write endpoint that changes lender facing state has a review counterpart that returns what would change without changing it, which is how you build a confirmation step into a non chat integration.

What does an end to end call sequence look like?

  1. Create the business (POST /businesses) and the people who own 20% or more.
  2. Create a client intake application and fetch its contract to learn the fields.
  3. Prepare an answer file upload for each document, upload to the signed URL, and confirm.
  4. Prepare and start autofill, poll until settled, list suggestions and accept the ones that are right.
  5. Check submission readiness and fill any gaps with answer updates.
  6. Create a project funding request, calculate matches, read the result summaries.
  7. Update matchmaking selections with the lenders the owner approved.
  8. Submit. Subscribe to deal webhooks to learn about terms and status changes.
curl -H "Authorization: Bearer $KEY" \
  -H "Content-Type: application/json" \
  -d '{"legal_name":"Northside Auto Repair LLC","country":"US"}' \
  https://api.businessloanbroker.ai/v1/businesses

Base URLs and exact paths are in the OpenAPI spec; the snippet above is illustrative.

Remote MCP, OAuth sign in, consent gated submission, free for the business.Server URL https://mcp.businessloanbroker.ai/mcp. Every page here has a markdown twin for retrieval.

Connect the server

Which webhook events exist?

Subscribe to the events that matter for your integration rather than polling:

  • client_intake_application.created, .updated, .status_changed, .submitted
  • client_intake_application_autofill_run.settled
  • project_matchmaking_run.status_changed
  • deal.created, deal.stage_changed, deal.updated
  • deal_application.status_changed, .submitted

Payloads carry the resource id and a summary; fetch the resource for the full state. Deliveries are signed and retried with backoff.

When should I use the API instead of the MCP?

Use the MCP when a person is in the loop in a chat client and you want the consent flow handled for you. Use the API when the application is driven by your own software: a bookkeeping platform that offers financing from inside the product, a franchise system onboarding new units, a lender referral partner. You can combine them: an agent in a chat client for the owner, and webhooks into your system for status.

Are you the business owner?You do not need any of this to apply. Upload your documents on the site and the application fills itself.
Apply now