Documentation
Overview of the Sancosmic platform — how it works, error codes, compliance references, and product scope.
Send energy or agricultural data to the API. The platform accepts a range of formats and asset types across both domains.
Data quality is checked first. If readings pass, the relevant engine analyses your system and produces validated output.
Results include validated metrics, plain-English recommendations, and stable module codes suitable for regulatory use.
The free tier runs the same engines as paid products. Output detail and request limits differ by tier.
| Tier | Runs / month | Output |
|---|---|---|
| Free | 5 | Top-level physics result — key metrics and recommendations, obfuscated at field level |
| Paid product | 10,000 | Full output — all validated fields for the commissioned product |
| Enterprise | 10,000 | Full output + advanced diagnostics, baseline tracking, and dedicated support |
For integration support or API access queries, contact physics@sancosmic.com.
These codes are returned when submitted data violates a physical or biological constraint that prevents a valid analysis from running. Each one is a diagnostic signal — it identifies what to check, not just that something went wrong.
The submitted data implies a system output that exceeds what is physically possible — more energy out than in. Common causes: unmetered energy sources (solar, battery discharge, grid import not captured), miscalibrated sensors or CT clamps, or swapped input/output readings.
Action: Audit all energy input sources, verify all sources are metered, and check sensor calibration before resubmitting.
Load changed between readings by more than the physical ramp rate for the declared equipment type. This indicates an unscheduled large switching event, a metering timestamp error, or data packet loss in the telemetry pipeline — not a gradual operational shift.
Action: Check for unscheduled switching events, verify metering timestamps are correct, and confirm your equipment ramp rate matches the declared asset type.
Submitted readings show a significant data imbalance — inputs and outputs cannot be reconciled. This reliably indicates a metering gap, sub-metering misconfiguration, or a data pipeline error. Analysis does not run until corrected.
Action: Verify your metering setup, check for unaccounted sources, and resubmit with corrected data. This error cannot be suppressed.
The submitted conditions fall outside the operating envelope for the declared system type — for example, thermal conditions incompatible with the stated equipment, or biological parameters outside viable range for the declared crop. The analysis cannot produce a valid result for the submitted state.
Action: Check that the declared system type matches the submitted conditions, and verify temperature, nutrient, or operational parameters are within expected bounds.
All paid outputs carry stable module codes — fixed identifiers linking each result to the analysis method that produced it. These are suitable for citation in audit reports, grant applications, and ESG disclosures.
| Framework | What Sancosmic supports |
|---|---|
| ESOS (Phase 3+) | Outputs include stable module codes suitable for citation in qualified energy audit reports and Lead Assessor sign-off. |
| SECR | Consumption and carbon reduction figures are derived from physics analysis, not benchmark averages. |
| ISO 50001 | Structured energy review outputs with traceable methodology — compatible with management system evidence requirements. |
| Innovate UK / ARIA | Suitable for grant applications that require a clear scientific basis for energy or agricultural technology claims. |
| TCFD / GRI 302 | Scope 1 and 2 emissions reduction figures backed by energy balance analysis rather than modelled estimates. |
| SFI (Agriculture) | Soil carbon outputs include sequestration figures citable for SOAM2 standard and carbon credit documentation. |
For enterprise assessments and compliance mapping, contact physics@sancosmic.com.
Create a free account and run your first assessment — no credit card required. For integration support, contact us directly.