Rate-lock / float-down timing decision
Lock-window-aware lock-vs-float-down recommendation for a deal already in the pipeline. Given a known lock-expiration date, the currently locked rate, and the float-down cost, returns a defensible hold-lock vs exercise-float-down call a loan officer can document — combining recent market movement (1w/2w/4w window) with payment + break-even math on this loan. Builds on the same recent-movement signal as /v1/buy-timing but framed around the lock window/expiration. A documentable sensitivity scenario, NOT a rate forecast. This route is the single source of truth; the MCP assess_rate_lock tool and the consumer app call it.
Authentication required: Pass your API key in the X-API-Key header.
Request
- Base URL: https://api.rateapi.dev
- URL: https://api.rateapi.dev/v1/rate-lock
- Auth: API key in header X-API-Key
Request body
Example request
{
"product_type": "mortgage",
"state": "CA",
"loan_amount": 400000,
"term_months": 360,
"locked_rate": 6.75,
"lock_expiration_date": "2026-07-15",
"float_down_cost": 500,
"float_down_rate": 6.5,
"float_down_bps": 25,
"since": "4w"
}Response
Lock-vs-float assessment. Degrades gracefully: when the lock is expired the recommendation is extend_or_relock; when rate history is thin, movement fields are null, recommendation is insufficient_data, confidence is low, and a note is included.
Changes
No recorded changes to this operation across all 1 revision of this API.