FormWiseFormWise Changelog
← Changelog

Your customers can now call your Agents, Flows, and Teams from their own software

The customers who want your Agents and Flows inside their own systems no longer have to go through a chat window. On Pro and Agency, you can sell API access the same way you already sell MCP access, and each Portal becomes an API your subscribers can build on.

Sell API access as part of the Plans you offer your customers. Open one of your Portal's Plans or Policies and turn on "Include API access". A subscriber on that Plan reaches exactly what the Plan includes, a member of a Group funded by that Policy reaches everything the Group is assigned, and every run spends their credits, not yours. MCP and API are separate switches, so a Plan can include either, both, or neither.

Every Portal gets its own API and its own reference. A Portal with API access answers at its own address, on your custom domain if you have one, and publishes an API reference under your brand with no mention of us. Your subscribers can list the Agents and Flows their Plan includes, send a message to an Agent, run a Flow with its inputs, stream the reply, read back any run they started, and hand off long runs to a callback URL instead of waiting.

One key, minted where it is needed. A subscriber creates a key in their account settings, and the same key works for the API and for apps that take a key instead of signing in. When a vendor is integrating on a customer's behalf, you can mint and revoke keys for that person yourself from their record on the Users page, from the org API, or through the FormWise MCP server. A key that would only ever be refused is never issued.

Set a ceiling per Plan. Each Plan that includes API access can carry its own requests-per-minute limit, so a starter tier and an enterprise tier get the room you decide. Leave it empty and the default applies.

Portals stop asking a question Plans already answer. The per-Portal "Allow MCP" and "Allow API" switches are gone. A Portal offers MCP or API exactly when a Plan it sells or a Policy funding a Group it admits includes that access. The Portal's Connections card shows the addresses and names the Plans and Policies that open each one.

Improvements
  • Users: A person's record now opens with their Access Map, followed by their API keys, so the whole picture is on one page.
  • Account settings: Your subscribers' settings are grouped into Account, Connect an app, API, and API keys. When a Plan is required, the page names the Plans that include it.
  • Pricing: A Plan that includes API access says so on the pricing screen, as "API access from your own software".
  • Plans: The MCP and API options always show on Plans and Policies. On a workspace without the Developer API they appear locked with an upgrade link instead of disappearing.
  • Automations (Beta): Schedules an Agent creates get a daily run cap of 24 unless a member raises it, and an Agent can create only so many schedules per day.
  • Automations (Beta): Cron expressions that fire too close together anywhere in their cycle are refused up front, not discovered later.
  • Automations: The webhook settings now explain when to send the secret as a header rather than in the URL.
  • Settings: The Integrations page is now called API keys and holds only the provider keys FormWise runs on. Optional services live on Connectors.
Fixes
  • Automations (Beta): Two runs of one automation failing at the same moment are both counted, so the automatic pause after repeated failures lands exactly when it should.
  • Automations (Beta): A one-time schedule whose time has expired is refused on resume instead of firing late.
  • Automations (Beta): A run's credit balance is rechecked partway through long workflows, not only after a pause.
  • Plans: Turning on MCP access for a Plan is now refused on workspaces without the Developer API, where it was previously accepted and silently did nothing.
New integrations43