Answer Hub · Software & workflow

What is the difference between the RAZE API and the RAZE MCP for a lender?

Reviewed by
Reviewed by RAZE
Last reviewed

Short answer

The RAZE API is for developers who connect a loan system to RAZE. The RAZE MCP offers the same API to an AI assistant, so a person can ask in plain language. Both reach the same RAZE data with the user's own permissions, and both work beside your LOS and core.

Two ways into the same RAZE data.

There are three ways to order a RAZE draw inspection: the Ordering Engine, the RAZE API and the RAZE MCP. The first is a screen a person works in. The other two connect RAZE to software a lender already runs, and they differ in who does the asking.

RAZE APIRAZE MCP
Who No component provided for KeepTogetherA developer No component provided for KeepTogetherAnyone on the team No component provided for KeepTogether
How No component provided for KeepTogetherCode in your loan No component provided for KeepTogetherA person asks an AI assistant No component provided for KeepTogether
Where No component provided for KeepTogetherThe OpenAPI reference and the Stage sandbox in No component provided for KeepTogetherThe setup page No component provided for KeepTogether
What No component provided for KeepTogetherProjects, orders, status, No component provided for KeepTogetherThe No component provided for KeepTogether

The Model Context Protocol (MCP) is an open specification, published at modelcontextprotocol.io, for how an AI assistant connects to outside software through a defined set of tools. The RAZE MCP is the RAZE API offered as a server on that protocol.

Why it matters for lenders.

The choice follows the work. A lender whose loan system should order inspections and receive the data builds on the RAZE API. A team that already works in an AI assistant uses the RAZE MCP for the same tasks without writing code. Many teams use more than one: order in the Ordering Engine, review from an assistant, or the reverse.

Neither path changes your LOS or core. RAZE works beside the systems you already run and integrates with your existing Construction Loan Administration workflow.

For software platforms.

Build product integrations on the RAZE API, with the OpenAPI reference and the Stage sandbox in the Developer Portal. Use the RAZE MCP to try a workflow in plain language before code is written, and to support users who work in an AI assistant.

How RAZE handles it.

Both paths reach the same RAZE data with the user's own permissions, and an order placed either way creates the same inspection record. Through the RAZE MCP, by default, a summary is shown and the write waits for your confirmation. A user can tell the assistant to skip that step, so set your team's rule: keep confirmation on. Actions taken through the RAZE MCP are logged in RAZE.

Every way to order is included at no platform fee, the RAZE MCP among them. An inspection ordered from an assistant is priced on the same published Rate Card. Your AI assistant subscription is separate.

The RAZE MCP FAQs answer the questions lenders ask next. To begin, Get Started.

Sources

Primary sources only. Where a figure appears on this page, it comes from one of these.

  1. 1.Model Context Protocol specification (revision 2026-07-28)Model Context Protocol · modelcontextprotocol.io
  2. 2.RAZE MCP FAQsRAZE
  3. 3.Draw Inspection API & Developer PortalRAZE
  4. 4.Set Up the RAZE MCPRAZE

See the workflow behind the answer.

RAZE standardizes how draw inspections are ordered, dispatched, captured and delivered, inside the loan administration workflow a lender already runs.

Get Started