AI editorial assists

louise-toolkit/ai adds optional Workers AI editorial help: alt text generated from an uploaded image, rewrite/tighten a passage, and SEO title + description suggestions. Everything is opt-in and best-effort—with no AI binding, or on any model error, the helpers return null and never block a save, upload, or publish.

Wiring

Add the binding, then opt each feature in.

wrangler.jsonc

"ai": { "binding": "AI" }

Alt text on upload—an accessor on the media route fills each new image’s alt from the image:

mediaRoute({ table: media, resolveEditor, altText: (env) => env.AI });

Rewrite + SEO—mount aiRoute for the editor client to call:

aiRoute({ resolveEditor, ai: (env) => env.AI });
//  POST /api/louise/ai/rewrite  { text, mode? }  → { text }
//  POST /api/louise/ai/seo      { content }       → { title, description }

Both are session-gated, same-origin mutations (each call spends AI budget), and answer 503 when the binding is absent—so the assist is cleanly optional.

Cost

Workers AI is billed in Neurons with a 10,000/day free allocation, then $0.011 per 1,000 Neurons. In practice each assist is a fraction of a cent (alt text ≈ $0.0002–0.0004/image; rewrite/SEO ≈ $0.0002–0.0004/call), and the first few hundred actions each day are free.

AI Gateway—caching, cost caps, fallbacks

Route the calls through AI Gateway for response caching (identical prompts are free on repeat), rate limiting (bound request volume and spend), retries + provider fallback, and request logging/analytics—all configured on the gateway, transparent to your code.

1. Create a gateway in the Cloudflare dashboard (AI → AI Gateway → Create Gateway) and note its id. Set caching, rate limits, and fallback there.
2. Pass the gateway config through—per feature:

// alt text: options flow through the media route
mediaRoute({
  table: media,
  resolveEditor,
  altText: (env) => env.AI,
  altTextOptions: { gateway: { id: "louise-gw", cacheTtl: 86400 } },
});

// rewrite + SEO: a gateway accessor on the route
aiRoute({
  resolveEditor,
  ai: (env) => env.AI,
  gateway: (env) => ({ id: "louise-gw" }),
});

Gateway caching already keys on the full request (model + inputs), so identical calls dedupe automatically. Set cacheKey only to deliberately widen a cache entry (for example, a content hash) across incidental request variance; cacheTtl: 0 disables caching for a call, and skipCache: true forces a fresh run.

Omit gateway and calls go straight to Workers AI—the gateway is purely additive.