Developers
Build on the FlowFinds API
The FlowFinds API: one HTTP interface, the same one the console uses, documented endpoint by endpoint.
What the API is shaped like
A JSON interface served from https://flowfinds.ai. The session is a cookie, set on the first response; there is no API key and no bearer token. A refusal is usually a 200 with a reason — the request was well-formed and the answer is a fact about your account. Nothing under /api/ is cacheable.
90 endpoints are documented from their handlers, in 10 groups, each with parameters, responses, errors and a runnable request. Read authentication and errors before the rest.
curl -s -b cookies.txt -c cookies.txt \
"https://flowfinds.ai/api/find"
curl -s -b cookies.txt -c cookies.txt \
-X POST -H 'Content-Type: application/json' \
-d '{"product_id": "…"}' \
"https://flowfinds.ai/api/select"Endpoint groups
Full referenceDiscoveryBeing shown a product, holding it, passing on it and claiming it. The exclusivity contract lives here.Offer and dashboardThe researched price for a held product, the facts a dashboard renders, and the verdict computed over them.Store and intentsGenerating a storefront, editing it through guided intents, and the domain and checkout paths attached to it.GrowthAd artifacts, the ad balance ledger, organic research and approval, and the referral link.SupplierSourcing terms, the supplier connection, and sample ordering.ActivityOrders, revenue, satisfaction sampling, the support desk and the operator's task list.Account and settingsCreating the account a claim is credited to, signing in and out, and the settings the desk reads.FixThe standalone store-repair tool: submit a URL, watch the run, adopt the result.Assistant and session (product surface)The Next.js routes on the product surface: the commerce assistant, generated pages, the journey carrier, the walkthrough and magic-link sign-in.Internal and administrativeRoutes that exist in the running server but are not part of the developer surface: the founder admin console, the marketing lane, payment-provider callbacks and the paths that serve generated HTML.
Models and engines
View allcommerce-reasoning-v1The decision engine an operator talks to: it investigates a question with application tools before it answers, and it names the evidence it used.The find engineScores a candidate product on three independently sourced legs, and refuses to average them into one comfortable number.The store editorTurns an instruction in the operator's own words into a proposed change with a cited reason, a rejected alternative, and a reversibility flag.
Everything for building
ConceptsProducts, offers, stores, claims, intents and evidence — the model behind the API.Agents and toolsThe tools the agent can call, and how to extend them.CookbookWorking recipes you can paste and run.SDKs and CLIOfficial libraries and the command line.ChangelogDated record of every change to the API and the product.System statusCurrent state of every FlowFinds service, measured every five minutes, with the outage history.