Availability: Arranged through sales
Two ways to process legal descriptions at scale. The honest split is not volume, it is who does the work and what already exists on your side.
Choose Bulk Processing Services when
- The need is a backlog: a large set processed as an initiative rather than a flow.
- The use case still needs validating, and a pilot on your own documents should come before anyone writes integration code.
- Development resources or infrastructure do not exist on your side: data lives in spreadsheets and scanned files, and there is no system ready to consume API output.
- The deliverable is more than a file format: custom output structures, a review interface, integrations, or a complete system built to requirement.
Choose the API when
- Documents arrive continuously and processing belongs inside your own software.
- The use case is defined and proven, and your team can build against a REST interface.
- Standard outputs fit: GeoJSON (WGS84), DXF, Shapefile, CSV, the PDF plot sheet.
- You want direct control of the workflow, project by project, document by document.
They also work in sequence
The standing enterprise pattern: BPS clears the backlog, BoundaryLogic Trace is where the team works with the results, and the API keeps your systems fed as new documents record. Starting with BPS does not commit you to it; many engagements exist to prove the case the API then serves.
Still unsure after this page: that is what discovery is for. Working with the solutions team covers what to bring.