What is Blue Jetty?

Blue Jetty is a mobile context engine (MCE) for AI search. App teams publish an authorized app map describing capabilities, relevant experiences, current offers and preferred destinations. AI assistants can retrieve that context to explain the app and offer a relevant next step.

How Blue Jetty works →

Does Blue Jetty sell publisher data?

No. Blue Jetty does not sell—and will never sell—the data publishers provide to us. Publishing approved app context makes it accessible to crawlers and AI assistants; it is not a sale of your publisher data. Public records can be retrieved and cached by third parties, so publish only information you are comfortable making public.

Read our Privacy Policy →

How much detail do we need to share?

You decide what information to submit and how much detail to include. Describe the capabilities, relevant experiences and links that help someone understand your app. Review and approve the actual public content before publishing. Keep confidential information, proprietary content and live workflows inside your app; do not upload credentials or personal data about your end users.

Choose what to include →

What’s the difference between GEO and AMC?

GEO (Generative Engine Optimization) is the practice of improving how your brand and content are discovered, understood and represented in AI-generated answers. AMC is publisher-controlled context that tells AI what your app offers, when it is relevant, and how users should reach the right experience. Blue Jetty delivers that context through an app packet containing capabilities, relevant experiences, optional offers and preferred links. GEO is an optimization practice; AMC is app information that can support that work. They complement each other.

See how Blue Jetty works →

How does Blue Jetty complement GEO?

GEO work helps make your website's answers accessible and useful to AI search. Blue Jetty adds publisher-controlled app context: capabilities, relevant experiences, offers and preferred destinations. When an assistant retrieves that context, it has more specific information to use in an answer. You can start using Blue Jetty before or after investing in a GEO provider.

See how Blue Jetty works →

Why use an app packet if our website already has FAQs?

FAQs are useful for answering common questions. A packet connects app capabilities, experience attributes, user intents and destinations in a maintained, structured representation. You can describe those same facts on your website; Blue Jetty gives your developer an API workflow for publishing and updating them together. Keep your website and packet consistent.

Explore app mapping →

What information does an app team publish?

Start with the app's major capabilities, user intents, experiences, routing destinations and representation preferences. Include selected structured records when they help explain the fit. Large catalogs and live application data can stay in the publisher's own systems.

App mapping examples →

How does an AI system find an app's Blue Jetty packet?

Publishers can link to the app's packet from their website and llms.txt. Blue Jetty also exposes public lookup, search, pages and sitemaps. These provide accessible discovery paths; each search or AI provider determines what it retrieves and presents.

Connect your publisher website →

Where does index information come from, and how current is it?

Blue Jetty continuously runs scheduled refresh jobs against Apple App Store and Google Play listings, updating available store information and retaining source attribution and observation timestamps. Individual apps refresh on a rolling schedule; daily Apple US chart checks discover additional apps. Successful observations can update descriptions, categories, ratings and available website links. Failed checks preserve the last successful data and do not advance its successful-check timestamp. Publisher-authored capabilities, experiences and offers remain separately attributed. A store release date and a successful listing check describe different events; inspect the dates on each record.

Explore the app index →

Can AI assistants search the app index without an account?

Yes. Public lookup, search, category filters and app records require no account or API key. Assistants can combine categories, platforms and multiple description keywords to narrow a research task, then follow record links for source dates and publisher-authorized context where available. The assistant decides which apps fit its user.

Use the app index →

Can several apps use the same publisher website?

Yes. A publisher can use a shared website to help crawlers discover its app records. Each app still needs its own store identity and publisher-authorization checks. Your developer follows the shared publisher discovery instructions rather than creating a separate homepage for every app.

Read the setup guides →

Does Blue Jetty guarantee AI recommendations?

No. Blue Jetty makes authorized app information available for retrieval. Each AI or search provider decides what to fetch, use and recommend. Packet requests show access to the information, not proof that it appeared in an answer or generated an install.

Understand crawler reporting →

Do we need a mobile SDK?

No mobile SDK is required for Blue Jetty. Your developer or coding agent submits the app map through the API and adds discovery references to your website. The packet is built to further enable your existing deep-linking or attribution setup.

Read the quickstart →

What is free, and what is Blue Jetty Growth?

Blue Jetty's core offering is currently free: publisher-controlled app information, hosting and distribution, fixed MMP and native links, basic management, and all dashboard analytics within the last 30 days. Growth covers Playables, link recipes, structured offer links and lifecycle management, iOS version monitoring with priority store data freshness, and expanded analytics access. Growth Early Access includes these features at no charge. No payment is required.

Get started →

What does crawler activity tell us?

The dashboard focuses on packet requests, with total crawler requests shown separately. It includes a last-30-day chart, provider breakdowns and last-seen activity. Provider names come from self-declared User-Agent identities, not verified provider ownership. These are recorded requests, not unique people, recommendations or conversions.

Read the analytics definitions →

How do we get started?

Create an account, accept the Terms, generate an API key and give the onboarding instructions to your developer or coding agent. Prepare and validate the app map, submit it, complete publisher authorization and add the supplied packet link to the official website.

Download the onboarding instructions →

What information will be public?

Published app packets are accessible on the open web. An authorized publisher should review the actual content, its accuracy, rights and level of detail before publication. Start with a useful app map; proprietary content and live workflows can stay inside your app. Do not submit personal data about your app's end users.

Review publisher terms →

Can we update or remove our app information?

Yes. Your authorized developer can maintain app information through the API, with version checks and publication history. For account or data-deletion requests, use the contact instructions in our Privacy Policy. Removing information from Blue Jetty cannot recall copies already retrieved by third parties.

Read the maintenance guide →