Ir al contenido
Floweet
Acceso pro

Plans, modules and AI

A key acts with its organization's plan: some modules need a higher plan (plan_required); pitches are written by AI with a live key, else from a template.

api.floweet.com/v1 · Contract 1.0.0-beta.1 · Beta

This documentation is written in English and French; it is shown to you in English.

Sections · Plans and AI

The API sells nothing of its own: a key acts with its organization's plan, exactly like the Floweet app for the member it acts for. Some modules are reserved to some plans, and the pitch is written by AI only with a live key.

What each plan opens

Plans go from Freemium to Enterprise, in this order: Freemium, Pack Simulation, Pro, Enterprise. A plan also opens the modules of the plans before it.

Module outside the plan

An operation whose module is not in the organization's plan answers 403 plan_required, with the module and the minimum plan in the details. Nothing is read or written.

Response 403
{
  "error": {
    "code": "plan_required",
    "message": "This module is not included in your organization's plan.",
    "details": {
      "module": "stations",
      "tier": "PRO"
    }
  }
}

To open it, change the organization's plan, or write to us at contact@floweet.com.

The pitch and AI

Writing a simulation's pitch is the only operation that may call an AI model:

  • with an fw_live_ key, AI writes the pitch; if it does not answer, or if the organization's daily cap of AI pitches is reached, the template takes over;
  • with an fw_test_ key, the pitch always comes from the template: no AI call is made;
  • the response's generator field says which one wrote it: gemini or template;
  • the pitch is written in the Accept-Language language and saved on the simulation: it replaces the previous one, and the app shows it.