Thin product pages
Thousands of SKUs with a one-line description from the spec sheet. Shoppers bounce, search engines shrug.
For retailers and online stores
Product descriptions for every SKU, review summaries shoppers trust, support replies that resolve on the first touch, and merchandising copy for every season.
descriptions generated at catalog scale
price reported on every call
fail-over through big sale days
The problem
Thousands of SKUs with a one-line description from the spec sheet. Shoppers bounce, search engines shrug.
Shoppers want the gist. Your top products have hundreds of reviews and no summary.
Where is my order. Can I return this. The same questions, ten times the volume.
Capabilities
Turn attributes and spec sheets into on-brand copy, with titles and bullet points per channel.
Condense reviews into pros, cons and who the product suits.
Draft answers from your returns and shipping policies for agents to send.
Catalog copy rarely needs your heaviest model. The router picks the lowest-priced model with the capability.
Re-running an identical prompt inside the cache window returns instantly and is not billed.
Automatic fail-over keeps support assist working when traffic spikes.
Use cases
Descriptions, bullet points and meta copy for every SKU.
A short summary block on each product page.
Policy-grounded reply drafts for your help desk.
Collection intros, gift guides and promo banners.
How it works
Paste attributes into the playground and tune the voice.
Loop through SKUs with an API key and an Idempotency-Key per item.
Daily and month-to-date usage in the dashboard.
Control
API keys are shown once at creation and stored only as a hash. Revoke any key instantly from Settings.
Every request carries its own receipt: tokens in, tokens out, latency and price. Nothing is billed that you cannot trace.
Per-account rate limits and a free monthly allowance keep experiments safe before they become production.
You choose exactly what you send. Repeat prompts can be served from your cache, and cache hits are never billed.
For developers
Send a prompt and a capability, or name a model. One bearer key, one small JSON body, and a full receipt on every response.
curl https://YOUR-DOMAIN/api/ainf/inference \
-H "Authorization: Bearer $AI_INFERENCE_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-1042" \
-d '{"prompt":"Summarise this ticket in one line","capability":"chat"}'Yes. Loop through your catalog against one endpoint. Your account's rate limit sets the pace, and you can adjust it in settings.
Send an Idempotency-Key per item. Usage for a key is metered once.
Give it your real attributes and ask it to use only those. Review high-traffic pages before publishing.
Each response reports its price, and the catalog shows per-token prices for every model, so you can estimate from a sample.
Start describing your catalog on the free allowance.