> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/images.md).

# Rmfg Images

Block that downloads RMFG's rendered pictures. The API's image links need the account's credentials, so a bare URL is useless downstream; this block fetches the PNG and hands it on as a platform media file.

## RMFG Get Image

### What it is

Downloads RMFG's rendered picture of a design or part, with holes and bends labelled

### How it works

Requests `/v1/designs/{id}/image`, `/v1/designs/{id}/parts/{part_id}/image`, or `/v1/dfm/{id}/parts/{part_id}/image` with the chosen `view` (iso, top, bottom, front, back, left, right, or flat for a sheet part's flat pattern) and optional `width` (0 uses RMFG's default, up to 4096). Setting `dfm_id` without `part_id` is rejected before any request, since a DFM picture is always of one part. Part pictures label every hole and bend by ID, which is how an agent decides which `hole_id` to tap or countersink; DFM part pictures additionally mark the configured operations.

The block always asks for PNG and checks the bytes it gets back: anything else (the SVG the API can also render, or an HTML error page) is refused with `RMFG returned <type> instead of a PNG` rather than stored as a media file. Unknown IDs and other HTTP errors are reported as `RMFG <code>: <message>`. The PNG goes through the platform's media pipeline, so the output is a workspace file in CoPilot and a data URI in graphs.

### Inputs

| Input      | Description                                                                                               | Type                                                                           | Required |
| ---------- | --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | -------- |
| design\_id | Design ID from Analyze Design                                                                             | str                                                                            | Yes      |
| part\_id   | Draw only this part, with every hole and bend labelled by ID. Empty draws the whole design.               | str                                                                            | No       |
| dfm\_id    | With part\_id, draw the part as configured in this DFM report, taps, studs, nuts and countersinks marked. | str                                                                            | No       |
| view       | Camera angle; flat shows a sheet part's flat pattern.                                                     | "iso" \| "top" \| "bottom" \| "front" \| "back" \| "left" \| "right" \| "flat" | No       |
| width      | Image width in pixels; 0 uses RMFG's default.                                                             | int                                                                            | No       |

### Outputs

| Output | Description                         | Type       |
| ------ | ----------------------------------- | ---------- |
| error  | Error message if the request failed | str        |
| image  | The rendered PNG                    | str (file) |

### Possible use case

**Hole Selection**: Show the customer the flat view of a part with labelled holes before asking which to tap.

**Quote Attachment**: Attach an iso render of the whole design to the quote email.

**Configuration Proof**: Send the DFM part picture so the customer can see where the hardware will go.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agpt.co/docs/integrations/block-integrations/images.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.