AI providers · xAI · updated September 2, 2026

Run your AI employees on Grok

Bring your xAI key and Coordinator's agents run on Grok — with validation strict enough to respect xAI's per-endpoint key permissions, billed by xAI directly to you at zero markup.

Free. No card. About two minutes to set up.

What you can delegate

A Grok-powered employee, not a chatbot

An agent here holds roles exactly like a person does, and its ceiling is its roles' ceiling: whatever someone with those roles could do in Coordinator, you can hand over. Grok decides how well the work gets done — not how far it reaches.

Money & books
  • Read a forwarded vendor PDF into a draft bill, validated before it touches the books
  • Watch receivables aging and draft the chase
  • Answer P&L and client-profitability questions from the live ledger
Projects & work
  • Create, file and update activities across your pipelines and boards
  • Work a queue — claim the next item, do it, hand off
  • Run the check-in round-up and keep stages honest
Time & billing
  • Log time as it works
  • Sweep unbilled hours into a draft invoice
  • Keep the time ledger clean enough to bill from
Records & forms
  • Triage form submissions into records and the right pipeline
  • Keep client records current as work happens
  • Find anything — records, contacts, history — on request
Scheduling
  • Prep today's meetings from the calendar
  • Tend booking-link intake and meeting polls
  • Keep resources and rooms straight
Chat & threads
  • Draft replies, follow-ups and summaries inside your team's threads
  • Announce what needs announcing
  • Turn a meeting thread into the follow-up tasks
The short list it can never do

Hold the Owner role. Message outside your organization before you deliberately climb the outbound ladder. Appear human in the audit trail — agent work is labeled agent work, always. Keep going after you hit pause. Everything else opens closed and is yours to grant, role by role.

The full AI-employees story — roles, fences, the outbound ladder
Why Grok

What Grok itself brings

