Documentation

Plug is the agent layer for an existing token. It does not launch tokens. Launch your token elsewhere with eligible fees routed to the Plug Agent Wallet, then bring its contract address to Plug.

Live token lookup, fee monitoring, execution, and persistent pairings are not connected.

Launch a token and configure its eligible fees to go to the Plug Agent Wallet shown below. Then connect Phantom, paste that token's contract address, choose an agent, configure it, and pair.

A pairing begins in Waiting for fees. No qualifying fees received means no agent activity.

The sequence is: launch token → route eligible fees to Plug → connect Phantom → paste CA → choose and configure agent → pair → agent waits → fees arrive → agent executes.

Configuration describes intended behavior. It is not evidence that an action has executed.

Pairing associates one existing token contract address with one agent configuration. The token should already be configured to send eligible fees to the Plug Agent Wallet.

Connect the Phantom wallet used to manage the token, then paste the contract address. The ownership signal does not block configuration, and the current interface does not write a pairing onchain.

Set the token's required, eligible fee destination to the Plug Agent Wallet when launching or configuring the token. Do this before pasting its contract address into Plug. Pairing alone does not supply an agent with funds.

Confirm the destination exactly. Only qualifying fees received at this wallet can trigger agent activity.

The Plug Agent Wallet is the Agent Operator destination that receives eligible fees before an agent can act.

Custody, signing, and execution details will be documented before live release.

Choose and configure an agent, pair it to the token, then wait for qualifying fees. Detection moves an eligible agent from Waiting toward Active execution. An operator may intentionally pause it.

Every completed action should eventually have an indexed, verifiable transaction record.

Buyback is intended to use received fees to purchase the paired token. Amounts, timing, venues, and safeguards are not implemented in this frontend.

Burn is intended to purchase the paired token and send acquired tokens to a verified burn destination. Burn mechanics and destination verification are not connected.

TWAP is intended to queue received fees and deploy them through scheduled token purchases. Schedule controls, limits, and failure handling remain to be specified.

Flywheel is intended to purchase the paired token and distribute acquired tokens through its configured strategy. Strategy execution is not connected.

Route divides eligible received fees between multiple destinations. A recipient may be a wallet or a supported X creator, and every recipient receives a configured percentage. Allocations must total exactly 100% before the configuration is valid.

For a wallet recipient, the intended behavior is to route that share to its configured address. For an X creator, the intended behavior is to attribute that share through a supported payout or claim system. X verification, wallet resolution, payouts, and claims are not connected yet.

When eligible fees arrive, a live Route agent would apply the configured split. With no eligible fees, it remains Waiting and nothing is routed. A configured route describes intent; only an executed transaction proves funds moved. Future executions should link to verifiable onchain records.

Waiting for fees means no qualifying funds have been detected. Active means qualifying funds have been received and the agent is operating. Paused means execution has been intentionally halted.

A configured or newly paired agent must not be presented as Active without detected qualifying funds.

An execution is one completed agent action, such as a purchase, burn, scheduled buy, strategy distribution, or fee route. Failed or pending attempts should not be represented as completed.

Execution indexing is not connected in this frontend.

Meaningful actions should expose their onchain transaction links, including fee receipts and agent executions. No production transaction feed is currently shown.

Production token eligibility and supported platforms have not been finalized. A contract address being accepted by the current input does not establish support.

No security guarantees are made by this frontend. Production requires documented authority boundaries, transaction validation, custody design, failure recovery, and independent review.

Always verify contract addresses, operator destinations, wallet prompts, and transaction details before signing.

Supported tokens, liquidity venues, fee sources, recipient limits, minimum balances, execution frequency, and transaction limits have not been finalized.

Does Plug launch tokens? No. Launch elsewhere and configure eligible fees to go to the Plug Agent Wallet before pasting the token contract address.

When do I connect Phantom? After the token is launched and its fee destination is set, connect the wallet used to manage it before configuring the agent.

Does pairing require SOL? The intended product does not charge SOL merely to pair through the website. Future network or execution costs are not specified.

Why is an agent waiting? No qualifying fees have reached the Plug Agent Wallet.