API reference
The API pages are generated from the public Python package and its typed models. They list signatures, parameter types, and return values. Contract behavior is documented in Reference; this section is the callable surface.
If you are new, read Getting started and Concepts first. The API is not a substitute for the model and privacy boundaries.
Core and artifacts
Inputs, data, and integrations
brushline.integrations.femicbrushline.integrations.freshforgebrushline.integrations.cataloguebrushline.integrations.fetchbrushline.integrations.capabilities- Model builder API
brushline.integrations.lidarbrushline.integrations.terrainbrushline.integrations.canopybrushline.instance_templatebrushline.state_initbrushline.integrations.lidar_coveragebrushline.integrations.lidar_benchmark
Vegetation and evidence
Optimization and strategic planning
brushline.optimization.formulationbrushline.optimization.evaluatorbrushline.optimization.operatorsbrushline.optimization.adapterbrushline.optimization.paretobrushline.optimization.validationbrushline.optimization.budgetbrushline.optimization.telemetrybrushline.strategic.dynamic_program- Stateful strategic MILP API
- Stateful heuristic API
- Stateful decomposition API
- Stateful coordination API
brushline.strategic.portfoliobrushline.strategic.monitoringbrushline.strategic.baubrushline.strategic.reportsbrushline.strategic.scenariobrushline.strategic.validation- Static plan API
- Two-stage recourse API
Tactical, operations, monitoring, and field
brushline.tactical.programbrushline.tactical.resourcesbrushline.tactical.accessbrushline.tactical.operationsbrushline.tactical.fhopsbrushline.tactical.timelinebrushline.tactical.validation- Shift scheduling API
- Operations API
brushline.monitoring.observationbrushline.monitoring.missionbrushline.monitoring.valuebrushline.monitoring.recalibrationbrushline.monitoring.replanbrushline.monitoring.validation- Field validation API
- Field comparison API