AI

AI design review: what the solved numbers mean, then what to change

Scope: ai. Decrements the monthly AI-analysis counter (Pro 25, Team 100; an account with its own AI key is not metered). At most 20 calls an hour per account through the API, across all its keys (429 RATE_LIMITED). At most 3 reviews run at once per account on the server that takes the request, the editor's AI reviews included; a 4th is 429 SOLVE_IN_PROGRESS with Retry-After: 30 and does not count against the hourly limit. Mode review — the plain-English read of the results first, then the recommended topology, derating and thermal changes, in one call. Send the design document: the review solves it (as given, at options.ambientTemperature °C, default 25) and works out every part's worst-case input (each battery at full charge, every tolerance corner). Every part a suggestion names is checked against the worst case where it would go; one rated below it is moved to rejectedSuggestions with its ratingCheck, and ratingBasis says what the check stood on. A solve result is accepted too, but carries no wiring, so it is checked at its one operating point only.

post/v1/ai/review

Request

  • Base URL: https://electronics-architect.com
  • URL: https://electronics-architect.com/v1/ai/review
  • Auth: HTTP bearer

Request body

designDesign required(unresolved $ref)

Response

Summary and suggestions, after the rating check.

summarystring
suggestionsobject[]
rejectedSuggestionsobject[]
ratingBasis'worst-case' | 'operating-point' | 'null' nullable
remainingunknown
limitunknown
modelstring
cachedboolean

Changes

No recorded changes to this operation across all 1 revision of this API.