Availability: Arranged through sales
The BoundaryLogic API plots legal descriptions from deeds, easements, and related land record documents inside your own systems. Send a document or the description text; receive plotted geometry and structured data your software consumes directly. It is the same pipeline behind BoundaryLogic Trace, without the interface.
What it plots
Two classes of description, stated plainly because the difference decides whether your documents fit.
Closed tracts. Metes and bounds and aliquot descriptions: a traverse of calls returning to the point of beginning.
Easements described from a centerline. Strip, corridor, and variable width easements. The description runs a centerline and states a width, and the geometry is generated by offsetting that centerline, curves carried through the offsets. Variable width is handled where the width is stated geometrically, against a course or a described point. See Plotting easements through the API for the full scope, and Limitations for what is not handled.
What comes back
Extracted calls as structured data, the surfaced check values for closed tracts (area, perimeter, closure error, precision ratio, remainder to the point of beginning), and exports: GeoJSON (WGS84), DXF, Shapefile, CSV, and the PDF plot sheet. What the API returns covers the data model in detail.
Where it fits
Continuous document flow. A title production system plotting during examination, a valuation pipeline processing recorded documents as they arrive, a GIS keeping an easement fabric current after a backlog is cleared. For one-time backlogs at volume, Bulk Processing Services is usually the better fit; Bulk Processing or the API? covers the decision.
Access
Access is arranged through sales, per organization. Start with the sales form at boundarylogic.com/talk-to-sales/, or book an API consultation at boundarylogic.com/demo/. Getting access covers what to include and what setup provides. Volume pricing is on the API pricing page.