Now generating video with Google Veo, Runway, and OpenAI Sora — see how it works

Getting Your API Keys

How to get an xAI (Grok) API key

Create a Grok API key in the xAI console for content, image and video generation — and why X Premium isn't the same thing.

What an xAI key powers in Landio

xAI's key drives Grok Imagine for image generation and video generation. It's the vendor to reach for when you want visuals with a looser, less corporate house style than the other image models produce.

The same key also covers Grok's text models, so one xAI key can write your captions and make your visuals — the only vendor here besides OpenAI and Google where that's true.

Before you start

You need an xAI developer account, created at console.x.ai. It's separate from your X account, though you can sign in with X.

An X Premium or Premium+ subscription — which includes Grok in the X app — does not include API credit. The API is billed separately, like every other vendor on this list.

Creating the key

xAI's console is small and the key page is easy to find.

  1. Go to console.x.ai and sign in, or create an account. You'll be placed in a default team.

  2. Open the API Keys section from the navigation.

  3. Create a new API key and name it after where you'll use it. If the console offers per-model or per-endpoint scoping, grant only image and video generation.

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

Adding credit

Add a payment method and a credit balance under the console's billing section. As with the other vendors, calls draw down a prepaid balance.

Image and video generation are priced per generation, so cost tracks how many visuals you make rather than how much you write. Budget accordingly if you're running an image-heavy content calendar.

Adding the key to Landio

Open AI Providers from the sidebar, find xAI in the vendor list, paste the key, and save. Grok Imagine then becomes selectable for image and video generation.

Keys are encrypted at rest and write-only — after saving, the page only tells you that a key exists, never what it is. That also means there's no way to read a key back out of us later, so keep the copy you saved at the vendor.

Adding a key doesn't unlock a feature; it changes who bills you for it. Every plan already includes an AI allowance, so drafting works before you do any of this. With your own key, that usage bills from xAI at their rates instead of counting against the allowance.

You can add more than one key per vendor. Landio will either spread calls across them or treat the extras as failover spares, depending on how you configure that vendor — useful when one key is a paid account and the rest are backups.

If something goes wrong

An authentication failure on a new key is nearly always a truncated copy.

A credit error means the balance is empty — top up in the console's billing section.

Frequently asked questions

Does X Premium include API access to Grok?

No. X Premium gives you Grok inside the X app. API access is a separate developer account at console.x.ai with its own prepaid balance.

What is xAI good for compared to the other image models?

Grok Imagine tends toward a looser, more playful visual style, where OpenAI and Google's image models lean cleaner and more corporate. Which one is right depends entirely on your brand — it's worth generating the same prompt on two vendors and comparing before committing.

Can I use xAI for writing captions too?

We route xAI to image and video generation. For text, pick Anthropic, OpenAI or Google on the AI Providers page — you can mix vendors freely across the three jobs.

Is it safe to paste an API key into a third-party app?

Keys are encrypted before storage and never displayed again after you save them. That said, the honest general answer is: give any third party the narrowest key you can, and keep the ability to revoke it. Where a vendor supports scoped or restricted keys, use one limited to the models Landio actually calls, and rotate it from the vendor's console if you ever stop using us.

This walkthrough was last checked against the provider's live console on . Providers redesign their dashboards without notice — if what you see doesn't match, the button names have probably moved rather than the process changing.

The provider's own documentation

All Help Docs