pitch.apis.mortgage

apis.mortgage

Agents can't originate a mortgage. Neither can most software. Both can call one that's licensed to.

A separate property under its own paper: its own entity, its own licenses when granted, its own liability. The entity is in formation. This record sells nothing, quotes nothing, and takes no Application. It takes names.

↓ scroll · arrow keys

You've been burned by this exact page before

You have integrated a mortgage "API" that turned out to be a lead form with developer docs, and a lead form that turned out to be someone else's license. You learned to read mortgage vendors the way an examiner reads a file: who actually holds the paper, what happens at their renewal, and which of your features dies when their arrangement changes.

Meanwhile the mortgage file itself, the most valuable document set in consumer finance, stays uncallable at exactly the edges no license is needed for: which eVault holds control of the eNote, what the attested Payoff figure is with its per-diem and good-through date, what the lien and release status of the Collateral is, what the note and the disclosure set actually say as typed fields. That work sits behind portals, faxes, and vendors whose price is a sales call.

The licensing boundary starts at the URL

Mortgage acts sit under their own federal and state regime. So this property stands apart from its own family on purpose: its own entity, its own licenses when granted, its own liability, never a feature flag on the apis.finance hub. One family key will open it, but what answers behind the URL is this entity, not the hub. And it never redirects into apis.finance in either direction, because a boundary that dissolves into a redirect was never a boundary.

Postedapis.mortgage

The front door is live and states the posture plainly, in its own footer: an entity in formation that holds no license, is not a lender, does not originate, quotes no terms, and takes no Application. The property's own stamp is WAITLIST, nothing of this property is stamped LIVE, and the waitlist is the only live thing this property offers.

Pendinggate: entity formation completed and licenses granted; the formation line is counsel-reviewed on every publish day (fin CONTEXT.md fork D)

"In formation" is a statement of fact with an expiry date, and the family canon requires it to be literally true each day it renders. When the entity exists and a license is granted, this claim flips with evidence; until then, amber is the honest color.

What ships first, under the entity's own paper

The reserved acts wait for the paper. The unlicensed edge of the mortgage file does not, and it ships first, in this order, every row stamped ROADMAP until the day it can say LIVE:

  • eNote / eVault adjacency · typed state on electronic promissory notes: which eVault holds control, transfer and control events attested, under the UCC's control regime for electronic chattel paper. ROADMAP.
  • Doc intelligence · the mortgage file read by machine: the note, the security instrument, the disclosure set, extracted as typed fields with the source page cited. ROADMAP.
  • Payoff / lien data · attested Payoff figures with per-diem and good-through date, lien and release status on mortgage Collateral. ROADMAP.

When a row goes LIVE it will say LIVE, its price will post flat on a machine-readable rate card, and the waitlist will hear it first. Nothing on this record implies otherwise, and nothing here is priced, because nothing here can yet release a fee.

Pendinggate: first capability row LIVE at apis.mortgage with its price posted on the rate card

The first product claim this brand will ever earn is one row flipping from ROADMAP to LIVE on its own front door, price posted, waitlist notified. Until that happens, the capability list above is a build order, not an inventory.

The reserved acts, named, and what refuses them

Four acts are Lender-Reserved: extend credit, take the Application, negotiate terms, decide. They are never performed by software and never pooled to a human either; a licensed Lender performs them or they do not happen. Beneath them sit the licensed acts (notarial, appraisal, MLO, escrow-holder), performed only by credentialed humans under a named sponsoring entity. The boundary covers the conversation, not just the commit: quoting terms and counseling on products are loan-originator acts under the SAFE Act, so utterances gate the same way transactions do.

The design consequence: a call that reaches a reserved act is answered with a typed refusal that names the act, the statute, the party it is reserved to, and the cure route, rather than with a silent failure or a fake approval. The honest state is the differentiator. What this record never claims is that building against the boundary settles anyone's lender status: who the law finds to be the creditor turns on a predominant-economic-interest analysis, not on an API contract. What is claimed is what is mechanically true, and only that.

Pendinggate: typed-refusal surface live at apis.mortgage with the family's ratified BLOCKED cure taxonomy (fin CONTEXT.md, open questions)

The typed refusal is design intent stated in the family's canon, not a shipped surface of this brand. The cure vocabulary itself is draft until ratified, and no refusal object is claimed as product until one can be exercised against a live endpoint here.

