API Integration
The separate REST contract is pending production verification. The published OpenAPI document contains no callable operations. Review the hosted MCP interface and confirm the access and coverage your workflow needs.
Start with one operation and a representative site
Identify the information your application needs and the action it will support. A site analysis request, a status check and a design export are different operations; do not assume one successful request has completed every stage or returned every layer.
- Review the developer documentation, published OpenAPI reference and authentication guide.
- Confirm the available operation, access method, request limits and expected response before implementing against it.
- Test a representative request and inspect its completion status, source coverage, missing fields and errors.
- Handle asynchronous completion and failed or partial results before scaling the workflow.
- Check the format, coordinates, units and access conditions of any returned export.
Usage and integration choices
A published plan allowance does not establish a verified production REST endpoint. Review current plans and usage for account access and any operation-specific limits. Public MCP checks and account-linked API operations are different access paths.
Atlasly does not currently publish an official JavaScript, TypeScript, or Python SDK. Obtain a confirmed REST deployment contract before generating a client or sending credentials. The hosted MCP interface is separate; inspect current tool discovery and verify the permissions, source coverage and completion behaviour of the operation you need.
Keep evidence with the result
Carry source references, observation dates, boundary assumptions and incomplete checks into your application's review flow. The methodology and limits guide explains why a missing result must not be interpreted as an absence of constraints.