Call the same geoprocessing engine the browser products use, from your own systems, with an enterprise key.
Send an `Idempotency-Key` header with any request you might retry. A repeat of the same key returns the first result instead of running the tool — and counting the run — twice.
curl -X POST "$BASE/buffer" \
-H "X-Api-Key: $KEY" -H "X-Api-Secret: $SECRET" \
-H "Idempotency-Key: order-1234-attempt-1" \
-F "[email protected]" -F "distance_m=100"Every successful response carries a `usage` object: the run and request ids, the bytes in and out, and the enterprise's allowance for the tool — its tier, the runs per window, and when the window resets. GET /usage returns the runs made in the current window.
"usage": {
"channel": "api",
"requestId": "req_…",
"runId": "6710…",
"inputBytes": 5000,
"outputBytes": 12345,
"totalBytes": 17345,
"inputFileCount": 1,
"outputFileCount": 1,
"allowance": {
"tier": "pro",
"runs": 15,
"windowDays": 1,
"resetAt": "2026-08-18T00:00:00.000Z"
}
}Access is set up with your enterprise: an administrator creates an API application in the Console and issues its key pair. Runs belong to the enterprise and count against its tier's allowance.
Read the reference