Loom API

Ask a question from your application. Loom finds relevant data, calls the enabled tools and brings the results into a conversation you can follow up on.

Loom or individual MCP servers?

Use Loom's HTTP API when you want it to coordinate the work: resolve the deal, find the table, query the records and inspect the evidence. Your application supplies the question and presents the answer.

Use the individual MCP servers when your own agent should choose and call the tools. Reveal handles discovery, Data queries records, Evidence inspects source trails, and GEO resolves places. Access and coverage are agreed for either route.

What's the balance on loan 25 in WFCM 2020-C58?

For teams adding a question-and-answer workflow to their own application.

Interface: HTTP API
Access: Request access
Availability: Access by arrangement
Runs on: Hosted service

Account and API key required. Contact us to agree on data scope and integration; there is no self-service registration.

Request Loom API access

Cairn roles: AI connectors, Public records library
Evidence roles: Source, Citation
Semantic context: Source meaning, Entity identity, Relationships
Contribution: Bring catalog discovery, data reads, evidence and geography into a cited conversation over the available corpus.
Limit: Coverage and permissions depend on the connected services; confirm News availability during provisioning.

Questions this tool can support

What’s the balance on loan 25 in WFCM 2020-C58?
Coordinate discovery and data queries over HTTP using provisioned services. A composed API does not include an automatically configured white-label operating service.
Available by arrangement
When did the borrower last pay?
Ask follow-up questions over the available records. Interpretations still need review; a paid-through field does not establish when cash arrived.
Available by arrangement
Text me when that changes.
An application could call the API as part of an agreed recurring check. Scheduling, change rules, evidence retention and authorized delivery are not activated by API access alone.
Potential use, not demonstrated here

What it does

Resolve a named deal and find the relevant dataset.
Inspect the schema and query records through enabled data tools.
Use evidence and geographic tools where the question calls for them.
Carry the deal and loan into a follow-up question in the same conversation.

A checked backend example

Ask for loan 25's scheduled and actual balances in WFCM 2020-C58 for October 2026.

In a November 4 backend test, Loom resolved the deal, found and described the table, and queried the loan in four read-only calls. It returned a scheduled balance of $9,268,821.88 and an actual balance of $9,399,496.50 for October 13. We checked both against the SEC exhibit.

The test used the data-access procedure. Follow-up interpretations needed review: a paid-through date is not a payment timestamp. This was a backend test, not an SMS transcript.

Follow the worked CMBS questions

Setup

Tell us the questions your application needs to answer and the data it should use. We will confirm scope, enabled services, credentials and the current API contract before you connect.

Request Loom API access

Coverage and freshness

Available datasets, source dates and operations depend on the services enabled for your account. Reveal, Data, Evidence and GEO form the existing stack. News is joining it; confirm provisioning before relying on news coverage.

Limits

Check field definitions, dates and sources before using an answer. A correct query does not make every interpretation correct.
A catalog entry does not establish current source coverage or permission to query its rows.
Holdings matching and recurring alerts require agreed inputs and setup.

Related tools and guides

Contact support

Want Cairn to do the work?

Follow the CMBS questions to see what each answer needs. You can ask Cairn directly or discuss an ongoing assignment through Hire Cairn.

For Cairn under your firm’s name, discuss white-label Cairn. We agree on the questions, data access, branding and who will operate it. Loom API access is one integration option; a firm-branded service needs its own agreed scope.