Any provider on this site can power the delegation above. These are the reasons to pick Grok in particular.

  • Price and context in one packageGrok 4.3 runs $1.25/$2.50 per million tokens with a million-token context window — the kind of numbers that make an always-on agent's monthly bill pleasant to read.
  • The only API with live X dataFirst-party, real-time access to what's happening on X is a capability no other provider ships — if your business runs on public sentiment, launches or breaking situations, that's not replicable elsewhere.
  • Models

    Grok models your agents can use

    Prices and lineup verified September 2, 2026. In the product, the picker is fetched live from xAI on your own key — it never goes stale, and a custom model id always works if it validates.

    Grok 4.3workhorse

    $1.25/$2.50 per million tokens with a million-token context — the value pick, and where xAI's retired slugs now silently land

    Grok 4.6flagship

    $2/$6 (tiered above 200K input), 500K context — the current top of the line

    Grok Build 0.1coding

    $1/$2 — xAI's coding-agent model, in public beta

    xAI's live listlive list

    the picker fetches what your key exposes; custom model ids save if they validate — useful given xAI retired eight legacy models in May 2026

    Media through Coordinator's pipeline: images. The authority on current rates is xAI's pricing page.

    What developers say · September 2, 2026

    Grok's API, as its users describe it

    Recurring themes from public developer forums and reviews — the likes and the complaints — and how each plays out when the provider runs inside your own workspace.

    What they like
    • Raw price-performance and context: Grok 4.3 runs $1.25/$2.50 per million tokens with a million-token context window, and the flagship 4.6 holds $2/$6 — aggressive numbers for what they buy.
    • First-party real-time X data is a genuinely unique capability no other API ships.
    • Generous trial economics: signup credits, plus a monthly credits program for teams that explicitly opt into sharing their API traffic.
    What they complain about — and how it plays here

    Documentation and platform polish rate below OpenAI and Anthropic in most developer reviews, and reliability gripes (stalls, abrupt rate limiting) recur.

    Here: This is exactly why Coordinator validates xAI keys twice — models list, then a live chat ping — so a key that can't actually run agents fails at connect, not mid-workflow.

    Churn risk is structural right now: the SpaceX acquisition (February 2026), a planned endpoint migration, and old model slugs auto-redirecting to newer models.

    Here: The xAI connection accepts a base-URL override, so an endpoint move is a settings field — and the live model list plus custom-id field absorb slug redirects without a redeploy.

    The monthly free-credits program is an explicit data-sharing opt-in — your API requests go to xAI in exchange.

    Here: Same posture as our Meta contributor-tier note: an explicit trade is better than a quiet one, but read the terms before routing client documents through a data-sharing program. Paid standard traffic carries xAI's no-training-without-permission policy with 30-day encrypted retention.

    Ours to get right

    How Coordinator treats your xAI key

    The section above is xAI's report card. This one is ours — the plumbing decisions that make handing an agent your API key boring instead of brave.

    Stored encrypted, shown as last-four

    Your key is encrypted like every credential in Coordinator, and after connecting, nothing ever displays more than its last four characters.

    Proven before it's stored

    Connecting is a live round-trip to xAI — a key that doesn't actually work can't be saved, so failures happen in settings, not mid-task.

    Billed by xAI, never by us

    Zero markup, no metering, no shared key anywhere in the system. Every agent turn bills your own account at the vendor's own prices.

    Two-step validation for scoped keys

    xAI keys carry per-endpoint permissions chosen at creation — 'the key is valid' and 'the key may call chat' are different facts. Coordinator checks both (models list, then a live ping), so a key that can't actually run agents fails in settings, not mid-workflow.

    Getting started

    From no key to a working agent in a few minutes

    Create a key at console.x.ai → API Keys, and tick the chat-completions endpoint when you create it.

    First, at console.x.ai
    1. 1

      Sign in at console.x.ai. This is the xAI developer console — an X Premium or Grok consumer subscription is separate and does not include API credit.

    2. 2

      Choose the team the spend should bill to (there is a team switcher at the top; a personal team is created for you).

    3. 3

      Open API Keys and choose Create API key.

    4. 4

      When the console asks which endpoints the key may call, enable chat completions and models. This is the step people miss.

    5. 5

      Copy the key — it starts with xai- and is shown once.

    6. 6

      Under Billing, add a payment method or buy credits. A key on an unfunded team authenticates and then fails on every call.

    Then, in Coordinator — the actual screens
    Connect xAI (Grok)
    API key
    xai-········g8k2
    Validate & save

    Key verified — a live call to xAI confirmed it before anything was stored. Only the last four characters are kept visible.

    Settings → AI: pick xAI (Grok), paste the key. A live call to xAI verifies it before anything is stored.

    Default model
    Grok 4.3
    Grok 4.3workhorse
    Grok 4.6flagship
    Grok Build 0.1coding
    xAI's live listlive list

    Fetched live from your key — never a stale list. Custom model ids work too.

    Choose a default model from your key's live catalogue — or set one per agent later.

    What it costs

    Billed per token on your own xAI account. Grok 4 Fast is the cheap tier and reads a one-page bill for a fraction of a US cent; Grok 4 costs meaningfully more per document. Check the models/pricing page for current rates.

    Watch out

    Images only — a PDF bill will not extract on Grok. And if the connect test reports a permissions error on a key you just made, it is almost always the endpoint ACL in step 4 rather than the key itself.

    Images, not native PDFs

    Grok's chat path takes images, and xAI documents no native PDF input (verified September 2026). In Coordinator, PDF-heavy extraction belongs with the native-PDF providers — Claude, Gemini or OpenAI.

    Your key, your spend

    xAI bills your account directly. No markup, no shared key.

    FAQ

    Grok + Coordinator, asked directly

    Why does Coordinator validate xAI keys twice?

    xAI keys have per-endpoint permissions. Coordinator lists models and then pings chat on your key, so a key without chat access fails at connect rather than silently mid-agent-run.

    Which Grok models can agents use?

    Any chat model your key exposes — the picker fetches the live list, and custom ids save if they validate.

    Do I pay Coordinator for usage?

    No. Coordinator is free; xAI bills your key directly.

    Not sure Grok is the one?

    Swap the brain, keep the team

    Your agents aren't built out of Grok — they're built out of roles, permissions and workflows. The model behind an agent is a setting: change it in a minute and the team, the history and the fences all stay put. Every provider we support gets the same treatment, and the same honest page:

    100% free — every feature, every seat

    Put Grok on the payroll

    Coordinator is free — the only bill is the one xAI already sends you.

    Free. No card. About two minutes to set up.