The outcome

Expose automation without granting a leaked key broad team access or letting model-selected tools perform uncontrolled actions.

FastGPT is a Open-source AI application platform for knowledge bases, conversational agents, visual workflows, plugins, Agent V2, and OpenAI-compatible APIs. Building grounded Q&A applications from documents, composing visual AI workflows and plugins, and publishing controlled agents through web channels or APIs. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.

Before you begin

Set the boundary before the tool starts.

Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.

Troiana principle

AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.

Step by step

A workflow you can repeat.

  1. 01

    Map inputs, outputs, every node and branch, team resources, external systems, permissions, side effects, idempotency, human approvals, timeouts, concurrency, quotas, SLO, and rollback.

  2. 02

    Separate retrieval, classification, transformation, and action nodes, use schemas and explicit conditions, restrict HTTP destinations, sandbox code, minimize variables, and keep model-chosen tools read-only.

  3. 03

    Create a dedicated least-privilege member and API key, set expiration and quota, store it server-side, pass the explicit app ID, and never assume an app-publishing key is app-scoped.

  4. 04

    Test all branches plus injection, malformed variables, unauthorized resources, SSRF, duplicate requests, loops, parallel limits, timeouts, provider outage, key expiry, denial, and compensation.

  5. 05

    Canary traffic, log redacted node outcomes, monitor errors, latency and spend, rotate keys, retain the prior workflow export, and verify revoked keys, deleted runs, and retired resources.

Working standard

What good use looks like.

  • Assume member keys reach team resources.
  • Restrict HTTP and code nodes.
  • Keep consequential release human-controlled.

FastGPT API keys act with the current member's access inside a team, so they may reach more than one app. OpenAI compatibility does not narrow that scope. Self-hosting requires secure cookies, origins, proxies, SSRF controls, databases, object and vector storage, code sandboxing, secrets, and patches. Isolate teams, minimize keys, validate uploads, constrain HTTP and tool nodes, require human approval, and test backup, restore, deletion, and billing.

Official references

Check the current product documentation.

Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.