Groq

Groq is an inference company. It designs Language Processing Unit (LPU) chips and runs a hosted API so applications can call language models with low latency. If you opened this page expecting a browser writing studio — a place to type a brief and export a landing page — close that mental tab. Groq is the layer underneath an app: you send a request, a model in Groq’s current catalog answers, and your code decides what to do with the text.

Official docs present an OpenAI-compatible API. The documented base URL is https://api.groq.com/openai/v1. Teams that already call another provider can often swap the host and the key, then retest. That compatibility is a convenience, not a promise that every OpenAI feature exists on Groq or that every model name matches. Read the Groq console for the routes you actually need (chat, audio, or others listed there this quarter).

The catalog is not a frozen menu. Groq lists models through the API; names that show up in last year’s blog posts may already be gone. Do not write Llama, Qwen, or any other family into a client statement of work as if Groq will host that exact checkpoint forever. Call the models endpoint, pin the identifier you tested, and schedule a quarterly check.

For WordsThatSells clients in Vientiane, Bangkok, and Ho Chi Minh City, Groq matters when a product already has a developer and a defined job: a site FAQ bot, an internal helper that comments analytics scripts, a batch rewrite tool. It does not replace a bilingual copywriter, and it does not know your hotel’s wet-season closure dates unless you supply them.

Developer trial access plus paid usage is how the directory classifies Groq (freemium). Caps, eligible models, and billing live in the account. Treat any third-party latency chart as a snapshot, not a contract.

• Hosted inference on Groq LPU hardware, sold around speed and throughput
• OpenAI-style API routes so existing SDKs can often retarget the Groq host
• A live model list you can query via the API rather than a brochure PDF
• Additional endpoints (including audio, when a model is exposed) documented in the console
• A developer trial or free tier with limits, then metered paid usage — confirm both in-account

Connectors, agent recipes, and playground extras appear in Groq’s docs at different times. Validate each one in your project before you put it on a client roadmap. Product surfaces move.

Start with a landing-page FAQ bot, not a vague “content engine.” An English-language tour operator in Bangkok or a riverside hotel near Vientiane often already has a services page with ten questions sales hears every week: transfer time from the airport, deposit rules, whether the pool is adults-only. Put those answers in a small approved store (even a JSON file the marketer can edit). The Groq call should retrieve or stay close to that store. Latency helps the chat feel alive on a phone over hotel Wi-Fi. It does not create truth. If you skip the store, the bot will invent a spa package you do not sell.

A second practical job is an analytics-script helper. Growth teams in Ho Chi Minh City and English-speaking operators who share one GA4 or Mixpanel property often argue about event names. A tiny internal tool can paste a draft snippet — say a WhatsApp click or a booking-form submit — and ask the model to propose a consistent name, a comment block, and a list of properties the developer should not forget (currency, language, city). A human still pastes the snippet. Groq is only speeding the first draft of the comment and the naming conversation. Do not let the model invent tracking IDs that never get implemented.

Before you put Thai or Lao strings into any of those tools, run a tokenization and rendering check. Thai has no spaces between words; Lao has its own vowel placement. A model that streams quickly can still split a brand name, drop a tone mark, or invent a Bangkok district. Build a short gold set: five product names, five street names, five sentences your receptionist actually says. Send them through the model you pinned. If the output breaks glyphs or “corrects” a Lao hotel name into Thai, change models or keep a native reviewer in the publish path. Speed does not fix a weak tokenizer.

English-language operators in the region still sit next to LINE Official Accounts and Facebook inboxes. Groq does not replace those channels. It can sit behind a web widget on an English landing page while the Thai-speaking team keeps answering LINE by hand. Do not promise a unified inbox. If the client’s buyers live in LINE, a fast English FAQ on the website is a support, not a substitute.

Rate limits and model deprecations are operational facts, not footnotes. When a campaign landing page suddenly gets ad traffic, a generous playground experiment can trip a cap. Document the exact model identifier in the repository — not the word Groq. Re-list models from the API when you reopen a project after Songkran or Tet, the same way you would re-check a payment gateway. Blog roundups go stale.

If the team has no developer, Groq is the wrong first tab. A marketer who needs a headline today should use a consumer chat product and a human editor. Come back to Groq when you are repeating the same prompt inside code: the FAQ bot, the snippet helper, a nightly rewrite of product titles. Until that loop exists, you are paying for an API you will not operate.

Keep keys on a server. A static marketing site should never embed a Groq token in the browser. Forms that collect guest names or passport hints in Laos or Thailand belong under your published privacy policy; do not dump identity documents into a prompt. WordsThatSells treats Groq as infrastructure behind a client build, not as a field the client types into during a workshop.

A useful pairing session: the marketer brings the approved FAQ and the gold-language set; the developer brings the existing OpenAI-shaped client. You retarget the host, time the first useful token on the same prompt, and decide whether the latency change is worth another vendor in the stack. If the demo feels the same, stay with the provider the team already bills. Groq’s value is felt in the product, not in a slide that says ultra-fast.

This directory lists Groq as freemium: a developer trial or free allowance, then paid usage. We do not copy token prices here because the grid moves when models enter or leave the catalog. Confirm caps, included models, and invoices on groq.com and in the console.