California deeds, prepared correctly and confirmed by a named human
The same engine behind the application escrow officers work in and the API platforms build on.
I'm building a product that prepares deeds
REST in, recorder-formatted PDF out — after your officer confirms it. The instrument doctrine is enforced at the request boundary, so a wrong deed fails in your tests, not at the counter.
{
"deed_type": "grant_deed_jt",
"grantee": {
"vesting": "a single man"
}
}A Joint Tenancy deed states its vesting on its own face. Choosing this instrument is the vesting decision.
I prepare deeds for California transactions
A guided wizard that prefills from county records and a preliminary title report, then puts every field in front of you to confirm before it prints. PCOR and BOE filled from the deed.
CITY OF LOS ANGELES
Submit the facts.
A human confirms the deed.
Anyone can render JSON into a PDF. A deed is a legal instrument, and the question a recorder, a title insurer and eventually a court asks is not which service formatted it — it is who decided. So there is no path through DeedPro, app or API, that produces a recordable document without an answer to that.
County records and title reports prefill what they can — each value carrying the name of where it came from. Nothing is treated as an answer yet, and no PDF exists.
Every material field requires explicit confirmation from a professional, by name, against the instrument as it will actually render. An anonymous service account cannot do this.
Hash-stamped at creation and stored insert-or-refuse — a differing hash is rejected rather than overwriting what is there — alongside a record of who confirmed what, and when.
A licence number can be recorded alongside the name when your integration sends one. It is optional, it is stored as supplied, and it is never verified by DeedPro — the confirmation record calls it license_claimed so no reader mistakes it for a check we performed.
County records prefill APN, legal description, and owner — as suggestions.
Every material field requires explicit confirmation before anything generates.
Who confirmed what, and when — stored with a hash-stamped, immutable PDF.
DeedPro is software, not a law firm. It prepares documents at the direction of the professional using it and does not provide legal advice or legal determinations.
The app and the API are the same thing, seen from two sides
Not a platform bolted onto a product, or a product carved out of a platform. The same templates, the same page geometry, the same confirmation requirement, the same hash-stamped output — which is why the county formatting is right in both, and why neither can print a deed nobody read.
Your officer works the wizard. Prefilled values show their source, exemptions explain what they cover, and each material field is confirmed one at a time. Corrections keep full lineage to the superseded document.
What the confirmation is here: the officer's own authenticated session. The deed is confirmed because she is signed in and worked it — there is no separate confirmation record.
- 21 recordable instruments, incl. affidavits and declarations
- PCOR and BOE forms filled from the deed
Your system posts the transaction and gets back a draft with a hosted review URL. Your officer opens it, reads the rendered instrument, and approves — or rejects it with a reason. The stored PDF exists only after that.
What the confirmation is here: a stored record naming the person, their role and the moment — retrievable per deed. That is the honest difference between the two paths, and it is why the API is the stricter surface.
- 9 deed-family instruments
- Confirmation record retrievable per deed
One deliberate difference. affidavits and declarations stay in the app. Their premise is a hand at the moment of execution — sworn statements, initial lines, checkbox elections — and a machine-to-machine call has no hand. That is a boundary, not a gap in the roadmap.
The hard part was never the PDF
A weekend gets you a templating library and a page that looks like a deed. What it does not get you is the doctrine: which instruments carry their vesting on their own face, which recite an organizing state, which cannot be machine-generated at all.
We encode them, which is why a mis-specified instrument comes back as an error naming the field rather than as a plausible-looking document.
Read the full instrument table| deed_type | grantee.vesting | also required |
|---|---|---|
| grant_deed | required | — |
| quitclaim_deed | optional | — |
| interspousal_transfer | required | — |
| warranty_deed | required | — |
| tax_deed | required | — |
| grant_deed_jt | fixed — sending it is a 422 | — |
| grant_deed_cp_ros | fixed — sending it is a 422 | — |
| grant_deed_corp | required | entity_state |
| grant_deed_partnership | required | entity_state, partnership_type |
County formatting — margins, fonts and the statutory furniture — is measured against California recorders' published requirements. Acceptance is still the recorder's call.
Nothing reaches the deed unseen
County-record and title-report data arrive as candidates, never as answers. Your officer confirms every one before anything prints, and the record keeps who confirmed what, and when.
Guided wizard
Clean, accessible forms with inline validation. Values arrive from county records with their source named, and the exemptions explain what they cover.
County formatting built in
Margins, fonts and the statutory furniture, measured against California recorders’ published requirements and surfaced for your officer’s review. Acceptance is the recorder’s call.
Review and print
Two-stage checks — substantive completeness, and formatting measured against the recorder’s published requirements. One click produces the final, hash-stamped PDF for her to record.
| Feature | DeedPro | Manual |
|---|---|---|
| Time to complete | 5-10 min | 45-90 min |
| Every field confirmed before printing | ||
| Recorder formatting checks | Built-in | Manual tracking |
| Multi-user collaboration | ||
| API access — same confirmation step | ||
| SmartReview validation |
Security you can check yourself
No certifications to wave. These three are things you can confirm on your own file — and the trust page leads with what we do not have.
Hash-stamped PDFs
Every PDF is fingerprinted (SHA-256) at creation, and the row that holds it is insert-or-refuse: a differing hash is rejected rather than overwritten.
Encrypted sessions
Token-based authentication over encrypted transport; sessions expire and say so.
The officer decides
Every material field requires explicit confirmation — recorded with who, what, and when.
Pricing
Offices pay for seats. Platform pricing is set on the call that issues your key.
Test keys, real PDFs on the same templates, the full confirmation flow. Build the whole integration on it before you commit to anything.
Request a test keyThere is no published per-deed rate yet, and we would rather tell you that than print a number we would renegotiate. Live keys are issued by hand after a conversation about what you are building.
Request accessFree
The whole product, on real files. Nothing is held back.
- 21 recordable California instruments
- PCOR and BOE forms filled from the deed
- Every field confirmed by you before it prints
- Immutable, hash-stamped PDFs
- Corrections with full lineage to the superseded document
Professional
For the officer who drafts every day.
- 21 recordable California instruments
- PCOR and BOE forms filled from the deed
- Every field confirmed by you before it prints
- Immutable, hash-stamped PDFs
- Corrections with full lineage to the superseded document
- Priority support
Business
Shared files across an office — an assistant preps, an officer reviews, and cover carries when someone is out.
- 21 recordable California instruments
- PCOR and BOE forms filled from the deed
- Every field confirmed by you before it prints
- Immutable, hash-stamped PDFs
- Corrections with full lineage to the superseded document
- Shared matter list across the office
- Priority support
Not yet available
Questions we would rather answer now
Is this only California?
Yes, for now. The templates are measured to California county recorder requirements and the data models are CA-specific. If you need a second state, we are the wrong vendor and will say so on the first call.
Does it connect to SoftPro, Qualia, or ResWare?
Not today. Property details can come from a county-record lookup or a preliminary title report you upload; everything else is entered. Title-software integration is not built yet, and we would rather say so than let you find out on your first file.
Why does the API cover fewer instruments than the app?
The app offers 21; the API exposes the 9 deed-family instruments. The difference is the affidavit and declaration family, whose premise is a hand at the moment of execution.
Who is allowed to confirm a deed?
A named person, recorded with their name and role. A service account cannot confirm. A licence number can be recorded when supplied, and is never verified by us.
What if the recorder rejects a document?
Formatting is measured against published requirements and surfaced for review, but acceptance is the recorder's call and we do not claim otherwise.
What about certifications?
No badges to wave. The trust page lists what exists and what does not, gaps first — including the ones a security review would ask about.
How are API keys issued?
By request rather than switched on by plan. You submit an inquiry, we talk, and a key is issued by hand — sandbox keys included.
Can I save partial work?
Yes. All wizard progress auto-saves. You can return anytime to complete.
Tell us what you are building. Keys are issued after a short conversation.
Every instrument, on real files. Paid plans add support and shared office files — not features.