Read the tool instructions in Markdown and the request/response schemas in OpenAPI. These public calculation APIs run the same models as the web and offline calculators. No account, API key or Turnstile is required.

• Emergency Lighting Battery Calculator — Full tool instructions (Markdown)
• OpenAPI contract
• Agent site index

Emergency Lighting Battery Calculator

POST /api/tools/v1/emergency-lighting-battery
Content-Type: application/json

Estimate a constant emergency load on one battery or bank. Results are conditional energy budgets, not a battery discharge curve, illuminance calculation, equipment recommendation or compliance approval. Obtain the operating assumptions from the user or equipment data; do not silently use the editable web examples.

estimate-runtime · size-battery

Estimate battery runtime

Use operation=estimate-runtime with batteryCapacity.value and its explicit Ah, mAh or Wh unit. batteryVoltageV is the nominal complete-bank voltage. capacity.basis=rated requires availablePercent for the intended load, temperature, cutoff and battery condition; capacity.basis=usable omits that factor. The complete example yields 96 Wh usable energy and about 129.6 minutes.

{
  "operation": "estimate-runtime",
  "batteryVoltageV": 12,
  "batteryCapacity": {
    "value": 10,
    "unit": "Ah"
  },
  "capacity": {
    "basis": "rated",
    "availablePercent": 80
  },
  "power": {
    "basis": "load",
    "load": {
      "kind": "total",
      "powerW": 40
    },
    "efficiencyPercent": 90,
    "overheadW": 0
  },
  "targetMinutes": 90,
  "extraCapacityPercent": 20
}

Open links.share to restore the input in the web calculator, then compare the assumptions with manufacturer data. The same available fraction must be rechecked if the load, battery, temperature or cutoff changes. Check full-duration operation and required light levels separately. Copy, CSV, print and offline HTML contain the same calculation; the offline file computes locally and its download endpoint is not a calculation API.

Request limits and errors

Send uncompressed application/json with strict types and no query parameters. Indoor lighting bodies are limited to 16 KiB; driver-match bodies to 16 KiB; battery bodies to 16 KiB; voltage bodies to 16 KiB; resistor bodies to 16 KiB; DMX bodies to 1024 KiB and 1000 fixtures; pixel bodies to 64 KiB, 64 run rows, 128 outputs and 2000000 channels. DALI bodies are limited to 64 KiB, 24 rows and 512 devices. Illuminance bodies are limited to 16 KiB and 400 planned points. Photometry bodies are limited to 1024 KiB with up to 4 files and 16 by 721 query directions per file. Lighting-cost bodies are limited to 64 KiB with up to 20 groups in each scenario. Body reading expires after 5 seconds. Complete success JSON is bounded to 4 MiB. GET/HEAD return 405; OPTIONS returns 204. Source responses are no-store. Anonymous browser CORS permits POST/OPTIONS and Content-Type with credentials omitted.

Tool POST requests and ordinary page requests share 120 requests per 60 seconds per IP/Cloudflare location; mitigation lasts 60 seconds. Heavy tool use can temporarily block pages from the same source. This is not an independent or globally exact API quota. Inquiry/search use their existing separate rule. Tool POST requests do not inherit the company-page or verified-bot exemption.

Cloudflare can return 403/429/5xx before the application, sometimes as HTML without CORS or Retry-After. Check HTTP status and Content-Type before parsing JSON. A browser may see only a network error. Do not present an error or an older result as a successful new calculation.