---
title: "Re-solve a design and check the fingerprint printed on an export"
method: POST
path: "/v1/designs/verify"
tags: ["Solve"]
---

# Re-solve a design and check the fingerprint printed on an export

`POST /v1/designs/verify`

## Request

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

Scope: `read`. Unmetered on Pro and Team; one of the month's solves on Free. This runs a full solve at `options.corner` under the `read` scope, within the same payload caps as `/v1/designs/solve`: a key limited to `read` can still spend solver time here. Give the design and, optionally, the 16-character `hash` from a report's attribution line; the answer is the hash this build computes, `matches`, the current attribution and the summary numbers to hold against the page. The keyless twin behind the verify URL is the page at /verify/{hash}.

## Request body

- object
  - `design` Design, required (unresolved $ref)
  - `hash` string: The design fingerprint printed on the export. Optional: without it the answer is the fingerprint alone.
  - `options` object
    - `corner` 'nom' | 'min' | 'max' | 'worst': Which tolerance corner to solve. `min`/`max` push every toleranced value to its extreme. `worst` moves each one the way that raises the draw and the heat (loads up, efficiencies down, a switcher's output up, an LDO's down) and holds the input at nominal; each sheet's `worstCase.held` lists what it held and why.
    - `ambientTemperature` number: Ambient in °C for the thermal estimates. Defaults to the design's own setting, else 25.

## Response `200`

The verification.

- VerifyResponse
  - `designHash` string
  - `expected` string, nullable
  - `matches` boolean, nullable: null when no `hash` was given.
  - `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>".
  - `summary` object
    - `converged` boolean
    - `totalSourcePower` number, nullable
    - `totalLoadPower` number, nullable
    - `totalDissipation` number, nullable
    - `efficiency` number, nullable
    - `warnings` object
  - `meta` object

## Other responses

- `400`: VALIDATION_FAILED or a malformed hash.
- `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.
- `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.

---

[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)