Anticode features
Each page below covers one thing Anticode does: what it's for, how to use it, how it works underneath where that matters, and its limits. Nothing here is a plan or a roadmap item; if it's listed, it works today.
Where to start
If you're new, how Anticode works walks through a build from the first sentence to the published page. The pages here go deeper on single features once you know which one you need.
Accounts and plans
- FeatureAI build receipts: tokens, cost and model for every buildWhat Anticode's AI build receipts list for each model build: tokens, cost, share of the daily and weekly limit, and why failed builds say Not charged.
- FeatureCredit packs: extra model builds, bought once, kept until usedHow Anticode's credit packs work: AI website builder credits that never expire, bought once and spent only on builds that go past your plan's allowance.
- FeatureTeam workspaces: one shared set of projects, three rolesHow Anticode's Team workspace shares projects and sites with invited people, and what the website builder team roles of owner, admin and member can each do.
- FeatureThe Agency plan: client sites under your name, built by your teamWhat Anticode's Agency white label plan for client sites removes (badge, generator tag, credit line), keeps (a hosting disclosure) and how its workspace works.
- FeatureThe build quote: what a model build will use, before it runsHow Anticode gives an AI build cost estimate before each model build: a share of today's limit, a token count, and the go-ahead an AI assistant must ask for.
- FeatureTwo-factor sign-in: an authenticator code after every sign-inHow website builder two factor authentication works on Anticode: authenticator app codes, ten recovery codes, and why sites that collect data need it on.
- FeatureUsage allowance: a daily and a weekly limit, measured by what builds costHow Anticode's AI website builder usage limits work: daily and weekly allowances measured by real build cost, Not charged for failures, and how Max relates to Pro.
Building
- FeatureBuild a preview with no account, and sign in only when it's worth itUse Anticode as an AI website builder without sign up: design-engine previews run in your browser, then an account adds model-written builds, saving and publishing.
- FeatureMulti-page sites: separate pages that share one header and designHow Anticode works as an AI multi page website builder: Work, Shop, Services, About, Pricing, FAQ, Book and Contact pages, each with its own title and checks.
- FeaturePhotos and videos: give the build your own picturesHow to add your photos to AI website and app builds in Anticode: upload up to eight files, the model sees each photo, and videos are placed by their file name.
- FeatureSelf-review: the build opens its app in a browser and fixes what it seesHow Anticode's AI builder screenshot testing works: each new app opens in headless Chrome at phone and laptop widths, gets clicked through, and is fixed.
- FeatureThe app sandbox: what a model-written app can and can't doAnticode is a sandboxed AI app builder: model-written apps run with no network, save to the visitor's browser, label demo data and send forms through Anticode.
- FeatureThe Architect: talking a build through before anything is madeAnticode is an AI website builder that asks questions before it builds: up to three, each with answers to tap, then a short plan you approve with Build it.
- FeatureThe template gallery: twelve sites and apps the model wroteAnticode's AI website templates are twelve sites and apps in very different styles. Copying one into your project uses no model call and nothing off your limits.
Code and agents
- Featureanticode.json: the open file every Anticode project lives inWhat anticode.json holds, how its public website project JSON schema validates it, and the rules /AGENTS.md gives coding agents for editing it safely.
- FeatureBuild and publish from your AI assistant with Anticode's MCP serverAnticode as an MCP website builder: connect Claude, ChatGPT or Cursor to /mcp with OAuth 2.1, then create, quote, build, edit and publish sites from the chat.
- FeatureCode-to-canvas sync: outside edits appear on the canvas, with an undoHow Anticode can sync coding agent edits to website builder canvases: the open builder spots outside changes, redraws with an undo and refuses stale writes.
- FeatureExport your site or app as a standard Next.js projectAnticode's AI website builder code export gives you a Next.js App Router project with TypeScript, Prisma and Postgres, server routes for each form and an admin area.
- FeatureHTML export: your page as one self-contained fileWhat you get when you export a website as a single HTML file from Anticode, what stays behind on Anticode's servers, and where the file can be hosted.
- FeatureThe Anticode CLI: work on a project from your terminalHow the Anticode website builder CLI signs in with a device code, pulls a project into a folder, pushes your edits back and publishes behind the server's gate.
Design checks
- Design checkAI stock phrases: website copy words the check flags, and what to write insteadThe AI stock phrases in website copy that Anticode's Critic and design gate flag, how the match works, where it misfires, and how to write specific lines instead.
- FeatureDead links: the check that stops links going nowhereHow Anticode's dead links on website check works: which empty, # and missing-anchor links the Critic reports, which ones the design gate refuses at publish.
- FeaturePlaceholder phone numbers and leftover template text, caught before launchWhich fake numbers the placeholder phone number check flags, and which leftover template text the design gate refuses at publish, from 555 numbers to example.com.
- Design checkThe body text size check: why paragraphs start at 16pxWhat the Critic's body text size check reads from a page's CSS, why body text under 16px fails readers on phones, where the check misfires, and how to build a scale.
- Design checkThe card hover lift check: why rising cards look generatedWhat the Critic's card hover lift check matches in CSS, why cards that rise on hover read as a template, and the hover states Anticode's design systems use instead.
- FeatureThe coloured glow check: what counts as a glow and why it dates a pageHow the Critic's coloured glow check reads box-shadow values: 40px of blur or more in any colour other than black. Why the effect looks generated, and what to use.
- FeatureThe Critic: nineteen design checks on every buildHow the Critic works as an AI website design checker: nineteen checks for generic AI tells, run on the exact HTML of each build, with results in the Report tab.
- FeatureThe design gate: twelve basics a page must meet before it's publishedWhich design basics Anticode's website design quality gate enforces before publishing, how each is detected, how to fix a failure and how app builds are repaired.
- Design checkThe ease check: why CSS default ease timing marks an untuned interfaceWhat the Critic's check for CSS default ease timing matches, why the browser's stock curve makes motion feel untuned, and the curves Anticode's design systems use.
- FeatureThe em dash check: keeping long dashes rare in your copyHow the Critic's em dash check counts long dashes in a page's visible copy, why more than two reads as machine-written, and four ways to rewrite the sentences.
- Design checkThe emoji icon check: finding emoji that stand in for iconsWhat the Critic's emoji icon check matches in a page's text, why emoji used as icons look generated and render differently per device, and what to do instead.
- Design checkThe eyebrow label check: when every heading wears a small labelHow the Critic's eyebrow label check finds spaced-capitals labels above headings, why one over most sections reads as templated, and when a single label is fine.
- Design checkThe font family check: why a one font family website reads as designedWhy Anticode's Critic allows one font family or one pairing, how the design gate refuses a third family, how each check counts fonts, and how to fix a failure.
- Design checkThe full height hero check: size the hero to its content, not the screenWhat the Critic's full height hero check matches, why a hero forced to 100vh hurts on phones and hides your content, and what sizing a hero to its content means.
- Design checkThe headline formula check: two patterns that make a hero sound generatedThe two hero headline shapes the Critic's headline formula check catches, X, not Y and two clipped fragments, why they read as generated, and plain alternatives.
- FeatureThe highlighted word check: why one recoloured word gives a page awayWhat the Critic's highlighted word check looks for in a page's main headline, why one coloured or italic word became a template habit, and what to do instead.
- FeatureThe language check: why a page must say what language it's inWhy Anticode's design gate runs an html lang attribute check before publishing, what lang does for screen readers and translation tools, and how the check reads it.
- FeatureThe opacity hover check: why fading on hover is weak feedbackWhat the Critic's opacity hover check flags in a stylesheet, why a hover that only fades an element tells visitors little, and what a hover state should change.
- FeatureThe overused font check: eleven typefaces that make sites look alikeThe eleven fonts the Critic's overused font check flags, why generated sites keep choosing them, and how Anticode's seven design systems pick a typeface instead.
- Design checkThe purple gradient check: what it flags and what to use insteadHow Anticode's purple gradient check finds gradients that mix purple, violet or indigo, why the design gate refuses them, what it misses and what to use instead.
- Design checkThe radius by role check: giving each kind of element its own shapeWhy corner radius should follow an element's role, what the Critic's radius by role check counts and its limits, and how Anticode's seven design systems set corners.
- FeatureThe reduced motion check: animation that turns down when people askHow Anticode's reduced motion check before publishing works: any page that animates must answer prefers-reduced-motion, and what the design engine does about it.
- FeatureThe serif fallback check: what happens when a web font doesn't loadWhat Anticode's serif fallback font check refuses at publish, why a serif fallback shows Times when a web font fails, and how design-engine font stacks are built.
- FeatureThe thin footer check: use the place visitors look for detailsWhat the Critic's thin footer check flags, why a footer that's only a copyright line wastes valuable space, and what a small business footer should carry.
- FeatureThe viewport check: why a page without one looks tiny on a phoneWhat Anticode's mobile viewport meta tag check requires at publish, why a page without the tag shows zoomed out on phones, and what the tag does and doesn't fix.
- FeatureThe visible focus check: keeping keyboard users able to see where they areWhy Anticode's design gate runs a visible keyboard focus check before publishing, what removing the outline does to keyboard users, and the style pages ship with.
Design systems
- FeatureAction colours: one website action colour, chosen from eightWhy an Anticode site has one website action colour, where it's used, the eight choices from red to black, and how to change it in the visual editor or in words.
- Design systemThe Brutalist design system: Archivo, heavy rules and hard shadowsWhat the Brutalist design system with Archivo sets in Anticode: condensed capitals, 2px rules, hard offset shadows, square corners, and where it came from.
- Design systemThe Editorial design system: Geist, hairline rules and a big headlineWhat Anticode's Editorial design system with Geist sets: paper and ink palette, square images, pill buttons, hairline rules, and the sites it suits best.
- Design systemThe Luxury design system: light Jost type and a lot of quietWhat the Luxury design system with Jost sets in Anticode: champagne on black, light display type, wide-tracked capitals, square edges and full-bleed photos.
- Design systemThe Organic design system: Figtree, sage and clay, and an arched photoWhat the Organic design system with Figtree sets in Anticode: a sage and clay palette, soft rounding by role, an arched hero photo, wavy links and its best uses.
- Design systemThe Playful design system: Fredoka, rounded shapes and a springy heroWhat the Playful design system with Fredoka sets in Anticode: cobalt and sunflower colours, generous rounding by role, springy hero shapes and where it fits.
- Design systemThe Swiss design system: Inter Tight, numbered sections and a single redWhat the Swiss design system with Inter Tight sets in Anticode: black, white and one red, square edges, numbered sections and how it applies the International Style.
- Design systemThe Technical design system: IBM Plex Sans on a blueprint gridWhat the Technical design system with IBM Plex Sans sets in Anticode: graphite and amber palettes, a blueprint grid, compact radii, and which sites it suits.
- FeatureThemes: what the auto light dark website theme options actually doWhat Anticode's Auto, Light and Dark themes do: Auto keeps the design system's own palette, Light and Dark use its other one, and none follow the visitor's device.
Editing
- FeatureChange requests: describe the change and keep everything elseHow Anticode lets you edit website with AI prompts: quick changes apply with no model call, others are written by the model, and each is checked for breakage.
- FeatureClient review links: show the preview, collect comments by sectionA client review link with section comments: your client opens the current preview with no account, comments on any section, and the link expires or can be revoked.
- FeatureSimple and Pro modes: how much of the builder you seeWhat Anticode's website builder Pro mode adds over Simple mode: Code, Map and Report tabs, agent logs and keyboard shortcuts. A setting, not a plan.
- FeatureThe code editor: edit the HTML and watch the preview followEdit website HTML code in Anticode's Pro mode: text, section order and colour tokens map back to the project, and scripts or javascript: URLs are refused.
- FeatureThe layout editor: drag, resize and layer, without breaking on phonesAnticode's drag and drop layout editor turns each drop into order, layers or anchors and each resize into column-snapped sizes, so the page holds at every width.
- FeatureThe Map tab: sections, forms, data and connectors, and what a change touchedHow the builder's Map tab draws a website structure map of sections, forms, routes, stored data and connectors, and checks that a change broke nothing.
- FeatureThe visual editor: change words, order and look without a new buildAnticode's AI website builder visual editor lets you retype text on the page, reorder sections and switch direction, theme or colour without asking the model.
- FeatureVersion history: preview and restore any saved versionHow Anticode's website builder version history works: each save becomes a numbered version you can preview on the canvas and restore without losing later ones.
Forms and data
- FeatureApp forms: how a sandboxed app still reaches its ownerHow a contact, booking or newsletter form inside an Anticode app reaches the owner through anticode.send, with the same checks and connectors as page forms.
- FeatureCMS collections: content you edit without rebuilding the siteHow Anticode's website builder CMS collections work: typed fields, entries edited in the dashboard, sections that list them and a page of their own for each entry.
- FeatureForm connectors: send every submission where you already workAnticode's website form integrations send submissions to Slack, Discord, Telegram, Sheets, Airtable, Notion, HubSpot, Mailchimp, Kit or a webhook, with sealed keys.
- FeatureFormula functions: work out a quote from a form's fieldsHow a quote calculator form formula works on an Anticode site: one line per result, worked out on the server, shown on the thank-you page, with clear limits.
- FeatureSite functions: run your own logic when someone sends a formHow site functions add custom server logic for website forms: a signed HTTPS call to your endpoint, its reply on the thank-you page, and what happens when it fails.
- FeatureWhere your site's form submissions go, and who can read themHow Anticode handles website form submissions: saved and sealed with AES-256-GCM, optional email alerts, CSV export, a retention setting and a log of every read.
Payments and bookings
- FeaturePayment links: point your buy and pricing buttons at your own checkoutHow to add a payment link to website buttons in Anticode: paste a Stripe, PayPal, Gumroad, Lemon Squeezy, Shopify or Whop link and your buttons open that checkout.
- FeatureThe booking calendar: current days, real dates and one booking per slotHow Anticode's booking calendar that prevents double booking works: the coming days on every visit, past or far-off dates refused, and each slot taken once.
Publishing
- FeatureApp-store packaging: your published site as an iOS and Android projectHow Anticode's website to mobile app packaging works: a store checklist read from your site, a Capacitor project to download, and what you still do to submit.
- FeatureBackups and integrity: every published file checked against its fingerprintHow Anticode handles website backups and integrity monitoring: ten published versions kept, file hashes recorded at publish, a daily recheck, and repair or takedown.
- FeatureInstallable sites: every Anticode site can live on a home screenHow to make website installable PWA-style with no work: Anticode adds a manifest, generated icons and an offline fallback while your pages keep no scripts.
- FeatureIntelligence: your sites' numbers, and an analyst that has to cite themWhat Anticode's website performance dashboard AI analyst shows: visits, leads, model use, a forecast only after 14 days, and answers that cite measured numbers.
- Featurellms.txt: a plain summary of your site for AI assistantsWhat Anticode's automatic llms.txt for every site says (the business, its offer, contact and every page), how it's built from what you publish and its limits.
- FeaturePrivacy and Terms pages written from what your site really doesHow Anticode's auto generated privacy policy and terms are written from each site's forms, connectors and services, why they update themselves and their limits.
- FeaturePublish to an anticode.dev address, then move to your own domainHow the AI website builder custom domain set-up works in Anticode: a free <name>.anticode.dev address, then your own domain on a paid plan with HTTPS set up for you.
- FeatureSite analytics: visits by source, counted without cookiesWhat Anticode's cookieless website analytics count (visits per day by source, AI assistants and crawlers kept apart) with no trackers, and what they leave out.
- Featuresitemap.xml and robots.txt, written for every published siteWhat the website builder automatic sitemap and robots.txt on each Anticode site contain, including CMS entry pages, and why they stay current with no work.
- FeatureThe Made with Anticode badge: which plans show it, and what else names AnticodeWhich plans carry the small Made with Anticode badge, how to remove made with badge website builder branding by upgrading, and what changes on Agency sites.
- FeatureThe release checklist: know a build will publish before you press PublishHow Anticode's website release readiness check runs the security gate, design gate and security baseline after every build, and says what's missing and where.
- FeatureThe security report: what your published site does, shown liveWhat each Anticode site's public website security report shows (checks, the exact CSP, what loads from where, how forms are wired) and why it's computed live.
Security checks
- FeatureAlt text on every image: how Sentinel and the design gate check itWhy every image needs a text alternative, how Sentinel's image alt text check differs from the design gate, and how curated photos and illustrations get theirs.
- Featureform-action 'self': why the policy guards form targets as wellWhy Anticode pages carry form-action self in their CSP, how it protects a page if an edit or an injected form tries to post elsewhere, and what it can't do.
- FeatureForms post to your own site: the check that keeps submissions at homeWhy every Anticode form must POST to a form action on its own origin under /api/, how generated forms leak data otherwise, and how the server re-checks it.
- FeatureInline event handlers: why onclick and onerror never shipInline event handlers security explained: how onclick-style attributes carry script, how Sentinel and the server find them, and what the code editor refuses.
- FeatureKeys and tokens in the page: what Sentinel looks for before anything shipsWhich key and token patterns Sentinel scans for when an API key is exposed in HTML, why anything in a page is public, and what to do if a real key turns up.
- FeatureLabelled fields: the three ways Sentinel accepts, and why placeholders aren't oneHow Sentinel's form field labels accessibility check works: the three ways a field can be labelled, why placeholder text doesn't count, and how Anticode does it.
- FeatureNew-tab links and noopener: closing the window.opener gapWhat a target blank link can do to your page without rel noopener, why Sentinel still requires it on every new-tab link, and how to fix a link that fails.
- FeatureNo scripts at all: why Anticode pages ship without JavaScriptWhy every Anticode design-engine page is a website with no JavaScript, how Sentinel and the publish gate enforce it, and what still works without scripts.
- FeatureSentinel: a security scan on the exact HTML that shipsHow Sentinel runs an AI website security scan on every Anticode build: twelve checks in the builder, a server re-check at publish and one-click fixes where safe.
- FeatureThe app code gate: twelve checks on every program the model writesThe AI generated app security checks Anticode runs on every app build: one document, no network, no frames, no eval, forms via anticode.send, and one repair pass.
- FeatureThe CSP check: a Content-Security-Policy on every page, and what it saysHow Sentinel works as a website CSP checker, what a Content-Security-Policy does, and the exact policy Anticode pages carry in their head and their response headers.
- FeatureThe HTTPS check: no plain-HTTP addresses on a secure pageWhat mixed content is, why an http:// image, link or form target on an HTTPS page is refused, and how Sentinel's mixed content check and the publish gate find it.
- FeatureThe referrer policy check: keeping full addresses privateWhat a referrer policy meta tag keeps private when visitors follow your links, the policy Anticode pages set, how Sentinel checks for it and how to check any site.
- FeatureThe security baseline: twelve items, checked for the site in handThe website security baseline every Anticode site meets, the items that only apply when a site collects data, and why publishing waits for two-factor sign-in.
- FeatureTyped, length-capped fields: why every input needs a type and a maxlengthWhy Sentinel wants a type and a form input maxlength on every text field, the limits Anticode's built-in forms use, and why the server checks every field again.