Coadjute
Coadjute Ltd is a London-based property technology company that operates a shared network for the UK residential property market, connecting estate agents, conveyancers, mortgage brokers, lenders and consumers through the CRM and case-management systems they already use rather than through any multiple listing service — the UK has no MLS and no RESO adoption. Built on R3 Corda distributed ledger technology and now positioned as a fully managed AML and compliance platform for UK property, Coadjute sits in the middle of the transaction as connective infrastructure: property packs, material information, shareable AML checks and status data moving between parties. Its API posture is partner-only and not publicly reachable. Coadjute's own Partner Terms of Service govern "the Coadjute Applet, APIs, Connector, Sandbox, DLT Application" under an Order Form and Subscription Term, and its Network Acceptable Use Policy names a "Partner Cloud API" and an "End User App Plugin" — but the developer portal that once published an API catalogue at developer.coadjute.com returns HTTP 502 as of 2026-07-26, api.coadjute.com answers only with authenticated JSON error envelopes, and no OpenAPI, Postman collection, SDK or public reference could be retrieved. The only publicly fetchable machine-readable contract is the Auth0-backed OpenID Connect discovery document at auth.coadjute.com. Coadjute publishes no open data; the open property-data layer in its home market belongs to HM Land Registry and Ordnance Survey, not to Coadjute.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Coadjute the way a machine reads it — 3 machine-readable artifacts, 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 — Coadjute scores 23.5/100 (emerging), with a separate agent-readiness read of 14/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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Coadjute
Each block below is one kind of artifact we hold for Coadjute. 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.
Security Posture 2
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Coadjute — 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
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lifetise · machine-readable index on apis.io