DEVELOPERS
A small tool surface for place-aware systems.
The proposed Arcwise interface is intended to accept clear location inputs, return typed outcomes, and keep evidence metadata close enough for an agent to explain.
All endpoints, schemas, hostnames, SDKs, API keys, and MCP integrations shown here are design proposals. They do not work yet.
This explorer is illustrative. It does not send a request or use a production API.
curl -X POST https://api.arcwisesi.cloud/v1/ask \
-H "Authorization: Bearer $ARCWISE_KEY" \
-H "Content-Type: application/json" \
-d '{ "question": "What constraints should move this site out of the shortlist?", "mode": "illustrative"}'Preview the sample to see a clearly labeled, non-live response shape.
Typed outcomes
Resolved, ambiguous, absent, unsupported, and retryable failures should not collapse into one empty response.
Selective context
Request only the fields the decision needs, reducing noise and making the evidence path easier to review.
Agent-ready access
A proposed REST API and MCP integration would expose the same place operations under consistent permissions.
EARLY ACCESS
Help define the developer interface.
Show us the decision, the geography, and the evidence a person needs to review.