Built
Built (Built Technologies) is an AI-powered real estate and construction finance platform that connects capital and information across the construction lending ecosystem. It serves banks, credit unions, private credit firms, owners, developers, and general contractors with construction loan administration, deal origination and underwriting, project financials, invoice and lien-waiver management, compliance tracking, and payments. Founded over a decade ago and headquartered in Nashville and New York, Built operates on one of the largest connected datasets in real estate finance and integrates with Procore, Sage Intacct, Yardi, QuickBooks, Encompass, nCino, and DocuSign. It is backed by Fifth Wall and Index Ventures. This profile was enriched from Built's public developer and trust surfaces; Built publishes an integrations directory, identity/SSO, a status page, and a trust center, but does not expose a public REST API or OpenAPI.
Built is profiled on the APIs.io network. Tagged areas include Company, Construction Technology, Construction Finance, Real Estate Finance, and Fintech.
Built’s developer surface includes engineering blog, documentation, support, changelog, and 14 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Consumer Lending Licensing (UK, US, Canada credit licence registers) | standard | 17.2 (thin) | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Service Levels 1
Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.
Built
SLASecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.