setgreet.com valid

Setgreet

Setgreet is the AI growth team for your mobile app. It designs, ships, and measures the native flows that grow your app (onboarding, paywalls, surveys, feature announcements, retention nudges) and publishes them into live iOS, Android, React Native, and Flutter apps with no code and no App Store release. Screens render as real native components, never a WebView. Pricing is based on Monthly Active Users, never a percentage of your revenue, and Setgreet works alongside the billing and subscription

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T04:55:25.437Z. Cached copy · Source on setgreet.com

# Setgreet

> Setgreet is the AI growth team for your mobile app. It designs, ships, and measures the native flows that grow your app (onboarding, paywalls, surveys, feature announcements, retention nudges) and publishes them into live iOS, Android, React Native, and Flutter apps with no code and no App Store release. Screens render as real native components, never a WebView. Pricing is based on Monthly Active Users, never a percentage of your revenue, and Setgreet works alongside the billing and subscription stack you already run rather than replacing it.

## How it works

- Describe an onboarding flow, paywall, or survey in plain language and the AI drafts a real, editable flow in your app's own theme.
- Refine it in a visual editor or by chat, target it with user attributes and events, A/B test it, then publish. Every device with the SDK updates within seconds.
- An AI agent can drive the whole loop (compose, publish, experiment, read analytics, iterate) through the Model Context Protocol server at mcp.setgreet.com.

## Key pages

- [Product](https://www.setgreet.com/product): what Setgreet does across activation, conversion, and retention.
- [Pricing](https://www.setgreet.com/pricing): MAU-based pricing, never a percentage of your revenue.
- [MCP server](https://www.setgreet.com/mcp): let an AI agent compose, publish, and iterate on flows via mcp.setgreet.com.
- [Use Setgreet with AI agents](https://www.setgreet.com/docs/mcp): connect an MCP client (Claude, Cursor, Codex), with per-client install and recipes.
- [Agent instructions (AGENTS.md)](https://www.setgreet.com/AGENTS.md): drop-in block teaching a coding agent to install the SDK and use the MCP correctly.
- [Free onboarding audit](https://www.setgreet.com/free-onboarding-audit): submit an iOS or Android app for a free onboarding teardown; one app is audited every week, and $49 one-time takes the next open slot.
- [Use cases](https://www.setgreet.com/use-cases): onboarding, surveys, announcements, upgrade prompts, permissions, campaigns.
- [FAQ](https://www.setgreet.com/faq): common questions about the product, SDKs, and billing.
- [Changelog](https://www.setgreet.com/changelog): what shipped recently.

## Blog

- [How many onboarding screens should your app have?](https://www.setgreet.com/blog/how-many-onboarding-screens): The standard advice says 3 to 5 screens. Public data from 910 top iOS subscription apps suggests the real median is about double that. Here is what onboarding length actually looks like, category by category. ([Markdown](https://www.setgreet.com/llms.mdx/blog/how-many-onboarding-screens))
- [Mobile app onboarding best practices that hold up in 2026](https://www.setgreet.com/blog/mobile-app-onboarding-best-practices): Most onboarding advice is a list of platitudes. These are the practices that survive contact with real drop-off data: personalize early, sequence permissions, place the paywall deliberately, and iterate without app releases. ([Markdown](https://www.setgr
…

Machine-readable: GET /v1/resolve?q=setgreet.com · GET /v1/domain/setgreet.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for setgreet.com:
1. POST https://agentwebmap.com/v1/sites/setgreet.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://setgreet.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/setgreet.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/setgreet.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.