One key, one family, and a door that keeps its own paper

Tier grammar is copy law in this family: api.X names one API for one profession; apis.X names a family of APIs sharing one key. apis.mortgage belongs to the apis family and stands apart from it on purpose, and every cross-link between the doors is an ordinary link, never a redirect.

Postedapis.finance

The family hub is live at apis.finance: the kernel, the catalog, the key, and the docs answer at the family's front door.

Postedapis.mortgage

The live apis.mortgage front door reports the family register with its stamps: hub and data door LIVE, origination door ROADMAP, this property WAITLIST.

The stamps are the family's honesty law rendered as product.

Postedapis.mortgage/llms.txt

The machine door is live: /llms.txt states the same facts this deck states, in the same order, for the agent reader. A page an agent cannot parse is a conformance failure in this family, and this one parses.

The mortgage triple

One vertical, three doors, one division of labor. This rail is the API face. closers.mortgage is the human selling door: where the mortgage vertical's offers are sold by people, into an industry that still buys from people. gigs.mortgage is the supply door: the humans who put facts into mortgage files, signing appointments, verifications, field inspections, curative work, paid flat per completed act, never on the direction of any Decision.

The division is the same one the whole estate runs on: the rail meters what migrates to software, the supply door organizes what a credentialed or briefed human must still do, and the selling door puts a human voice on the demand side. Three brands, because a brand is one ICP and one motion; one vertical, because the file underneath is the same file.

Pendinggate: closers.mortgage and gigs.mortgage front doors live with their own records

The sibling doors are records in progress in the same estate wave as this one, not live products, and nothing about their liquidity is implied. The triple is stated here as architecture: the coordinates are held and the records are being drafted, and this claim flips when their doors stand.

Why the slow door wins

The boundary as architecture

license, liability, and URL are one boundary; competitors bolt disclaimers onto lead forms, this property is structurally unable to be one

Namespace + tier grammar

in the agent-discovery layer, the mortgage family door should resolve here the way the finance family resolves to its hub; the plural grammar is already law across the family

Candour as compounding trust

every stamp on the door has been honest since day one, so the first LIVE is believable the day it posts; a burned ICP buys candour before capability

eNote control adjacency

positioned next to the most ownable choke point in the vertical before owning it is possible, with the revisit trigger already written

How it goes to market

The motion is B2A2B: the mortgage technologist's systems and agents calling the rail on their company's behalf, with B2A alongside as agents address the door directly. The channel matches the reader: the record, the machine door, and the namespace position, because this ICP evaluates by reading and their agents evaluate by parsing. Pre-launch there is no paid acquisition and no funnel theater; there is a waitlist whose three questions (what you are building, which surface first, expected volume) are the actual sequencing input for what ships first.

Postedapis.mortgage

The waitlist is live on the front door with exactly those three questions, and it routes to a mailbox answered by a person. In this family a dead mailbox is a conformance failure, and "contact sales" is a dead end by construction.

Where it stands

Stated plainly: this brand is a live front door, a live machine door, a held coordinate inside a live family, and a waitlist. Nothing else, and the deck has said so at every step.

Postedapis.mortgage

Live today: the front door with the ratified hero, the WAITLIST stamp, the ROADMAP capability register, the family table, the boundary clause, and the waitlist intake. Nothing on the page claims more than this paragraph does.

Pendinggate: entity formed; first license granted

The entity clears formation and a license is granted. The claim that unlocks every other claim, and it is not this deck's to make early.

Pendinggate: first row LIVE, price posted, first external caller in production

The claim that matters commercially: an external builder's system calling a LIVE row under a posted price, on this entity's paper. It posts when it has happened, with the record in evidence, and the waitlist hears it before this deck does.

Take a place in line

The waitlist at apis.mortgage is the one live thing this brand offers today, and it is answered by a person.

If this was forwarded to you: apis.mortgage is the mortgage door of the apis finance family, held apart under its own paper because mortgage acts carry their own licensing regime. The entity is in formation, its licenses are not yet granted, nothing is live except the waitlist, and every capability named here is stamped ROADMAP on the live door. That candour is the product for now. If you build mortgage technology: join the waitlist at apis.mortgage. If you know who does: forward this.