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.

Coadjute is profiled on the APIs.io network. Tagged areas include Real Estate, United Kingdom, PropTech, Property Transactions, and Conveyancing.

Coadjute’s developer surface includes engineering blog, authentication, support, pricing, and 20 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

26.8/100 thin ▬ flat Agent 15/100 agent aware Front door AI 2/6 trace 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 United Kingdom PropTech Property Transactions Conveyancing AML Compliance Distributed Ledger Estate Agents Mortgage

Kin Score

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

Composite quality — 26.8/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 3.2 / 17

Access Clarity 7.8 / 17

Operational Transparency 2.0 / 11

Contract Governance 1.9 / 10

Discoverability 4.7 / 9

Regulatory Posture 5.9 / 15

Agent readiness — 15/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 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 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 6 / 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 Horizontal (data, software, accessibility, platform) 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/lifetise/"><img src="https://apis.io/badge/lifetise/card.svg" alt="Coadjute 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
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
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

10 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 19.0 — up to +16.2 composite points
Access Clarity scores 46.1 — up to +10.8 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/lifetise/apis.yml: open an issue on github.com/api-evangelist/lifetise 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
Consumer Lending Licensing (UK, US, Canada credit licence registers)	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.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Dynamic Client Registration

measured — observed by APIs.io (published)

Security Posture 2

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

Lifetise Authentication

oauth2/openIdConnect/apiKey · 3 schemes

SECURITY

Lifetise Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Lifetise Scopes

14 scopes · authorizationCode/clientCredentials/deviceCode/implicit

14 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Lifecycle

Lifecycle

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

Authentication

OAuthScopes

Compliance

Operate 4

Status, limits, changes, and where to get help

StatusPage

SLA

Support

Contact

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Pricing

Pricing

Company 5

The organization behind the API

Blog

BlogRSS

Website

Blog

LinkedIn

Other 2

Properties that don't map to a standard resource type

OpenIDConnectDiscovery

OpenIDConnectDiscovery

AcceptableUsePolicy

AcceptableUsePolicy

Source (apis.yml)

aid: lifetise
url: https://raw.githubusercontent.com/api-evangelist/lifetise/refs/heads/main/apis.yml
name: Coadjute
kind: company
description: '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.'
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
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
image: https://www.coadjute.com/hubfs/Logo.svg
tags:
- Real Estate
- United Kingdom
- PropTech
- Property Transactions
- Conveyancing
- AML
- Compliance
- Distributed Ledger
- Estate Agents
- Mortgage
tags_raw:
- Real Estate
- United Kingdom
- PropTech
- Property Transactions
- Conveyancing
- AML
- Compliance
- Distributed Ledger
- Estate Agents
- Mortgage
- Real-Estate
created: '2026-07-26'
modified: '2026-10-06'
specificationVersion: '0.23'
apis: []
common:
- url: https://www.coadjute.com/resources/tag/insights
  type: Blog
- url: https://www.coadjute.com/resources/rss.xml
  type: BlogRSS
- type: DomainSecurity
  url: security/lifetise-domain-security.yml
- type: Website
  url: https://www.coadjute.com/
- type: Authentication
  url: authentication/lifetise-authentication.yml
- type: OpenIDConnectDiscovery
  url: https://auth.coadjute.com/.well-known/openid-configuration
- type: OAuthScopes
  url: scopes/lifetise-scopes.yml
- type: WellKnown
  url: well-known/lifetise-well-known.yml
- type: Conformance
  url: conformance/lifetise-conformance.yml
- type: Compliance
  url: https://www.coadjute.com/our-technology
- type: Lifecycle
  url: lifecycle/lifetise-lifecycle.yml
- type: LLMsTxt
  url: llms/lifetise-llms.txt
- type: StatusPage
  url: https://status.coadjute.com
- type: SLA
  url: https://www.coadjute.com/incident-severity-levels-and-slas
- type: Support
  url: https://www.coadjute.com/help-centre
- type: Login
  url: https://app.coadjute.com/
- type: TermsOfService
  url: https://www.coadjute.com/coadjute-partner-terms-of-service
- type: AcceptableUsePolicy
  url: https://www.coadjute.com/coadjute-network-acceptable-use-policy
- type: PrivacyPolicy
  url: https://www.coadjute.com/privacy-statement
- type: Pricing
  url: https://www.coadjute.com/pricing
- type: Blog
  url: https://www.coadjute.com/resources
- type: GitHubOrganization
  url: https://github.com/coadjute
- type: LinkedIn
  url: https://www.linkedin.com/company/coadjute/
- type: Contact
  url: https://www.coadjute.com/contact-us
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Coadjute API — frequently asked questions

How do I authenticate with the Coadjute API?

Coadjute documents its authentication (oauth2/openIdConnect/apiKey · 3 schemes). The details are profiled on APIs.io as Lifetise Authentication.

Is the Coadjute API ready for AI agents?

Coadjute has a Kin Score of 26.8 out of 100 (thin) and an Agent Readiness score of 15.1 (agent-aware), scored by API Evangelist on 2026-11-06.

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/lifetise"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/lifetise/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.