Solutions

Design as an API call

You need an image generated per record, per user or per event, and building a rendering pipeline is not the product you are working on. Graphtr gives you a template library, a renderer and an API in front of both, plus an MCP server when the caller is an agent rather than your backend.

The problem

What usually goes wrong

If none of these are familiar, this page is probably not for you.

Generating one image per record means owning a rendering pipeline.

Headless browsers for screenshots are slow and break quietly.

The design has to look designed, and you are not a designer.

The answer

What Graphtr does about it

A renderer you do not maintain

POST a template id and the copy, get image bytes. No browser, no font provisioning, no queue.

Templates that already look right

218 designs made by hand. You choose one programmatically and fill it, rather than composing a layout in code.

MCP when the caller is an agent

Relay exposes the same library over Model Context Protocol, so an assistant can design without you writing an integration.

Products

What you would actually use

All products

Render

One POST, one finished design.

Learn more

Relay

Your agent, holding the pen.

Learn more

Charts

A table of numbers, in a chart that looks designed.

Learn more

FAQ

Questions

What do I get back?

The file. SVG or PNG bytes in the response body, not a job id to poll and not a URL that expires.

Is there a spec?

An OpenAPI document at /api/v1/openapi.json, and an llms.txt for agents that discover you by reading rather than by clicking.

How are we rate limited?

By rendered design per month, with the remaining allowance in the response headers so a client never has to guess.

Your ideas deserve better than a blank page

Open the editor and see for yourself. Nothing to install, nothing to cancel, and your first design is about five minutes away.

Start designing now