--- title: "Build with AI agents" description: "What Fluveo publishes for AI coding agents, and what a person must do." url: https://docs.fluveo.com/agents/ --- > Index of every page: https://docs.fluveo.com/llms.txt. Integrating Fluveo? Read https://docs.fluveo.com/agents/integrate.md first. # Build with AI agents What Fluveo publishes for AI coding agents, and what a person must do. An AI coding agent can integrate Fluveo by reading these docs and nothing else. This page lists what we publish for agents, what a person has to do first, and the limits an agent meets. ## What a person does, and what the agent does A person does two things the agent cannot do: 1. Create the Fluveo account in the [Dashboard](https://dash.fluveo.com). Test mode works at once; activate the account in the Dashboard only to go live. 2. Create a test secret key (`sk_test_...`) in the Dashboard under **Settings > API keys**, with the **Create secret key** button and a name for the agent, and put it in an environment variable the agent's code reads, such as `FLUVEO_SECRET_KEY`. The Dashboard shows a new secret key only once. An agent that only reads can get a restricted key (`rk_test_...`) with **Read** on the resources it needs instead. For a checkout page with Fluveo's payment form, also copy the test publishable key (`pk_test_...`) from the same screen into `FLUVEO_PUBLISHABLE_KEY`: it is the only key a page may hold. The agent does the rest in test mode: it writes the integration, calls the API, creates the webhook endpoint, verifies signatures and runs the checks at the end of [the integration playbook](https://docs.fluveo.com/agents/integrate.md#verify-your-integration). > **For AI agents:** > > Never ask the person to paste a secret key into the chat or into source code. Ask them to set an environment variable and read it from there. > Never use a key that starts with `sk_live_`. Live mode is not open yet, and the API answers such a key with 403. ## What we publish for agents | Resource | Where | What it is for | | --- | --- | --- | | llms.txt | [/llms.txt](https://docs.fluveo.com/llms.txt) | The index: what Fluveo is, the hard rules, and one line per page. Start here. | | One file per task: the checkout | [/llms/custom-checkout.txt](https://docs.fluveo.com/llms/custom-checkout.txt) | Everything to build a first checkout page of your own with Fluveo's payment form, under 40 KB: the rules, the quickstart, the calls a checkout makes and the errors they throw, the test cards and the webhook signature check. | | One file per task: the payment form | [/llms/payment-element.txt](https://docs.fluveo.com/llms/payment-element.txt) | What changes the form after a first checkout, under 40 KB: the rules, the form's calls, events and options, and the errors they throw. | | Every page in one file | [/llms-full.txt](https://docs.fluveo.com/llms-full.txt) | All pages, each starting with its title and a `Source:` line. For agents with a long context. | | Markdown of any page | the page address plus `.md`, such as [/agents/integrate.md](https://docs.fluveo.com/agents/integrate.md) | The page as clean Markdown: every code tab labelled, and the notes written only for agents. | | Markdown in one language | `.curl.md`, `.node.md`, `.python.md` or `.php.md` in place of `.md`, such as `/agents/integrate.python.md` | The same Markdown with each code group using that language when present, otherwise cURL when present or its first tab. Much shorter on long pages. Each `.md` lists its copies at the top. | | OpenAPI | [/openapi.json](https://docs.fluveo.com/openapi.json) | Every operation Fluveo serves. If it is not in this file, it does not exist. | | API version | [/versions.json](https://docs.fluveo.com/versions.json) | The one API version Fluveo serves, `2026-05-27.dahlia`. | | Agent skill | [/skills/fluveo-custom-checkout/SKILL.md](https://docs.fluveo.com/skills/fluveo-custom-checkout/SKILL.md) | A skill file for coding agents that load skills: the rules, the steps and the checks of a custom checkout. See [Install the skill](https://docs.fluveo.com/agents.md#skill). | | MCP server | The Fluveo MCP server is not available in production yet. | For agents that connect to servers instead of fetching pages. See [Fluveo MCP](https://docs.fluveo.com/agents/mcp.md). | Every HTML page also links its Markdown copy with ``, so a tool that reads the HTML can find it. ## The "Use with AI" menu Next to the title of every page, the **Use with AI** menu has four entries: - **Copy for LLM** copies the page's Markdown with Fluveo's hard rules on top, ready to paste into any chat. - **View as Markdown** opens the `.md` copy. - **Open in ChatGPT** and **Open in Claude** start a chat that reads the page. ## Ready prompts [The ready prompts](https://docs.fluveo.com/agents/prompt.md) are two blocks of text a person pastes into their coding agent, each with the rules the agent must follow and the checks it must run before it says it is done: - "Build a custom checkout page for this app with Fluveo": your own page, with Fluveo's payment form in it. - "Integrate Fluveo payments into this app": payments made from your server, with no page of ours. ## Install the skill A coding agent that loads skills can keep the custom checkout rules at hand. Download [SKILL.md](https://docs.fluveo.com/skills/fluveo-custom-checkout/SKILL.md) and save it in a folder named `fluveo-custom-checkout` inside the folder your agent reads skills from. For an agent that reads `.agents/skills` in the project, the file is `.agents/skills/fluveo-custom-checkout/SKILL.md`. The skill is short on purpose: the rules, the steps and the checks. It sends the agent to [/llms/custom-checkout.txt](https://docs.fluveo.com/llms/custom-checkout.txt) for the code, and to [/llms/payment-element.txt](https://docs.fluveo.com/llms/payment-element.txt) for the form's options. ## Connect the MCP server The Fluveo MCP server is not available in production yet. It lists 28 tools, each shown only to a key whose permissions allow it. `search_fluveo_docs` and `fetch_fluveo_doc` read these docs. `fluveo_api_search`, `fluveo_api_details`, `fluveo_api_read` and `fluveo_api_write` find and run API operations. `get_account_info` names the store behind the key. Seven more each read one kind of store data: `get_balance`, `list_disputes`, `retrieve_dispute`, `list_events`, `retrieve_event`, `list_webhook_endpoints` and `retrieve_webhook_endpoint`. `list_customers`, `retrieve_customer`, `create_customer` and `update_customer` read and change the store's customers. `create_checkout_session` and `create_payment_link` make a Fluveo payment page or a payment link for a buyer. `list_payments`, `retrieve_payment`, `search_payments`, `list_refunds` and `retrieve_refund` read the store's payments and refunds. `create_refund`, `capture_payment` and `cancel_payment` refund, capture or cancel a payment, each only after a person approves that one call in the Dashboard. [MCP tools](https://docs.fluveo.com/agents/mcp/tools.md) has each one's arguments and answers. ## Limits - **Markdown has its own address.** A page always answers HTML, even to `Accept: text/markdown`. Ask for the `.md` address instead. - **The MCP server starts no payment.** Through it an agent reads the docs and the store, and runs the writes its agent key allows, with a person approving the sensitive ones in the Dashboard. An agent key may not create or confirm a PaymentIntent, or create a payout. An agent's code creates payments with a secret key and plain HTTP calls to the API. ## Next - [Integrate Fluveo with an AI agent](https://docs.fluveo.com/agents/integrate.md): the step-by-step playbook. - [Fluveo MCP](https://docs.fluveo.com/agents/mcp.md): let an AI client read and change your test store through the MCP server. - [The ready prompts](https://docs.fluveo.com/agents/prompt.md): copy one into your coding agent. - [Quickstart](https://docs.fluveo.com/start.md): your first payment, written for people. - [Testing](https://docs.fluveo.com/start/testing.md): test keys and test values.