---
title: "Derating analysis against NASA GSFC or IPC-9592 (synchronous, unmetered)"
method: POST
path: "/v1/designs/derating"
tags: ["Solve"]
---

# Derating analysis against NASA GSFC or IPC-9592 (synchronous, unmetered)

`POST /v1/designs/derating`

## Request

- Base URL: `https://electronics-architect.com`
- URL: `https://electronics-architect.com/v1/designs/derating`
- Auth: HTTP bearer

Scope: `solve`. One nominal solve, then every rated part is held to the chosen standard's derating table — the same evaluator the editor's Derating panel runs. `standard` is required: `NASA_GSFC` (EEE-INST-002 Table 4 by part family: ICs at 0.75 × Tmax, never above 110 °C or Tmax − 40; diodes at 0.80 × Tmax, never above 125 °C or Tmax − 40) or `IPC_9592` (115 °C cap). Each graded component carries its checks (parameter, actual, rated, derated `limit`, `stressPct` = actual over RATED, `status`, and `basis`: the EEE-INST-002 section the rule comes from, or null for a check the standard does not cover and for every IPC check), a worst-case status and mitigation text; `summary` counts them; `thresholds` is the table used; `solve.converged` is the solver's verdict on the solve underneath — read it. Status: GREEN inside the limit, ORANGE within the last 20 % under it, RED over it. A rating the design leaves at 0 or blank is UNSTATED, not a 0 limit: that parameter is skipped and listed in the component's `unrated`, the same rule the solver applies. Sources, loads and the BMS have no abs-max ratings and are not graded. Unmetered on Pro and Team; one of the month's solves on Free.

## Request body

- object
  - `design` Design, required (unresolved $ref)
  - `standard` 'NASA_GSFC' | 'IPC_9592', required: The derating standard to grade against.
  - `options` object
    - `ambientTemperature` number: Ambient in °C for the thermal estimates. Defaults to the design's own setting, else 25.

## Response `200`

The derating report and request metadata.

- DeratingResponse
  - `result` object
    - `standard` object
      - `id` string
      - `apiId` 'NASA_GSFC' | 'IPC_9592'
      - `label` string
      - `reference` string
    - `ambientTemperature` number
    - `summary` object
      - `evaluated` integer
      - `compliant` integer
      - `warning` integer
      - `overstressed` integer
      - `worstStatus` 'GREEN' | 'ORANGE' | 'RED'
    - `components` DeratingComponent[]
      - `id` string
      - `name` string
      - `type` string
      - `sheet` string
      - `worstStatus` 'GREEN' | 'ORANGE' | 'RED'
      - `worstStressPct` number
      - `checks` DeratingCheck[]
        - `parameterName` string
        - `actual` number
        - `rated` number: The abs-max rating from the part's properties.
        - `limit` number: rated × the standard's factor, or lower where the rule sets its own ceiling: a junction temperature (NASA: ICs never above 110 °C or Tmax − 40, diodes 125 °C or Tmax − 40; IPC: 115 °C) or, at NASA, a resistor's √(P_derated × R).
        - `unit` string
        - `stressPct` number: actual over RATED, in percent; a thermal check grades the rise over ambient against the rated rise.
        - `status` 'GREEN' | 'ORANGE' | 'RED'
        - `basis` string, nullable: Where the rule comes from: a citation such as `EEE-INST-002 M3 Table 4` (M3 microcircuits, S1 diodes, R2 resistors, C1 capacitors, F3 fuses) on a NASA check, or null — a check the standard does not cover, whose factor is the tool's own (capacitor ripple, inductor current, transformer and inverter VA, diode and rectifier power, battery, motor), and every IPC check, because that column has not been checked against IPC-9592.
      - `unrated` string[]: Parameters whose rating the design leaves unstated (0 or blank). They are not in checks, are not graded and do not count toward the status; the rating must be entered before they can be.
      - `recommendations` string: Mitigation text for every failing check, or a one-line pass, followed by the unrated parameters when there are any.
    - `thresholds` object: The factor table used: the fraction of the rating allowed per parameter class. `*_tj_cap` and `*_temp_cap` keys are temperature ceilings in °C, `*_tj_margin` keys mean "never above Tmax − n °C", `fuse_temp_derate` is the fraction lost per °C above 25 °C, and null means the standard sets no such limit.
    - `statusLegend` object
    - `solve` object
      - `release` string
      - `simulatedAt` string, date-time
      - `elapsedMs` number
      - `converged` boolean
      - `sheets` object[]
        - `sheetIndex` integer
        - `sheetName` string
        - `converged` boolean
        - `error` string
  - `meta` object
    - `attribution` Attribution: Who solved it and how to check (AR4.1). The same block on every solve response (`meta.attribution`), every export, and — as one line — every PDF, PNG and CSV the editor or the API produces.
      - `solver` string
      - `release` string: The build that solved the design — the release tag on production (e.g. "0.9.60"), "main-<sha>" on staging, "dev" elsewhere.
      - `resultContract` string: The result-shape contract version (`result.version`).
      - `designHash` string: Sixteen hex characters of SHA-256 over the canonical design: parts, properties, tolerances, selected parts and wiring. Layout, routing and solve options are excluded, so one design has one hash at every corner.
      - `generatedAt` string, date-time
      - `verifyUrl` string: /verify/{designHash}, with ?s=<token> when the design has a VIEW-ONLY public share link, so the page can re-solve it unaided. An `edit` or `clone` share link is deliberately omitted: that token also opens the design for writing, and an export is a document you hand to someone else.
      - `statement` string: The one printed line: "Solved by Electronics Architect solver vX · design <hash> · <date> · verify: <url>".
    - `schemaVersion` integer
    - `standard` string
    - `corner` string
    - `ambientTemperature` number
    - `nodes` integer
    - `sheets` integer
    - `elapsedMs` number
    - `metered` boolean

## Other responses

- `400`: VALIDATION_FAILED with the failing schema paths, or INVALID_REQUEST — a missing or unknown `standard`, a corner other than nom, a bad ambient.
- `401`: No key, a browser token instead of a key, an unknown key, or a revoked key (code KEY_REVOKED).
- `403`: The key lacks a required scope (INSUFFICIENT_SCOPE), or the call needs a plan the account does not have (PLAN_REQUIRED): on the Free plan, compare, exports, Monte Carlo jobs, AI synthesis, a design with more than one sheet, or a save, share or key past the Free limits; or a team key whose team is no longer paid for.
- `413`: PAYLOAD_TOO_LARGE — a payload cap was exceeded.
- `429`: RATE_LIMITED: the key's per-minute allowance is used up (or, before any key is recognised, too many requests from one address presented an unknown or revoked key). On the routes that solve inside the request (solve, verify, derating, compare, exports, ai/review, ai/synthesize) it can also be SOLVE_IN_PROGRESS: this account already has 3 calls of that kind running on the server that took the request (solves, AI reviews and syntheses are each counted separately). `Retry-After` is set either way; for SOLVE_IN_PROGRESS it is 2 s for solves and 30 s for AI reviews and syntheses.
- `500`: SOLVE_FAILED — the solver refused the circuit.

---

[API](https://skmtc.dev/electronics-architect/apis/electronics-architect-api.md) · [All operations](https://skmtc.dev/electronics-architect/apis/electronics-architect-api/llms.txt) · [OpenAPI document](https://skmtc.dev/electronics-architect/apis/electronics-architect-api/revisions/98066184ba67?raw)