Skip to content

Documentation

The input format and the output format

A reference for the brief, the output structure and the export. Everything needed to fit packs into your process rather than fit your process around the service.

Brief fields

The brief is the pipeline's only input. Everything in the output derives from it, so a thin brief produces generic output and a detailed one produces specifics.

FieldRequiredDescription
offeryesWhat you sell, in your own words. 10 to 4000 characters.
offerUrlnoA link to the product, if one exists.
verticalyesThe vertical: gambling, nutra, SaaS, finance and so on.
geoyesThe market you buy in. A country code or a list.
languageyesThe creative language. It need not match the interface language.
platformyesmeta, tiktok, google or telegram. This sets the limits.
audiencenoWho buys. The more concrete, the sharper the angles.
tonenoThe tone. Neutral and businesslike by default.
constraintsnoWhat is off limits: income claims, competitor mentions, health claims.

Output schema

Each section returns a fixed structure. Below are the fields per section, exactly as they land in the JSON export.

Angles and hooks

  • name a short name you can recognise in a spreadsheet
  • insight the belief or friction the approach rests on
  • rationale why it lands on this audience in this geo
  • segment the sub-segment it speaks to
  • risk low, medium or high by how likely the platform is to object

Ad copy

  • hook the first three seconds, spoken aloud
  • primaryText primary text inside the platform limit
  • headlines three to six headlines that stand alone
  • descriptions two to four descriptions
  • angleId a reference to the angle so the pairing is never lost

UGC scripts

  • title a working title for the video
  • duration 15s or 30s
  • scenes[].timecode scene bounds, for example 0:00 to 0:03
  • scenes[].visual what happens on camera
  • scenes[].voiceover what is said
  • scenes[].onScreenText the on screen caption

Prelanding blocks

  • headline headline, up to 90 characters
  • subhead subhead, up to 180 characters
  • benefits three to five concrete benefits
  • cta one call to action, up to 40 characters

Image prompts

  • format 1:1, 4:5 or 9:16 for the placement
  • prompt the scene description for the generator
  • negative what to keep out of the frame

Policy review

  • severity ok, caution or block
  • where which piece of copy it refers to
  • quote the exact offending span
  • rule the platform rule it brushes against
  • rewrite a rewrite that keeps the meaning

Export formats

CSV suits the ad account and client sign off: one row is one finished variant. JSON keeps the whole structure, including the nested scenes of a script.

  • CSV is UTF-8 with a BOM, so Excel opens non-Latin text without a fight.
  • JSON mirrors the output schema exactly, with no wrapper and no metadata.

Credits and limits

  • A full pack costs 10 credits. The policy pass is free and always runs.
  • Credits are taken before the model call and returned automatically if the section fails.
  • Character limits come from the brief's platform: Meta (Facebook / Instagram) 125/40/30, TikTok 100/40/40, Google Ads 90/30/90, Telegram Ads 160/40/60.

Abuse protection

Public endpoints are gated by a proof of work: the browser solves a small computation before the form is submitted. For a person that is a fraction of a second; for a script that wants ten thousand free generations it is ten thousand puzzles.

  • One solved puzzle buys exactly one request: replaying the pair is rejected.
  • Rate limiting counts against an irreversible hash of the client; the raw address is never stored.
  • There are no third party widgets and no trackers on the public pages.

Ready to try it

Thirty credits on signup.