Availability: Arranged through sales
Where the API sits in real systems. Use this page to shape a technical spec and to answer the internal question every evaluation reaches: what would this look like in our stack.
Title production
Plot during examination rather than after it. The examination system posts the deed or the description text as it enters the workflow, and the plotted geometry and check values come back into the examiner’s view: the boundary drawn, the closure and precision surfaced, with your team reviewing what comes back rather than keying it in from scratch. Per-description GeoJSON or the PDF plot sheet attaches to the file.
Document pipelines
Valuation, assessment, and records systems process documents in a steady flow. Each recorded document becomes a project document; the structured calls and geometry come back for matching against your parcel identifiers. Where document filenames or text carry a parcel id or instrument number, downstream matching stays automatic.
GIS and the parcel fabric
Consolidated project GeoJSON (WGS84) drops onto a parcel fabric directly; DXF and Shapefile serve CAD and desktop GIS. The standing enterprise pattern: Bulk Processing Services clears the backlog, BoundaryLogic Trace is where the team works with results, and the API keeps the fabric current as new documents record. If your project starts with a backlog, read Bulk Processing or the API? first.
What an evaluation needs
- Inputs: PDF, JPEG, PNG, TIFF, or raw description text. See The document processing workflow.
- Outputs: GeoJSON (WGS84), DXF, Shapefile, CSV, PDF plot sheet. See What the API returns.
- Scope: closed tracts and centerline easements, with the exclusions in Limitations. Check them against a sample of your own documents before committing the spec.
Ready to scope it: send the spec questions through the sales form at boundarylogic.com/talk-to-sales/, or book an API consultation at boundarylogic.com/demo/.