Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ResWare

ResWare is customizable title and escrow production software for real estate closings, originally built by Adeptive Software Corporation and acquired by Qualia Labs in December 2020 (now shipping as ResWare 10 within the Qualia ecosystem). It is an on-premises, workflow-driven platform covering title and escrow production, document management and auto-generation, secure communications, and escrow accounting. ResWare exposes an integration API to partners and customers that is historically a SOAP/XML web-service API (built on Windows Communication Foundation / WCF, Microsoft binary protocol by default with Basic Authentication available on request), complemented by newer REST APIs for document handling. There is no public, self-serve developer portal - API access is gated behind a partner/integration program and an "API assistance" package (developer support hours, REST/WCF code samples, and documentation), with pricing on request via [email protected]. The logical service areas below are modeled from partner-integration behavior; ResWare publishes no public API reference or OpenAPI, so no REST surface is fabricated here.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles ResWare the way a machine reads it — 8 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — ResWare scores 10.5/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 10.5/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 1.7 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 8.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
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

How we profile ResWare

Each block below is one kind of artifact we hold for ResWare. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 7

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

ResWare Contacts API

Modeled logical service area for the people and organizations attached to a file - buyers, sellers, lenders, agents, and vendors - and their roles and mappings to partner-side i...

ResWare Files & Orders API

Modeled logical service area for creating and managing title/escrow files (orders) - the core transaction records that carry file number, property, parties, and status through t...

ResWare Documents API

Modeled logical service area for retrieving, uploading, and generating documents attached to a file - closing packages, executed documents, and auto-generated forms. In partner ...

ResWare Tasks API

Modeled logical service area for ResWare's action-based tasks and multi-directional workflow steps that drive a file through its lifecycle - creating, completing, and querying t...

ResWare Accounting API

Modeled logical service area for escrow accounting - trust ledgers, receipts and disbursements, reconciliation, and remittance data tied to a file. Delivered over ResWare's gate...

ResWare Notes API

Modeled logical service area for reading and writing notes and activity entries on a file, used by partners to post status updates and messages back into ResWare. Delivered over...

ResWare Partners API

Modeled logical service area for ResWare's partner-integration framework - the proxy/partner web-service messages that exchange orders, documents, and status with external vendo...

Scroll within the panel for all 7 ·

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

Resware Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for ResWare — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/resware · machine-readable index on apis.io