Documentation
Glossary
Every term FlowFinds uses, defined once.
Every term FlowFinds uses in its API and its product, defined once. Where a term has a precise mechanical meaning that differs from its everyday one — hold, qualified, refusal, publish — the definition here is the binding one.
42 terms. For how they fit together rather than what each means, read Concepts.
Account
An email address, and the durable subject of everything that is not session-scoped: claims, revenue, the usage meter, the referral link. Binding one to a session adopts everything that session already did. See Authentication.
Ad artifact
A generated creative with explicit pass criteria attached — a minimum click-through rate and a maximum cost per click — so the artifact states in advance what would count as it working. An ad may not assert a present-tense angle on evidence older than the permitted age.
Allowance (claim allowance)
How many products one account may claim. Distinct from the usage meter. Reaching it is answered with claim_limit_reached, which — unlike the other exhaustion states — has an exit.
Attention
One of the two verdicts. Something needs the operator, and the response carries the specific items that earned it. Its opposite is quiet.
Because
The prose justification on an intent proposal, paired with source_row. Not decoration: an intent with no evidence to cite is refused rather than executed. See Concepts.
Bucket
One metered feature’s own allowance. There are five — website_edit, growth_edit, find, ad, support — and they are not pooled, so exhausting one leaves the others untouched. See Rate limits.
Claim
A permanent, exclusive assignment of one product to one founder. Not reversible, not queued, and not the same as a hold. See Concepts.
Control
An endpoint described by its effect rather than its signature. GET /api/controls serves, per endpoint, its consequence, whether it is reversible, and a note on what it does not do.
Credit
The meter’s internal unit. Costs are relative to each other, not to a currency: a website edit costs 50, a support answer costs 1.
Dead-control defect
The named failure of rendering a control that cannot work — a preview button for a product with no offer, a top-up button where payments are unconfigured. The API serves availability flags such as preview_available and can_top_up specifically so a client need never guess.
Evidence row
A dated, sourced fact attached to a product: a URL, a date, a claim, and a leg. The currency the whole system spends — it drives freshness, justifies intents, and bounds what an ad may assert.
Exclusivity
The contract that no other session’s claim may surface on yours, enforced by a single founder-scoped resolver rather than by a filter each endpoint applies for itself.
ff_session
The session cookie, and the entire credential. Issued to any request arriving without one; Path=/, Max-Age=31536000. See Authentication.
Founder
The person operating one FlowFinds business. In the API, the subject a session or account resolves to. Used in reason codes such as claimed_by_another_founder.
Freshness
A derived figure on a product, computed from the age of its evidence rather than stored. Served alongside evidence_age_days and score.
Funded first sale
A stated commitment carried in the referral response: every founder’s first sale is funded because they joined, not because someone referred them. The response says so explicitly so the referral copy cannot claim credit for it.
Hold
A temporary, expiring resolution of a product to one session while the founder decides. A hold is not ownership — endpoints that require a claim refuse a hold with no_claim.
Intent
A requested change, served back as a proposal with its because, its source row, the alternatives considered, and whether it is reversible. applied_at stays null until someone accepts it. See Concepts.
Leg
The persuasion function an evidence row can serve — urgency or scarcity. An intent resolves to a leg, and the leg selects which section leads the page.
Manifest
The store’s record of what was generated. A store is ready only when the manifest exists and its browsable path resolves. A stale manifest is regenerated by publishing.
Milestone
An observed event in a journey — account_saved, dashboard_entered, card_pressed. Milestones are what make a referral qualified; nothing is inferred.
Offer
The price layer over a product: the price, the margin it implies, and the observed third-party listings it undercuts. Either status: "offer" or a stated reason — never an invented number.
Organic campaign
Briefs, strategies and an approval log for unpaid distribution. It posts nothing — there is no platform account behind it — and the API does not claim otherwise.
Pass
Declining a candidate. Final: a passed product is never re-offered to you, and a claim attempt on one is refused with passed_by_you.
Pass criteria
The thresholds an ad artifact must clear to count as working, stated on the artifact before it runs rather than judged afterwards.
Product
A catalogue entity with dated evidence behind it. You do not create products; you are shown them, and you claim one. See Concepts.
Qualified referral
A referral where the friend really joined and reached the dashboard. Neither “invited” nor “clicked” counts. Only qualified referrals move the multiplier. See Rate limits.
Quiet
The verdict meaning nothing needs the operator right now. The opposite of attention.
Reason
The stable machine-readable key on any refusal. Branch on this rather than on the HTTP status, which varies by endpoint for the same reason. The full registry is served at GET /api/reasons. See Errors.
Referral code
A durable, account-owned link code, derived by hashing so it cannot be enumerated. Signing in elsewhere never changes it; historic device codes are kept alive as aliases.
Referral multiplier
The factor qualified referrals apply to your limits: 2.0× at the first, +0.5× each after, capped at 4.0×. Reported separately from the tier multiplier, and the only one referral copy may quote.
Refusal
A well-formed request the system declines to perform, answered with status: "refused" and a reason. Frequently HTTP 200, because the request was understood and the answer is a fact.
Reversible
A flag on intents and on controls saying whether the effect can be undone. An irreversible action requires explicit confirmation and otherwise refuses with irreversible_without_confirmation.
Score
A derived ranking figure on a product, computed from its evidence. Derived, never stored, so it cannot disagree with the rows it came from.
Servable
Whether anything remains that can be shown to this session. not_servable means your own product has left the served set — a state, not a deletion.
Session
The ff_session cookie and the journey attached to it. Can claim, build and hold; cannot be recovered if the cookie is lost with no account bound.
Source row
The URL of the dated evidence row cited by an intent, served as source_row alongside dated. The audit trail for every change the agent proposes.
Store
The generated storefront: eleven pages, a domain, and a section order with a stated reason for that order. Built asynchronously; published by re-crawling, not by flipping a label.
Support agent
The agent that answers customer messages from the product record, bound to that record. A ticket exists only where it could not answer — so an empty desk means it handled everything.
Tier
The plan a meter subject is on: free, pro, max5, max20. Pro is 1.0× by definition and every other tier is a multiple of it. An unknown or expired-term account reads as Free.
Verdict
The dashboard’s single answer: quiet, attention, or not servable. It restates the other surfaces through their own resolvers and never recomputes a figure — which is why it also serves source, naming the resolver behind each number.
Window
A meter period. Two are nested: a five-hour window and a weekly cap, both fixed rather than sliding. resets_at_5h and resets_at_week are epoch seconds.
Next: Concepts · Errors · API reference