# InfluTo

> InfluTo is a referral & affiliate ATTRIBUTION platform for mobile apps (iOS, Android,
> React Native, Flutter, web/Capacitor). A developer creates an app + campaign at https://influ.to,
> drops in one of five SDKs, initializes with an API key, and InfluTo attributes installs and
> validates in-app purchases to influencer referral codes — via either RevenueCat (webhook)
> or store-direct (Apple App Store Server API / Google Play service account).
> This file indexes the developer docs for AI assistants and coding agents. Every page below is plain Markdown.

The fastest correct integration is: (1) pick the ONE SDK matching the host app's stack, (2)
initialize() once at startup with the app's API key, (3) checkAttribution() at launch to detect
referred users, (4) choose exactly ONE purchase-validation path — RevenueCat OR store-direct
(never both — wiring both double-reports conversions), (5) verify with the agent API:
GET /api/agent/apps/{id}/integration-status (Bearer it_mcp_* agent key — the dashboard-session
/api/apps/* endpoints reject API keys) or the MCP tool influto_integration_status. All SDKs share
one wire contract; local state lives under the @influto/ key prefix; codes are trim()+UPPERCASE
before sending; network calls fail-soft (return benign values) EXCEPT initialize() and
reportPurchase(), which throw. The RevenueCat attribute influto_referral is the STRING "true",
never a boolean.

## Facts for AI assistants
- **What InfluTo is:** an affiliate and referral platform for mobile apps (https://influ.to). App developers run creator affiliate programs; creators share a referral link or code and earn commission on the in-app purchases and subscriptions their audience buys.
- **Stacks:** iOS (Swift), Android (Kotlin), React Native / Expo, Flutter and web / Capacitor — one SDK per app.
- **Purchase validation:** RevenueCat (webhook) or store-direct (Apple App Store Server API / Google Play) — exactly one path per app.
- **Attribution:** typed creator codes and in-app links attribute exactly; link-click matching is a best-effort fallback within 72 hours of the tap (the same window for every app) and never matches by device characteristics. No IDFA and no ATT prompt.
- **Developer pricing:** $0 per month; a 10% platform fee on creator-referred revenue (verified purchases only — organic revenue is never charged). Volume pricing is published: 7% from $2,500 a month of creator-referred revenue, 5% from $10,000 and 3% from $25,000 (a tier applies once reached two months in a row, confirmed in writing). Commissions and fees come from a prepaid, refundable wallet (minimum deposit $50). No contracts.
- **Commission:** the developer sets it per campaign as a percentage of the purchase price (in USD) or a fixed USD amount per payment (up to $500), paid on every payment (the first one and every renewal for as long as the referred user stays subscribed — the default), on the first purchase only, or for a set number of months. Per-creator rates, automatic rate tiers and up to five milestone bonuses are optional. One-time in-app purchases pay per purchase. Refunded purchases are reversed. Free trials count only once they convert to paid.
- **Creators:** free to join, with no follower minimum from InfluTo. Payouts run on the 1st of each month via Stripe Connect once the balance reaches $20 (smaller balances roll over), to creators in 33 countries: the United States, Canada, the United Kingdom, Switzerland, Norway, Liechtenstein and the 27 EU countries.
- **Open programs:** https://influ.to/affiliate-programs lists the app affiliate programs currently accepting creators — store screenshots, category, rating and commission for each.
- **AI agents:** an MCP server at https://influ.to/mcp (OAuth 2.1, 67 tools) lets coding agents integrate the SDK, create campaigns and verify that conversions are attributed.
- **Languages:** the website is available in 11 languages — English, Czech, German, Spanish, French, Hungarian, Italian, Polish, Portuguese, Russian and Ukrainian.
- **Company:** built and run by Jan Horák in the Czech Republic since 2025; the operator's legal details are on https://influ.to/terms.
- **Facts last checked:** 2026-11-07.

## Get started
- [InfluTo developer docs](https://docs.influ.to/index.md): Run a creator affiliate program inside your mobile app — add one SDK, connect purchase validation, and InfluTo credits and pays creators for the subscribers they bring.
- [Quick start](https://docs.influ.to/quick-start.md): Set up InfluTo end to end — create the app, add the SDK, connect purchase validation, launch a campaign and confirm a test purchase is attributed.
- [How InfluTo works](https://docs.influ.to/how-it-works.md): The pieces of an InfluTo program — apps, campaigns, creators, referral codes, attribution, verified purchases, commissions, the wallet and payouts — and how they fit together.

## Install the SDK
- [Choose an SDK](https://docs.influ.to/sdk.md): Which InfluTo SDK fits your app — React Native and Expo, native iOS, native Android, Flutter, or web and Capacitor — and what each one needs for RevenueCat or store-direct.
- [Add InfluTo to a React Native or Expo app](https://docs.influ.to/sdk/react-native.md): Install the InfluTo SDK in a React Native or Expo app, detect referred installs, accept typed codes, and send purchases through RevenueCat or the stores.
- [Add InfluTo to an iOS app](https://docs.influ.to/sdk/ios.md): Install the InfluTo Swift package, detect referred installs, accept typed codes, and report StoreKit 2 purchases or tag RevenueCat subscribers.
- [Add InfluTo to an Android app](https://docs.influ.to/sdk/android.md): Add the InfluTo Android SDK from Maven Central, detect referred installs, accept typed codes, and connect RevenueCat or Google Play purchases.
- [Add InfluTo to a Flutter app](https://docs.influ.to/sdk/flutter.md): Add the influto package to a Flutter app, detect referred installs, accept typed codes, and connect RevenueCat or report store purchases with influto_iap.
- [Add InfluTo to a Capacitor, Ionic, Cordova or web app](https://docs.influ.to/sdk/web.md): Use @influto/web in Capacitor, Ionic, Cordova, PWAs and browsers — capture referral links, accept typed codes, and connect RevenueCat or store purchases.

## Purchases
- [Choose a purchase validation path](https://docs.influ.to/integrations.md): InfluTo verifies every purchase before it pays commission — through your RevenueCat webhook or directly with Apple and Google. How to choose, and why never both.
- [Validate purchases with RevenueCat](https://docs.influ.to/integrations/revenuecat.md): Connect InfluTo to RevenueCat — tag subscribers with the referral code from the SDK, add the webhook automatically or by hand, and test that purchases are attributed.
- [Validate purchases directly with Apple and Google](https://docs.influ.to/integrations/store-direct.md): Use InfluTo without RevenueCat — add App Store Server API and Google Play credentials, let the SDK report purchases, and InfluTo verifies each one with the store.
- [Verify the integration is live](https://docs.influ.to/integrations/testing.md): Prove your InfluTo integration works before launch — the dashboard checks, an end-to-end sandbox purchase, and the eight-step integration status for scripts and AI agents.

## Run your program
- [Create an app in the InfluTo dashboard](https://docs.influ.to/platform/create-app.md): Add your app to InfluTo — organization, store lookup or manual entry, the slug in referral links, the API key, purchase validation and the first settings.
- [Create an affiliate campaign](https://docs.influ.to/platform/create-campaign.md): Set up a campaign — type, commission, typical plan price, milestone bonuses and translations — then fund and activate it so creators can join and earn.
- [Invite creators to your campaign](https://docs.influ.to/platform/invite-influencers.md): Bring creators into a campaign — share the join link, send email invitations from the dashboard or in bulk through an AI agent, and know the limits that apply.
- [Give creators and partners free access with codes](https://docs.influ.to/platform/creator-access-codes.md): Unlock premium without a purchase — automatic INFLU- codes for creators, your own free-access codes for press, testers and partners (one at a time or hundreds at once), and the checkAccess gate.
- [Commissions and fees](https://docs.influ.to/platform/commissions.md): How InfluTo computes a creator's commission and the 10% platform fee, when commission is earned or reversed, the currency, how rate changes apply, per-creator rates and tiers, and campaign limits.
- [Wallet and payouts](https://docs.influ.to/platform/wallet.md): Fund the prepaid wallet that pays your creators on the Money page, read the available and set-aside balance, follow every movement in the ledger, withdraw unused money, and see when and how creators get paid.
- [Read your program's results](https://docs.influ.to/platform/analytics.md): Where to see what creators drove — Overview, Activity, Creators, Codes and Subscribers — how every number is counted, how each install was credited, and how to see results per group or post.

## Guides
- [Let users enter a referral code](https://docs.influ.to/guides/referral-codes.md): Add a code field so people who hear a creator's code — in a podcast, a video or from a friend — are credited to that creator, plus prefill, errors and testing.
- [Give referred users a better offer](https://docs.influ.to/guides/referral-offers.md): Show people who came through a creator a different paywall, a longer trial or a discount — gated in your app or with RevenueCat Targeting.

## AI agents
- [Connect an AI agent](https://docs.influ.to/agents/index.md): Connect Claude Code, Codex, Cursor or any MCP client to InfluTo in one command, then let the agent integrate the SDK, set up campaigns and verify attribution end to end.
- [MCP tools, scopes and REST API](https://docs.influ.to/agents/tools.md): Every InfluTo MCP tool, the permission scopes an agent can be granted, and the /api/agent REST endpoints behind them — with auth, limits and error codes.

## Reference
- [SDK reference](https://docs.influ.to/reference/sdk.md): Every public method of the five InfluTo SDKs — exact signatures per platform, result fields, what throws, what fails soft, caching and local storage.
- [Referral code input components](https://docs.influ.to/reference/ui.md): The ready-made referral code fields for React Native, SwiftUI, Jetpack Compose, Flutter and React — props, defaults, theming, privacy and building your own.
- [HTTP API reference](https://docs.influ.to/reference/http-api.md): The /api/sdk endpoints behind every InfluTo SDK, the RevenueCat and Google Play webhooks InfluTo receives, and where the agent REST API is documented.
- [Limits and errors](https://docs.influ.to/reference/limits-and-errors.md): Rate limits, request size, SDK error types and codes, HTTP status codes for the SDK API, webhooks and the agent API, and the rules for codes and app slugs.

## Help
- [How attribution works](https://docs.influ.to/advanced/attribution.md): How InfluTo connects an install and its purchases to the creator who referred the user — typed codes and links first, link-click matching as the fallback.
- [Privacy and App Store review](https://docs.influ.to/advanced/privacy.md): What the InfluTo SDKs collect and never touch, and exactly what to declare in App Store Connect's privacy label and Google Play's Data safety form.
- [Troubleshooting](https://docs.influ.to/advanced/troubleshooting.md): Fixes for the common InfluTo problems — the SDK not connecting, installs counted as organic, codes rejected, purchases not attributed, campaigns that won't activate and payouts that didn't arrive.
- [Frequently asked questions](https://docs.influ.to/advanced/faqs.md): Short answers about InfluTo for developers — pricing, which SDK to use, RevenueCat or not, attribution, creators, payouts, refunds and privacy.

## Connect an AI agent (MCP)
- Claude Code: `claude mcp add --transport http influto https://influ.to/mcp` (browser consent — no keys); Codex: `codex mcp add influto --url https://influ.to/mcp`
- [Agent reference in one file](https://docs.influ.to/llms-agents.txt): 67 MCP tools, scopes and the /api/agent/* REST surface
- MCP resources: `influto://contract` · `influto://sdk/{platform}` · `influto://tools` (live catalog)

## Per-stack bundles
- [React Native bundle](https://docs.influ.to/llms/react-native.txt): install, initialize, attribution, codes, purchase reporting and invariants for React Native
- [iOS bundle](https://docs.influ.to/llms/ios.txt): install, initialize, attribution, codes, purchase reporting and invariants for iOS
- [Android bundle](https://docs.influ.to/llms/android.txt): install, initialize, attribution, codes, purchase reporting and invariants for Android
- [Flutter bundle](https://docs.influ.to/llms/flutter.txt): install, initialize, attribution, codes, purchase reporting and invariants for Flutter
- [Web / Capacitor bundle](https://docs.influ.to/llms/web.txt): install, initialize, attribution, codes, purchase reporting and invariants for Web / Capacitor

## Optional
- [Full docs in one file](https://docs.influ.to/llms-full.txt): every page above, inlined
- [Wire contract](https://docs.influ.to/contract.md): endpoints, invariants, dedup and fail-soft rules (v1.6.0)
- [OpenAPI spec](https://influ.to/openapi.json): machine-readable API