Install Jentic One Beta

Connect the Deed API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Deed API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flandregistry.gov.uk%2Flandregistry" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flandregistry.gov.uk%2Flandregistry" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Deed API.

Submit a new digital mortgage deed payload for registration with HM Land Registry

Retrieve a deed document by its reference for review or downstream signing

Extract the structured deed contents for storage in a property workflow system

Validate deed payload contents against the schema before submission

Track a deed by reference across the digital mortgage process

GET STARTED

Start building with Deed API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Deed API for, with concrete tasks.

★ Digital Mortgage Deed Submission

A conveyancing platform creates a digital mortgage deed by posting the structured payload to the Deed API, receiving a deed reference that the borrower and lender can later sign. This replaces the paper deed step in the property purchase or remortgage workflow and ties into HM Land Registry's wider digital registration process.

POST a deed payload containing borrower, lender, charge, and property details to /deed/ and store the returned deed reference for the e-signature step.

Deed Retrieval for Review

A solicitor's case management tool fetches an existing deed by reference to display its contents to the client before signing or to attach the document to a case file. The Deed API returns the structured deed payload, which the application can render in a human-readable form. Useful for audit, review, and reconciliation tasks.

GET /deed/{deed_reference} for the supplied reference and surface the borrower, lender, and property fields for client review.

AI Agent Conveyancing Assistant

An AI agent embedded in a conveyancing workflow uses the Deed API through Jentic to draft and submit a digital mortgage deed, then retrieve it for signing. The agent searches Jentic for deed submission, loads the schema, and executes the call without manually wiring HM Land Registry endpoints. This shortens the time from instruction to signing-ready deed.

Use Jentic to submit a new deed for property TT12345 with the supplied borrower and lender details, then immediately GET the deed by the returned reference to confirm the payload.

Key Endpoints

2 endpoints — the hm land registry deed api supports the digital mortgage deed workflow used to register a deed against a property in england and wales.

METHOD

PATH

DESCRIPTION

POST

/deed/

Create a new digital mortgage deed payload.

GET

/deed/{deed_reference}

Retrieve a deed by its reference.

POST

/deed/

Create a new digital mortgage deed payload.

GET

/deed/{deed_reference}

Retrieve a deed by its reference.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the HM Land Registry Deed API by hand means targeting the api.landregistry.gov.uk host and handling the digital mortgage deed lifecycle yourself. Through Jentic you install once, import the Deed API from the API Directory, store any service credential once, and your agent calls it.

Permission scoping

You choose which Deed operations the agent may call, so you can limit it to the ones it needs, such as creating a digital mortgage deed and retrieving one by reference. Granting retrieval alone lets the agent read a deed without being able to create new ones.

Credential isolation

Any credential issued for the HM Land Registry digital mortgage service is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a digital mortgage deed' or 'retrieve a deed by reference', and Jentic returns the matching Deed API operation with its input schema so the agent calls the right endpoint without browsing the HM Land Registry docs.

FAQs

Specific to using Deed API through Jentic.

What authentication does the Deed API use?

The published OpenAPI spec does not declare a security scheme. In practice the digital mortgage service is restricted to authorised conveyancers and lenders; access is arranged with HM Land Registry rather than self-service. Through Jentic, any credentials configured for the API are stored encrypted in the vault and never enter the agent context.

Can I create a digital mortgage deed with the Deed API?

Yes. POST /deed/ accepts a structured deed payload and returns a deed reference that downstream signing and registration steps use to identify the deed.

Can I retrieve an existing deed with the Deed API?

Yes. GET /deed/{deed_reference} returns the structured deed document for the supplied reference, which clients can render for review or attach to a case file.

What are the rate limits for the Deed API?

The spec does not enumerate rate limits. As an HM Land Registry service, throughput expectations are governed by the digital mortgage onboarding agreement; check with Land Registry directly for production limits.

How do I submit a deed through Jentic?

Search Jentic for 'create a digital mortgage deed', load the operation schema, and POST the payload to /deed/. Capture the returned deed_reference for the signing step.

Is the Deed API free to use?

There is no per-call fee in the spec; access is governed by HM Land Registry's digital mortgage service agreements rather than a public pricing tier.

Can I limit what my agent is allowed to do with the Deed API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Deed operations and credentials the agent may use. You can allow only the operations it needs, such as retrieving a deed by reference with GET /deed/{deed_reference} while withholding the ability to create new deeds with POST /deed/. Granting retrieval alone lets the agent read a deed without being able to submit a new digital mortgage deed.

Landregistry Deed API

Name: Deed API
Brand: Deed API
Availability: InStock

Official vendor OpenAPI document · agent-readyFinanceAccountingnone2 EndpointsREST

For Agents

Create and retrieve digital mortgage deeds with HM Land Registry's Deed API to support property registration workflows.

Use for: I need to create a digital mortgage deed for a property, Retrieve a deed by reference DEED-12345, Submit a new deed payload to HM Land Registry, Get the contents of an existing deed document

Not supported: Does not handle title register searches, property valuations, or stamp duty calculations - use for digital mortgage deed creation and retrieval only.

The HM Land Registry Deed API supports the digital mortgage deed workflow used to register a deed against a property in England and Wales. It exposes operations to create a new deed payload and to retrieve a deed by its reference, returning the structured deed document for downstream signing and registration. The API is part of the Land Registry digital mortgage service and was developed under the Digital Mortgage programme.

Jentic One on Github View OpenAPI Document