AI app and site builders
Products like Lovable or v0
People describe a site and get it. MakeFont gives each generated project its own headline and text type, matched to what they described.
Back to MakeFont
Design partners
Give everything your users build a typeface of its own.
MakeFont lets AI agents design real, installable fonts. We are looking for a few platforms to build the integration with: AI app and site builders, design tools and coding agents.
Why type
AI makes everything look the same. Type is the quickest way out.
Generated sites and apps keep landing on the same few default fonts. A typeface of its own is what made the work of real designers recognisable, and it has been out of reach for anyone without a type designer.
- Your users' projects stop looking generated. Every site built on your platform can get letters nobody else has, drawn from the brief.
- A feature others do not have. Custom type used to be something only big brands could afford. On your platform it becomes one step.
- It happens where your users already are. The agent offers a font inside the flow they already use. Nobody leaves your product to search a font library.
Who it is for
Who we want to build this with.
Three kinds of products, one idea: when someone makes something with your tool, it can come with its own type.
Design tools
Tools like Figma
Today type is picked from a menu. An integration could make a font from the brief or the moodboard, right on the canvas.
Coding agents
Agents like Claude Code, Codex or Cursor
They build front ends every day. With the MakeFont skill or MCP server, the agent can offer a custom font when a project deserves one.
Names are examples of the kind of product we mean. None of them is a MakeFont partner today.
Integration
Three ways in. Pick the one that fits your product.
All three are in development. Design partners get them first and help decide what they look like.
- Your userdescribes a project: "a landing page for my bakery"
- Your productyour agent or backend decides the project deserves its own type
- MakeFontreceives the brief, and a reference image if you like, and designs the fontAPIMCPSkill
- Font filesTTF and WOFF2, plus an editable source
- Your user's projectheadlines and text in a typeface nobody else has
API
Your backend sends a brief or a reference image and gets back an installable font: TTF and WOFF2 for the web, plus an editable source.
For builders that run their own generation pipeline.
MCP server
Your agent calls MakeFont as a tool, in the same session in which it builds the page, and sets the result in place.
For platforms and agents that speak MCP.
Agent skill
One line to install. From then on the agent notices when a project deserves its own type and offers to make it.
For coding agents that load skills.
Illustration
Build a landing page for my bakery, Crumb & Co. Warm, a bit old-fashioned, nothing corporate.
Here is your page. I also made Crumb Display, a typeface just for your bakery, and set the headlines in it.
Crumb & Co.
Bread worth waking up for.
Pilot
How a pilot runs.
Small, concrete and with real users. You decide at the end whether it goes further.
- Intro callWhat you build, who your users are and where type would matter for them.
- Use case and success criteriaWe pick one flow in your product and agree what a good result looks like.
- Pilot with real usersMakeFont fonts run in that flow for a small group. We shape the interface around your product as we go.
- DecisionTogether we decide whether and how to roll it out to all your users, including terms and licensing.
For your teams
The questions your teams will ask.
Straight answers, including the ones that are still open. Forward this page to whoever needs to say yes.
Product
What do our users get?
A font made for their project, offered inside the flow they already use, without leaving your product.
Engineering and IT
What do we build, and what data leaves our platform?
One integration: an API call, an MCP server or a skill. MakeFont receives the brief and, if you choose, a reference image. The integration is planned to work without personal data about your users. Hosting region, security requirements and data processing terms are agreed before a pilot starts.
Leadership and procurement
What does it cost, and who owns the fonts?
There are no prices yet; the terms of a pilot are agreed with each partner. Licensing for generated fonts is being defined with our first partners and will be settled before a public launch.
The deal
What you get. What we ask.
You get
- Access to the API, MCP server and skill before they are public.
- A say in the interface: formats, style controls, speed, and how licensing works for your users.
- Fonts for a real use case of yours during the pilot.
- A direct line to the people building MakeFont.
We ask
- A real use case in your product, with real users.
- Honest feedback, early and often.
- One person on your side who can try things quickly.
Where we are today: early. Two trial fonts exist, one weight each, and one of them runs on our homepage. API, MCP server and skill are in development, and there are no public prices yet.
Questions
Questions partners ask.
Is there a public MakeFont API yet?
No. The API, the MCP server and the agent skill are in development. Design partners get access first.
What does a font come as?
Our trial fonts come as TTF and WOFF2, plus an editable UFO source. We plan the same formats for the API.
Who owns the fonts?
We are defining licensing now, together with our first partners. It has to be clear for your users before a public launch.
What does it cost?
There are no prices yet. We agree the terms of a pilot with each design partner.
Which tools will it work with?
Anything that can call an API or an MCP server, plus agents that load skills, such as Claude Code, Codex and Cursor.
How do we start?
Use the form below or write to contact@makefont.ai. Tell us what you build and where type would matter for your users.
Design partners
Build it with us.
We start with a small number of platforms. Tell us what you build.
Or write to contact@makefont.ai