uxgen.ai

uxgen teaches your agent the trade of selling: the order of the sections, the photography, a locked grammar, and an audit that rejects a page unable to take money. Account: not signed in yet — that is normal on a fresh install, and it is not a billing problem. Call any tool: the server answers 401 with the authorisation it needs, your client opens the browser, and the account signs in. If you have already paid, sign in with the address you paid with. 🔴 THIS IS A REMOTE SERVER, AND THAT CHANGES ONE THING ONLY: IT NEVER TOUCHES YOUR DISK. No tool here takes a file path, and no tool here writes a file. You send CONTENT, you get CONTENT back, and YOU write it. Read your file, paste it as `html`; take what comes back and save it. WHAT EXECUTES — all but one of the 14, on the real engine: · `uxgen_brief` — FIRST, before the first tag. The design law and the trade. · `uxgen_theme` — the locked grammar and its CSS, right after the brief. Pass `heriteDe` (the HTML of a page of the site this one joins) whenever the page is not standalone: without it the typeface comes from a HASH of the brand colour, and a page entering an existing site comes out in a DIFFERENT font. Measured 09/09. · `uxgen_demarrer` — 🚨 THE SKELETON AND THE RECIPE, and it is NOT optional. It decides how many pages, in what order, and what each band must prove. Call it after `uxgen_theme` and BEFORE writing anything. Skipping it is the single most expensive mistake on this server. · `uxgen_poser` — 🚨 IT WRITES THE PAGE, you do not. Fill every `contenu` of the recipe with the customer's own words (hold the `_max` limits) and send the whole recipe back. Bench of 28/08: 1 166 tags laid by the engine, ZERO written by hand. What stays yours: the WORDS, and the choice of skeleton. · `uxgen_audit` — send `html` or `url`. Real headless Chrome, five widths, the computed styles, and a robot that clicks the buying path. Named gaps with their selector, no score. ⏱ 45 to 65 s — that is not a hang. · `uxgen_render` — send `html`. You get the first screen and the full page at 390 and 1440 as real images. OPEN THEM before changing a line. · `uxgen_publier` — send `html`. It returns the verdict and the content to write, plus the relative path it recommends. It publishes nothing itself. · `uxgen_packshot` — send the photograph as `photoBase64`. You get the image. · `uxgen_status` — engine state, plus your image allowance. · `uxgen_piece` — one part, its HTML and its prompt. Free accounts: 10 parts; paid: all 173. · `uxgen_image` — generation, charged to your image allowance. · `uxgen_seo` — one seed keyword in, an SEO plan out: monthly traffic, difficulty, who holds the top of the page today, and what to write to take it. Live Google data through our key, charged to a separate monthly allowance. Pack plan and up. · `resources/list` then `resources/read` — the teaching library, including the design law (117 272 characters). `uxgen_brief` names the two to open first. This is the channel with no size cap: use it. 🧷 IF THE MERCHANT ALREADY HAS A STORE: never rewrite their page. Inherit their theme (`uxgen_theme` with `heriteDe`), add only what the audit names as missing (`uxgen_audit` with `conserver: true`), at the anchor it names, with `uxgen_piece`, and show a per-section diff (kept / changed / added) before publishing. `uxgen_brief` defaults to `mode: "improve"` as soon as the sentence mentions an existing site. Rebuild only when they ask for it in those words. THE ONE THAT REFUSES: `uxgen_ameliorer`. It adjusts the CSS of one section and never adds one; its judge is a vision model, no vision key is posed here and its engine is not deployed. The refusal says so. Do not invent its result. 💰 IMAGE ALLOWANCE — every account gets an amount per month, and every image really consumes it. A quota refusal carries a JSON block with `code` and `reessayable`: when `reessayable` is false, IT IS A DECISION, NOT AN OUTAGE — stop, do not loop, and tell your user.