AGENT BUILDERS
Add place-aware tools without building a GIS stack first.
A proposed API and MCP surface would let agent teams request location context through predictable tools while retaining provenance and human control.
Illustrative workflow only. Availability, source coverage, integrations, and operating limits will be defined with pilot participants.
01 / REVIEW FLOW
A human-readable path from input to decision support.
- 01Define the decision boundary
- 02Select only necessary fields
- 03Expose uncertainty to the agent
- 04Require approval before consequential action
QUESTIONS TO KEEP VISIBLE
Can the agent explain the source?
What happens when a place is ambiguous?
Which action always requires a person?
02 / RESPONSIBLE USE
Context supports judgment. It does not authorize action.
Customers would be responsible for ensuring that they control or are authorized to evaluate the locations and systems involved, for reviewing applicable source licenses, and for placing qualified people in the approval path before consequential decisions.
EARLY ACCESS
Discuss an Arcwise agent builders pilot.
Show us the decision, the geography, and the evidence a person needs to review.