Write landing page labels, or check them with dryRun
Stores one label card per landing page: industry, product form, target gender, target age, price band and page kind, each a value of the named list version or null. StefanBrain computes the landing key from each raw URL and checks each value against its list. Every item gets its own result, in order: a refused item names its reason and does not stop the others, and an unknown value returns the valid values. Idempotent: the same request sent again answers already_stored. dryRun: true runs every check, returns each landing key, and writes nothing. A stored card is never edited, and it is not shown in benchmarks until StefanBrain activates its label version. 1 to 200 items in a UTF-8 body of at most 32 MB. Rate-limited, never metered. Requires the tools scope and the account’s own landing_page_label_writer grant.
Authorizations
Authorization: Bearer stefan_sk_... (API key — bills the API wallet) or stefan_oat_... (OAuth member token — bills your plan pool).
Body
The name of this way of reading pages. Its first write binds it to taxonomyVersion, model and promptVersion; a later request under the same name with another of them is refused. A name starts with estate-: StefanBrain keeps every other name for its own readings.
^estate-[a-z0-9._-]{1,57}$The list version the labels are values of.
1 <= x <= 2147483647The model that made the labels.
1 - 200The version of the prompt that made the labels.
1 - 200SHA-256 of the file the items came from.
^[0-9a-f]{64}$true checks every item and returns each landing key, and writes nothing.
One item per landing page.
1 - 200 elementsResponse
One result per item, in the order the items were sent.
One result per item, in the order the items were sent.
- Option 1
- Option 2
- Option 3
- Option 4

