Know what a route proves.

From a person to a destination

Choose an exact X account and confirm the person. FeeTo generates a unique Solana fee destination. The recipient does not need to supply a wallet address or register before you start.

Set that destination as the 100% creator-fee recipient on Pump.fun. Then paste the token CA once. FeeTo verifies the canonical fee configuration before publishing the route. A fresh destination remains private during setup.

The routed recipient allocation is 100%. FeeTo takes 0% of those creator fees. Solana network costs and third-party costs can still apply.

Identity is the anchor

Handles can change. FeeTo uses the provider’s stable account identifier for matching, while handles and names remain display information. An exact public lookup identifies the account; only recipient authentication verifies account control.

An account holder’s identity verification does not endorse a token. It also does not establish independent wallet signing control. Those facts are kept separate in the product.

What activation checks

The sender provides the token CA only after setting up Pump.fun. Verification checks the intended mint, canonical supported Pump configuration, finalized state, intended destination, sole shareholder and 100% allocation. It records the configuration evidence and verification time.

A route cannot change its bound mint. A private capability authorizes the sender’s setup intent. It is not a wallet key, and it never belongs in a public link.

The proof describes the checked configuration. It does not establish token safety or prevent third-party programs and external systems from changing.

Read the number, and its label

Tracked fees received are observed finalized Pump distributions. They are history, not a wallet balance. The available RPC history can be incomplete, so FeeTo says Tracked rather than claiming a complete All Time total.

Destination balance is observed SOL at the destination. It may include other transfers and can fall after funds leave. Unknown or unavailable balances are not shown as zero.

Claimable or unclaimed fees need a separate source. That amount is not inferred from balance. Market cap is a secondary external token-market observation, with its own availability and observation time.

Recent activity represents indexed finalized events, not a promise of instant delivery. Previously recorded data remains labeled with its time when updates fail or become stale.

Identity verification and wallet control

Recipient login matches the stable social identity to eligible destinations. Privy provides the wallet infrastructure. The live ownership transition and signing permissions must be independently demonstrated before FeeTo offers signing or withdrawal actions.

The current Access experience can display verified account routes and destination observations when configured. Funds actions remain gated where the ownership proof is unresolved. FeeTo does not currently make a non-custodial or exclusive recipient-control claim.

What becomes public

Public active routes show the token, named recipient, destination, route evidence and allowed financial observations. Explore, creator and token pages group eligible public routes. They do not reveal private pending setups or private provider links.

Someone can route fees to a person who has not joined FeeTo. A route never implies that the person launched, approved or endorsed the token. Public creator totals concern their public FeeTo scope, not their entire income or wealth.

What sign-in shares

Native X authentication is handled through Privy. FeeTo verifies the token server-side and matches the stable social account. FeeTo never asks for or stores your X password.

FeeTo stores minimal identity snapshots and route records. Public responses omit raw provider subjects, Privy IDs, session internals and private capabilities. There is no frontend advertising or analytics tracker in this implementation.

Exact production processors, deployment logging and retention details require operator confirmation. See Privacy for the current implementation and remaining publication inputs.

Current support

The public product is X-first, on Solana, using supported Pump.fun creator-fee configurations. Live functions are enabled only after their credentials and required ownership proofs are configured. An unavailable action does not create a route or transfer funds.

TikTok and Instagram adapters are gated separately. They are not shown as available product choices. No automatic first-transfer token binding, multi-chain routing or automatic distribution is offered.