---
title: "Design Tr Module From Intent"
method: POST
path: "/api/tr-module/design"
tags: ["tr-module"]
---

# Design Tr Module From Intent

`POST /api/tr-module/design`

## Request

- Base URL: `https://api.pcbgenerator.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.pcbgenerator.com/api/tr-module/design`
- Auth: none declared

Design both chains and the shared front end, then compute the budgets.

The sibling of the route above, not a widening of it. `POST /api/tr-module`
is the pure-engine path and needs an isolation figure and a limiter the
caller has already chosen; a caller who only knows "9.4 GHz, 20 W" has
neither, which is exactly the design intent this route serves.

Selection and orchestration reuse `assemble_tr_module`, the SAME function the
`design_tr_module` agent tool calls, so the assistant and any UI can never
disagree about which part fills a slot.

Rate-limited harder than either sibling (15/min vs 60): this one runs the
full transmit convergence loop, the receive assembler and the per-slot
scoring agents against the component database.

## Request body

- object

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/pcbgenerator/apis/pcb-stackup-generator-api.md) · [All operations](https://skmtc.dev/pcbgenerator/apis/pcb-stackup-generator-api/llms.txt) · [OpenAPI document](https://skmtc.dev/pcbgenerator/apis/pcb-stackup-generator-api/revisions/b6084b3ace32?raw)