Closinglock

Closinglock is an Austin, Texas fintech and fraud-prevention company whose platform secures the money movement and identity checks inside a residential real estate closing. Title companies, real estate attorneys, agents, underwriters and their buyers and sellers use it to share wire instructions over an authenticated channel instead of email, verify identity and bank-account ownership before funds move, collect and disburse funds through SecurePay digital payments, retrieve and verify mortgage payoff statements, manage and e-sign closing documents, run two-way text messaging with the parties to a file, and evidence FinCEN and ALTA Best Practices obligations. The company announced SOC 2 Type II certification in August 2023 and raised a $34M Series B led by Sageview Capital in January 2025. Closinglock ships integrations into the major title production systems — SoftPro, RamQuest and ResWare — plus a DocuSign e-signature partnership, but those integrations are built bilaterally with each vendor: as of this profile Closinglock publishes no public developer portal, API reference, or machine-readable contract.

Closinglock is profiled on the APIs.io network. Tagged areas include Real Estate, Title Insurance, Fraud Prevention, Payments, and Identity Verification.

Closinglock’s developer surface includes engineering blog, support, signup flow, and 12 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

17.9/100 emerging ▲ 5.4 Agent 0/100 human only Front door AI 1/6 silent Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

0 APIs

Real Estate Title Insurance Fraud Prevention Payments Identity Verification Document Management Fintech Compliance Security Company

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 17.9/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 1.2 / 17

Access Clarity 6.3 / 17

Operational Transparency 1.2 / 11

Contract Governance 1.9 / 10

Discoverability 4.7 / 9

Regulatory Posture 2.9 / 15

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/closinglock/"><img src="https://apis.io/badge/closinglock/card.svg" alt="Closinglock on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

13 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 7.1 — up to +18.6 composite points
Access Clarity scores 36.8 — up to +12.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/closinglock/apis.yml: open an issue on github.com/api-evangelist/closinglock to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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
Biometrics Testing (biometric recognition vendors, identity verification depth)	undeclared	-	-	-

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.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Closinglock Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Closinglock Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp

SignUp

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Access & Security 4

Authentication, authorization, and security posture

Security

SecurityTxt

DomainSecurity

Compliance

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

Other 1

Properties that don't map to a standard resource type

SecondaryMarketListing

SecondaryMarketListing

Source (apis.yml)

aid: closinglock
name: Closinglock
description: 'Closinglock is an Austin, Texas fintech and fraud-prevention company whose platform secures the money movement
  and identity checks inside a residential real estate closing. Title companies, real estate attorneys, agents, underwriters
  and their buyers and sellers use it to share wire instructions over an authenticated channel instead of email, verify identity
  and bank-account ownership before funds move, collect and disburse funds through SecurePay digital payments, retrieve and
  verify mortgage payoff statements, manage and e-sign closing documents, run two-way text messaging with the parties to a
  file, and evidence FinCEN and ALTA Best Practices obligations. The company announced SOC 2 Type II certification in August
  2023 and raised a $34M Series B led by Sageview Capital in January 2025. Closinglock ships integrations into the major title
  production systems — SoftPro, RamQuest and ResWare — plus a DocuSign e-signature partnership, but those integrations are
  built bilaterally with each vendor: as of this profile Closinglock publishes no public developer portal, API reference,
  or machine-readable contract.'
url: https://raw.githubusercontent.com/api-evangelist/closinglock/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: none
  source:
  - security
  generated: '2026-11-06'
  method: derived
image: https://www.closinglock.com/wp-content/uploads/2025/12/closing_lock_thumb.png
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-09'
modified: '2026-08-09'
tags:
- Real Estate
- Title Insurance
- Fraud Prevention
- Payments
- Identity Verification
- Document Management
- Fintech
- Compliance
- Security
- Company
tags_raw:
- Real Estate
- Title Insurance
- Fraud Prevention
- Payments
- Identity Verification
- Document Management
- FinTech
- Compliance
- Security
- Company
- Real-Estate
- Document-Management
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.closinglock.com/
- type: Blog
  url: https://www.closinglock.com/blog/
- type: BlogRSS
  url: https://www.closinglock.com/feed/
- type: Support
  url: https://www.closinglock.com/contact/
- type: SignUp
  url: https://closinglock.com/login
- type: TermsOfService
  url: https://www.closinglock.com/legal/
- type: PrivacyPolicy
  url: https://www.closinglock.com/privacy-policy/
- type: Security
  url: security/closinglock-vulnerability-disclosure.yml
- type: SecurityTxt
  url: well-known/closinglock-security.txt
- type: WellKnown
  url: well-known/closinglock-well-known.yml
- type: DomainSecurity
  url: security/closinglock-domain-security.yml
- type: Compliance
  url: conformance/closinglock-conformance.yml
- type: Conformance
  url: conformance/closinglock-conformance.yml
- type: LLMsTxt
  url: llms/closinglock-llms.txt
- type: SecondaryMarketListing
  url: https://forgeglobal.com/closinglock_stock/
x-enrichment:
  date: '2026-08-09'
  status: minimal
  artifacts_added: 8
  pass: local-v1
x-coverage:
  state: none
  reason: no-developer-program
  detail: Closinglock ships an end-user closing platform only — its 55-page sitemap contains no developer, API, or integration
    page, api./docs./developer.closinglock.com do not resolve at all, and its SoftPro, RamQuest, ResWare and DocuSign integrations
    are built bilaterally by those vendors rather than through any published API program.
  evidence:
  - url: https://api.closinglock.com/
    status: 0
  - url: https://docs.closinglock.com/
    status: 0
  - url: https://closinglock.com/openapi.json
    status: 404
  - url: https://closinglock.com/graphql
    status: 404
  - url: https://www.closinglock.com/page-sitemap.xml
    status: 200
  - url: https://www.closinglock.com/llms.txt
    status: 404
  - url: https://www.closinglock.com/.well-known/security.txt
    status: 200
  checked: '2026-08-09'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/closinglock"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/closinglock/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/closinglock/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.