API 1.2.0: a spec that matches production, JSON numbers, and new SDKs
The OpenAPI spec now describes what the API actually returns, for all 70 operations, and CI validates it against recorded production responses on every change. Sixteen endpoints that worked but were undocumented are now in the spec (lookup, lookup/batch, parcels/batch, comps, occupants, violations, market snapshot, CMBS exposure, freshness and more).
Compatibility note: every field the spec types as a number is now a JSON number. Values such as total_assessed_value used to arrive as strings ("19388200.00"). Code that converted them with Number() or float() keeps working; code that called string methods on them must change. Identifiers such as parcel_id, county_fips and zip stay strings. Errors are RFC 7807 problem bodies everywhere.
@propraven/sdk@0.3.0(npm),propraven 0.2.0(PyPI) andgithub.com/jdw2111/propraven-go v0.3.0: generated from the spec in each SDK repo, covering every operation, with retries on 429/503/504, typed errors, pagination helpers and webhook signature verification. These are breaking releases: new client names and namespaces (client.parcels.get).@propraven/mcp@0.2.0: tool names the Anthropic API accepts (parcel_lookup, …), and no tool can trigger a paid call.- The Postman collection is regenerated from the spec (70 requests).