# InfluTo — notes for AI coding agents

> 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).

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.

## Pick exactly one SDK for the host stack

| Platform | Language | Package | Registry | Version |
|---|---|---|---|---|
| React Native | TypeScript | `@influto/react-native-sdk` | npm | v1.7.0 |
| iOS | Swift | `github.com/influto/influto-ios` | Swift Package Manager | v1.1.1 |
| Android | Kotlin | `to.influ:android-sdk` | Maven Central | v1.1.1 |
| Flutter | Dart | `influto` | pub.dev | v1.1.1 |
| Web / Capacitor | TypeScript | `@influto/web` | npm | v1.0.1 |

- Expo / React Native → React Native SDK · SwiftUI / UIKit → iOS · Kotlin / Java → Android · Dart → Flutter.

## The 5 things to get right
1. Install the ONE matching SDK (+ peer deps).
2. `initialize()` ONCE at startup with the API key (it THROWS on failure — surface it).
3. `checkAttribution()` at launch; gate referred-user offers on `attributed`.
4. Choose ONE validation path — RevenueCat webhook OR store-direct — never both.
5. Verify with the InfluTo MCP's `influto_integration_status`, or REST:
   `GET /api/agent/apps/{id}/integration-status` with a Bearer `it_mcp_*` agent key
   (the dashboard `/api/apps/*` routes are session-only and reject API keys).

## Connect the control plane (MCP — optional but the fast path)
- One command, OAuth browser consent, no keys: `claude mcp add --transport http influto https://influ.to/mcp`
  (Codex: `codex mcp add influto --url https://influ.to/mcp`; any MCP client: HTTP server https://influ.to/mcp).
- 62 tools: provision apps + campaigns (incl. milestone bonuses + i18n), configure
  validation, VERIFY attribution, invite creators, mint join links, read canonical analytics,
  check the wallet. Full catalog: https://docs.influ.to/llms-agents.txt (live: `influto://tools`).
- CI fallback: `it_mcp_*` key from https://influ.to/dashboard/connect-agent as a Bearer header.

## Don't
- Don't hardcode the API key or put any `it_*` key / store secret in committed source or a tool argument.
- Don't set RevenueCat `influto_referral` to a boolean — it is the STRING `"true"`.

Full machine docs: https://docs.influ.to/llms.txt · Agent reference: https://docs.influ.to/llms-agents.txt · Wire contract v1.6.0: https://docs.influ.to/contract.md