Form entry
The redesigned URAR, the Restricted Appraisal Update and the Completion Report, with GSE labels, options and maximum lengths enforced as you type.
Form entry, live GSE compliance checks, MISMO 3.6 XML, GSE-style PDFs and UCDP preflight. One API, branded as your own.
Built from the published GSE specification: Appendices A, D, E, F and H.
Five hard problems that every appraisal platform has to solve for UAD 3.6. UAD Engine ships them as one tested API.
The redesigned URAR, the Restricted Appraisal Update and the Completion Report, with GSE labels, options and maximum lengths enforced as you type.
Every Appendix H-1, H-2 and H-3 rule, with each finding pointed at the field that caused it. Fix it before UCDP sees it.
Lossless read and write, validated against the GSE XSD itself. Import an existing report, edit it and export it again.
The report PDF laid out to the Appendix E style guide, with comparable grids, defect tables and photos in place.
Send a delivery package and get UCDP's own SYS findings back before you submit it.
Rendering the redesigned URAR is where most UAD 3.6 projects stall. UAD Engine prints every report field in Report Field ID order, to the GSE style guide, straight from the XML.


REST and JSON, keys per tenant, and errors that name the field. Check a report in one call.
curl https://uadengine.com/v1/validate \
-H "Authorization: Bearer $UAD_API_KEY" \
-H "Content-Type: application/xml" \
--data-binary @report.xmlimport { readFile } from "node:fs/promises";
const res = await fetch("https://uadengine.com/v1/validate", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.UAD_API_KEY}`,
"Content-Type": "application/xml",
},
body: await readFile("report.xml"),
});
const { valid, issues } = await res.json();import os, requests
res = requests.post(
"https://uadengine.com/v1/validate",
headers={"Authorization": f"Bearer {os.environ['UAD_API_KEY']}",
"Content-Type": "application/xml"},
data=open("report.xml", "rb"),
)
print(res.json()["issues"]){
"valid": false,
"issues": [
{
"severity": "error",
"ruleId": "UAD1002",
"fieldId": "subject.city",
"message": "Provide the city name for the subject property physical address.",
"path": "/MESSAGE/.../ADDRESS/CityName"
}
]
}Drop the uad-form web component into your app. It takes your colour, logo and font, works in light and dark mode, and runs on phones.
<script src="https://uadengine.com/embed.js" defer></script>
<uad-form api="https://uadengine.com"
report="rpt_8f2k…" token="emb_…"></uad-form>Run your own branded forms software without hiring a compliance team.
Move to UAD 3.6 on a tested engine and spend your roadmap on what makes you different.
Check reports and delivery packages against the GSE rules before they reach UCDP.
Each report is checked against the rules for its own type.
| Report | Appendix | Rules | Automated |
|---|---|---|---|
| Uniform Residential Appraisal Report (URAR) | H-1 v1.5 | 728 | 728/728 |
| Restricted Appraisal Update | H-2 v1.3 | 102 | 102/102 |
| Completion Report | H-3 v1.3 | 102 | 102/102 |
Separate tenants, API keys and branding for every client.
Browser-safe tokens scoped to one report, with an expiry.
Who changed what, kept even after a report is deleted.
Reports, PDFs, packages and validations counted per month.
Per-tenant limits with standard headers and Retry-After.
Version-checked writes, so two saves can never overwrite each other.
The new Uniform Appraisal Dataset from Fannie Mae and Freddie Mac, together with the redesigned URAR. Since November 2, 2026, new appraisals submitted to UCDP must use it.
Yes. The form, the PDF and the software identity in the XML can all carry your company's name, colours and logo.
The URAR, the Restricted Appraisal Update and the Completion Report, each checked against its own GSE rule set (H-1, H-2 and H-3).
Yes. Send any UAD 3.6 XML to the validation endpoint, or a full delivery package to preflight, and get the findings back by field.
Fannie Mae and Freddie Mac each verify appraisal software themselves. Contact us for UAD Engine's current status and what it means for a product built on it.
By usage: reports created, PDFs rendered, packages built and validations run. Get in touch and we'll quote for your volume.
Tell us what you're building. We'll set you up with an API key and a sandbox tenant.
Request access →Or email [email protected]