WesternAgent ONE API integration services (net sheets & closing costs)

1 — CRM-embedded instant net sheet

Context: a brokerage wants agents to produce a seller net sheet from inside their CRM without re-keying. Data/API: POST /netsheet with the listing's price, payoff, commission, and county; response is the line-item proceeds breakdown plus a branded PDF URL. OpenData mapping: the net sheet becomes a structured resource the CRM owns and can re-query — the same "your data, via an API" principle Open Banking applies to statements.

2 — Lender pre-qual & cost-to-close sync

Context: a loan origination system needs a realistic buyer estimate aligned with the agent's numbers. Data/API: POST /buyer-estimate returns PITI, prepaids, reserves, lender and title fees; the LOS reconciles it against the Loan Estimate. OpenFinance mapping: shared, machine-readable cost figures across agent and lender — exactly the data-portability goal of TILA-RESPA disclosure alignment.

3 — Multi-county relocation comparison

Context: a relocation platform wants "what will closing cost in County A vs. County B?" Data/API: GET /closing-costs?county=... pulls recording fees, transfer taxes, and title rate bands; the platform diffs two counties for the same price point. OpenData mapping: reference data exposed as a queryable service rather than a PDF buried in an app.

4 — Title company quote & audit pipeline

Context: a title agency wants every quote it issues logged with the rate source. Data/API: the title rate card endpoint plus a webhook that fires when a net sheet is generated; each event is written to the agency's warehouse with the underwriter, state, and price band used. OpenFinance mapping: consented event streams + immutable records, the audit pattern regulators expect.

5 — "Cost of waiting" nurture automation

Context: a marketing platform wants to re-engage fence-sitting buyers. Data/API: HomeLink Intelligence holding-cost + Buy Now vs. Buy Later appreciation data, scheduled monthly per saved property; the platform emails an updated cost-of-waiting card. OpenData mapping: a derived-data feed the marketing system subscribes to, refreshed on a cadence the user authorised.

A. Authentication (token exchange)

POST /api/v1/westernagent/auth/token
Content-Type: application/json

{
  "client_id": "<ISSUED_CLIENT_ID>",
  "client_secret": "<ISSUED_SECRET>",
  "grant_type": "client_credentials",
  "scope": "netsheet:read buyer-estimate:read closing-costs:read"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "token_type": "Bearer",
  "expires_in": 3600,
  "scope": "netsheet:read buyer-estimate:read closing-costs:read"
}

# On 401: refresh via the same endpoint.
# On 429: honour Retry-After; we ship an exponential-backoff client.

B. Seller net sheet generation

POST /api/v1/westernagent/netsheet
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json

{
  "state": "TX",
  "county": "Travis",
  "sale_price": 525000,
  "existing_loan_payoff": 312400,
  "listing_commission_pct": 3.0,
  "selling_commission_pct": 3.0,
  "closing_date": "2026-06-15",
  "hoa_transfer_fee": 250,
  "home_warranty": 600
}

200 OK
{
  "gross_sale_price": 525000,
  "deductions": {
    "loan_payoff": 312400,
    "listing_commission": 15750,
    "selling_commission": 15750,
    "owner_title_policy": 3245,
    "escrow_settlement_fee": 350,
    "recording_fees": 110,
    "transfer_tax": 0,
    "property_tax_proration": 4180.22,
    "hoa_transfer_fee": 250,
    "home_warranty": 600
  },
  "estimated_net_proceeds": 172614.78,
  "pdf_url": "https://.../netsheet/2f9c....pdf",
  "rate_source": "TX promulgated title rate (filed)"
}

C. Webhook: net sheet generated

POST https://your-app.example.com/hooks/westernagent
X-Signature: sha256=...
Content-Type: application/json

{
  "event": "netsheet.generated",
  "occurred_at": "2026-05-11T14:08:31Z",
  "account_id": "agent_88231",
  "office_id": "title_co_4410",
  "resource_id": "netsheet_2f9c8a",
  "state": "TX",
  "county": "Travis",
  "sale_price": 525000,
  "estimated_net_proceeds": 172614.78,
  "rate_source": "TX promulgated title rate (filed)"
}

# Verify X-Signature with the shared secret before processing.
# Idempotency: dedupe on resource_id + event.

D. Buyer estimate (compact)

POST /api/v1/westernagent/buyer-estimate
Authorization: Bearer <ACCESS_TOKEN>

{ "state":"TX","county":"Travis","purchase_price":525000,
  "down_payment_pct":10,"loan_type":"conventional",
  "term_years":30,"interest_rate":6.625 }

200 OK
{ "loan_amount":472500,"principal_interest":3025.41,
  "monthly_tax":875.00,"monthly_insurance":145.00,
  "monthly_pi_ti":4045.41,"lender_fees":1685,
  "prepaid_interest":686.13,"escrow_reserves":3060.00,
  "owner_title":3245,"lender_title":150,
  "estimated_cash_to_close":62311.13 }

Regulatory alignment

Closing-cost figures are consumer-facing financial estimates, so the deliverables are designed to sit cleanly next to the disclosure regime. We align net sheet and buyer-estimate output with the structure of the TILA-RESPA Integrated Disclosure (TRID) Loan Estimate / Closing Disclosure, keep RESPA Section 8 (anti-kickback) considerations in mind for co-branded outputs, and add fields for the FinCEN Residential Real Estate Reporting Rule (effective March 1, 2026) when a workflow touches non-financed transfers — PalmAgent itself added FinCEN alerts to its platform. Title rate cards reference the relevant state-promulgated or filed rates and ALTA policy forms.

