X Developer Exhibit: how to get your app listed

#Quick answer

The X Developer Exhibit is X's public gallery of products built on the X API, at developer.x.com/exhibit. You submit from the Developer Console, pick App or Agent Use Case, and Grok reviews the submission in about a minute. Nothing publishes until you paste a launch post URL from the same X account you are signed in as. Edits and republishes go back through review every time.

Last updated: October 2026

X rebuilt the Exhibit on 11 October 2026, and almost everything written about it describes the version from July. The gap matters, because the current flow has two requirements the launch announcement never mentioned and one listing type that did not exist. Here is what submitting actually involves now, pulled from X's own documentation rather than the announcement thread.

#What the Exhibit is, and what changed in October

X (formerly Twitter) has pitched this consistently since it first floated the idea. On 17 June 2026 the Developer Platform team opened an early-access interest form, saying it wanted "well-built, creative, and useful applications that demonstrate strong usage of the X API." Two weeks later, on 1 July 2026, the team launched it properly and described it as "a curated app store style showcase specifically for the X ecosystem, but without the gatekeeping of a traditional app store."

The 11 October rebuild is not a reskin. X describes it as rebuilt from the ground up, and the practical changes are these:

• Agent use cases are now first-class listings. You can submit a Grok Bot template or an agent skill file as the product itself.
• The listing format carries more. Up to five screenshots, an optional video URL, a custom logo, and four separate prose fields instead of one description.
• The gallery has shelves. Official partners, Public Utility apps and agentic implementations sit in distinct sections rather than one flat list.

That last point is the real reason to pay attention to how you fill the form in. A flat directory rewards being listed. A sectioned one rewards being listed in the right place.

#The two listing types, and why one is a cheap door

You choose the type first, and the type locks after your first submit. There is no changing it later, so this is the one decision worth slowing down on.

That second row is the interesting one. If you have built a Grok Bot template or an agent skill that does something useful with X, you can get an official X listing with no product website, no landing page and no company behind it. For anyone who has shipped a bot and never shipped a marketing site, that is the lowest-effort route to a page on an X-owned domain that currently exists.

It also connects to money. On 27 September 2026 X began an invitation-only Grok Bot Template Rewards pilot, paying creators through X Money when other people use their templates. X reserves discretion over amounts, and a creator's own usage of their own template does not count. The Exhibit is where those templates get found, so a listing is upstream of the rewards program rather than separate from it. If you are new to how Grok sits inside the platform, what Grok does on X covers the user-facing side.

Then pick one of six categories: Bots and Automation, Analytics and Insights, Content and Scheduling, Community and Moderation, Developer Tools, or Data and Research.

#What review actually checks

Grok runs the review in the background. The Console tells you to come back in about a minute, and that is roughly how long it takes.

What it is checking is more specific than quality. Per X's documentation, the name, logo and screenshots are checked against the X account you are signed in as. The developer name and handle on the listing come from that account and you cannot type them in. So the failure modes are mostly identity ones:

• The default Console app name (your account ID plus username) or the default app icon. Pick a product name and upload your own icon.
• Someone else's logo. The X logo, the Grok mark and other companies' marks are out unless the signed-in account is that brand. X spells out the exception: @X, @xai, @XDevelopers and @grok may use those marks. Saying your product is "built on the X API" does not authorize them.
• A display name of "X" on a personal account, which X calls impersonation outright.
• Not a real X API product. Unrelated websites, link dumps, empty wrappers and placeholder pages get rejected. The X Developer Guidelines are the governing document for what a legitimate API product is.
• Screenshots that are not of your product. A stock page or an empty frame fails.
• A second listing for an app that already has one.

Four fields have a stated length bar rather than a format one. Description, "how it was built" and "who it is for" all need a real paragraph, not a slogan. X asks explicitly for more than a sentence on each. The tagline is the one place a single line is fine.

#The launch post requirement

This is the step that catches people, and it appears nowhere in the July announcement.

When review passes, the Console asks for the link to the X post that launches the app. It has to be a status URL in the form https://x.com/you/status/... from the same account you are signed in as. A post from any other account is rejected. Only after the link is accepted can you publish, and the listing then goes live at developer.x.com/exhibit/your-slug.

Two consequences follow. Write the launch post before you start the submission, not after, or you will stall at the last step with an approved listing you cannot publish. And if you planned to submit from a company account while announcing from your personal one, that does not work. Pick one account and keep both the app and the post on it.

One more rule the announcement never mentions: editing a live listing sends it back through review. So does unpublishing and republishing. It does not go live again on the old approval. The July framing of "submit, verify, you're live, no long wait times" was accurate for a first pass and is wrong about the steady state. Treat the listing as a reviewed artifact, not a profile you tweak casually.

Unpublish and delete are separate actions, which is a sensible design. Unpublish takes the app off the gallery and keeps the listing in the Console so you can edit and republish. Delete removes it.

#Public Utility: credits, not a badge

Once a listing is live, you can request Public Utility status from it. X describes it as a credit program for public-good work on the X API. The request goes to the X Dev Platform team, they decide whether the app belongs on that shelf, and until they approve it the app stays an ordinary listing.

X pre-empts the two obvious misreadings on the same page: it is not a way to skip review, and you cannot mark your own listing as a utility. The honest read is that this is discretionary and the amount is not published, so plan your X API budget on the assumption you are paying full price. If the credits land, treat them as a bonus. The free-credit incentives X added on 2 October 2026, worth up to $70 for a new account, are the predictable ones.

#What a listing is actually worth

Be realistic. The Exhibit is a gallery on a developer subdomain, not an app store with install intent behind it. X's own pitch is discoverability, traffic and credibility, and of those three the third is the one you can count on: a listing on an X-owned domain is a verification signal you can point at.

The honest case for submitting is cheap optionality. The submission takes under an hour if your screenshots exist, it costs nothing, the backlink and brand presence are real, and the Public Utility and Grok Bot reward paths both run through it. The case against is that X's developer relations have swung hard before. API prices rose sharply in 2024 and shut down a generation of third-party apps, access to AI developers got restricted, and the platform moved to pay-per-use metering in February 2026. A gallery is a cheap way to court builders back. It is not a commitment.

Which is the useful frame: list the app because the listing is nearly free, not because the Exhibit is a distribution channel.

#Before you submit

A short checklist, in the order the Console will ask:

1. Decide App or Agent Use Case. It locks. Agent use case if your deliverable is a Grok Bot template or a SKILL.md.
2. Get an API key sorted if you have not. Getting an X API key now ends at a billing screen, and the app has to belong to the account you sign in with.
3. Rename the Console app and upload a real icon. The defaults are a documented rejection reason.
4. Write the three prose fields properly. What it is, how it uses the X API, who it is for. A paragraph each.
5. Take at least one honest screenshot of the product. You can add five.
6. Draft the launch post and keep the status URL ready.
7. Submit, wait about a minute, then publish with that link.

If your app reaches X through an AI client rather than your own HTTP code, the X MCP servers are worth wiring up first, since they make the "how it was built" field easy to write honestly. And if your product posts on behalf of users, check whether it needs the automated account label before you put it in a public gallery, because a reviewed listing is exactly the wrong place to be caught without one.

One last distinction, because the two things get confused. The Exhibit is for products built on the sanctioned API. Browser-based tools are a different category: X-Autopilot drives real Chrome on your own Mac with your existing session and no API key, which is a grey area under X's automation rules rather than an approved path, and we do not claim otherwise. Running locally on your own connection is a smaller detection surface than a cloud tool posting through a shared IP pool, which is reduced exposure rather than none. If an official listing is what you want, build on the API. That is the door the Exhibit opens.