Integration

Connect FormDesigner to DiceBear

When something happens in FormDesigner, your agent does the next thing in DiceBear. Describe it and it is built, tested on every scenario and kept running.

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want FormDesigner and DiceBear to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

FormDesigner collects the sign-ups, surveys and quiz entries; DiceBear turns any seed value into an avatar image in the style you pick. Joined together, each new submission in FormDesigner can produce a matching avatar from a name or email, and the resulting image link can be written back onto the entry itself.

Example flows

What FormDesigner can start in DiceBear

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with FormDesigner and DiceBear

Triggers and actions 1 trigger · 12 actions

Each app on its own

Reviews

What our customers say

More from FormDesigner

More into DiceBear

Questions

FormDesigner and DiceBear, answered

Can the avatar be saved back onto the FormDesigner submission?

Yes. After DiceBear generates the avatar, the Update form entry action writes the image link onto the entry the submission created, so the picture sits alongside the answers.

How do I choose which DiceBear style is used?

You can name a style directly in the Generate avatar action, or run List avatar styles first and pick from what DiceBear currently offers. Either way the seed you pass, such as an email from the FormDesigner entry, decides the exact image.

What can start an automation from FormDesigner?

Any of FormDesigner's 1 trigger in the catalog, including New Submission. Describe the moment in plain language and your agent picks the right one.

What can your agent do in DiceBear when something happens in FormDesigner?

Any of DiceBear's 2 actions, including Generate avatar and List avatar styles. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from DiceBear to FormDesigner?

DiceBear has no triggers in the catalog today, so automations start in FormDesigner. If you need the other direction, ask: your agent reads DiceBear's API documentation and adds it.

Do I have to build a connector for FormDesigner or DiceBear?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.