Data handling

• Access only under written client authorization or via documented public endpoints — no credential sharing beyond what you provision.
• Data minimization: we request only the fields a scenario needs; PII (client names, addresses) is optional and can be tokenised.
• Consent and request logging, retention windows you set, and deletion on request.
• Encryption in transit (TLS) and at rest; signed webhooks; scoped, rotatable API tokens.
• NDA and DPA available; we will not implement or document anything that circumvents WesternAgent ONE or PalmAgent access controls.

PalmAgent ONE

PalmAgent's flagship "real estate's #1 closing cost app." Same calculation engine as WesternAgent ONE, just the unbranded build — net sheets, buyer estimates, HomeLink Intelligence. An integration here generalises directly.

FidelityAgent ONE

Brought by Fidelity National Title, a city/county-specific closing cost app for generating buyer estimates and seller net sheets on iPhone and iPad. Holds the same shape of transactional data with Fidelity's rate cards.

IndependenceTitleAgent ONE

Independence Title's branded net sheet and closing-cost app. Stores buyer/seller estimates and Texas-market fee schedules — a natural candidate for the same unified export.

WestTXAgent ONE

A West Texas-focused PalmAgent build. Same engine, region-specific county data; useful when a brokerage spans multiple branded apps and wants one consolidated dataset.

WesternPower ONE

Another PalmAgent-family app for closing-cost calculation. Holds net sheets, buyer estimates, and local cost tables that map cleanly onto the same API schema.

UnityAgent ONE

A branded "ONE" app in the same lineage, used by agents to produce client-facing estimates. Part of the cross-app data picture an integrator typically consolidates.

TitleCapture

A title-quote platform whose net sheet accounts for closing costs, recording & transfer fees, mortgage payoffs, property taxes and HOA dues, with website calculators. Different vendor, overlapping data — a common "we also use TitleCapture" pairing.

CostsFirst (First American Title)

First American Title's desktop-and-mobile tool for buyer monthly/down-payment and seller-net calculations. Teams comparing CostsFirst output with PalmAgent's often want both in one warehouse.

Opendoor Home Sale Calculator

A consumer-facing estimator that subtracts commissions, closing costs and mortgage payoff from an expected sale price. Adjacent data, useful as a sanity-check feed alongside professional net sheets.

MortgageCalculator.org Net Proceeds

A web seller-net-proceeds calculator driven by sale price, mortgage info and closing date. Lighter than a county-specific net sheet, but part of the same keyword and use-case space.

Deliverables checklist

• API specification (OpenAPI / Swagger) for net-sheet, buyer-estimate, closing-cost-reference, and webhook endpoints
• Protocol & auth-flow report (token / session chain, request signing, rate limits)
• Runnable source for the core endpoints in Python and Node.js, with an exponential-backoff client
• CSV/Excel and branded-PDF export helpers
• Automated tests, a Postman/Insomnia collection, and written API documentation
• Compliance guidance (TRID-aligned fields, RESPA Section 8 notes, FinCEN RRE fields, data retention)

Engagement models

• Source code delivery — from $300. You receive runnable API source code plus full documentation; pay after delivery once you're satisfied it works.
• Pay-per-call hosted API. Use our hosted endpoints and pay only for the calls you make — no upfront cost; good for teams that prefer usage-based pricing.
• NDA / DPA on request; optional ongoing maintenance as PalmAgent ships updates.

About us

We are an independent studio focused on app protocol analysis and OpenData / OpenFinance API integration, with engineers who have shipped work for banks, payment gateways, title and real-estate platforms, and cloud infrastructure teams. For a tool like WesternAgent ONE that means we understand both the technical side (mobile session flows, request signing, rate limiting) and the domain side (net sheets, title insurance rate filings, TRID, RESPA, the FinCEN real-estate rule). We deliver end-to-end: protocol analysis → API design → build → validation → compliance notes.

• Real estate fintech, payments, digital banking, and data-export integrations
• API gateways, webhook pipelines, and security reviews
• Custom Python / Node.js / Go SDKs and test harnesses
• Source code delivery from $300 — runnable code and full docs, pay after delivery upon satisfaction
• Pay-per-call hosted API — pay only per call, no upfront cost

Contact

For a quote, or to submit your target app and requirements (counties/states in scope, the endpoints you need, expected call volume), open our contact page:

Contact page

Note: WesternAgent ONE and PalmAgent are products of PalmAgent Software (support: support@palmagent.com). We are an independent integration studio and are not affiliated with PalmAgent.

Engagement workflow

1. Scope confirmation: which flows (net sheet, buyer estimate, closing-cost reference, HomeLink), which states/counties, expected volume.
2. Protocol analysis and API design (typically 2–5 business days, complexity-dependent).
3. Build and internal validation against real scenarios (typically 3–8 business days).
4. Documentation, sample code, Postman collection, and test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; white-label variants or third-party approvals may extend timelines.

FAQ

What do you need from me to start a WesternAgent ONE integration?

How long does delivery take?

How do you handle compliance with RESPA and FinCEN rules?

Can you cover the other PalmAgent-branded apps too?