Everything you can do by clicking in Flowy has a programmatic route too. This page is a signpost to the three of them. Each has its own full reference for the details.
API keys
An API key is a scoped secret for one workspace, meant for servers and scripts. Create one under Settings → API keys, choose All, Read Only, or a Restricted set of permissions, and optionally cap its daily spend and rate limit. Runs started with a key bill that workspace. See API keys to create one, and Authentication and Permissions for sending it and what each scope unlocks.
The MCP server
Flowy ships a hosted MCP server at mcp.tryflowy.ai/mcp that connects any MCP-capable agent (Claude, Claude Code, Cursor, ChatGPT, and others) straight to your account. There’s no key to copy: you sign in and consent once in the browser, and the connection is bound to your account, billing your personal wallet by default or a workspace you choose. See MCP server for the full tool list and how to connect your agent.
The CLI
@tryflowy/cli (the flowy command) signs you in from the terminal and can wire the hosted MCP into your agent for you. No manual config editing. It also generates media, checks your balance, and manages brand kits directly from the command line. See CLI to install it.
Building your own integration
If you’re building a product that connects to other people’s Flowy accounts rather than only your own, register an OAuth app instead of using a personal API key. It requests only the scopes it needs and users can revoke it anytime. See OAuth apps to register one, and Connected apps for how a user manages and revokes access to apps they’ve authorized.
Not sure which one fits? A key is for your own scripts against your own workspace; the CLI is the fastest way to try Flowy from your terminal or wire up an AI agent; an OAuth app is for a product other people will connect their own Flowy account to.
