---
name: aeon-launch-token
description: Help a human or agent organize token details for a LAEONCH launch, ask for missing basics, and prepare a LAEONCH launch review.
---

# LAEONCH Token

Use this skill when someone wants to launch a Bankr-powered token through LAEONCH, the official Aeon launchpad.

## What This Skill Does

- Turns a plain-language project brief into token details LAEONCH can review.
- Asks only for missing basics.
- Saves a reviewed setup page for the LAEONCH team.
- Stops before live launch execution.

## What It Must Not Do

- Do not sign transactions.
- Do not launch a live token by itself.
- Do not post, DM, follow, join, or use private social accounts.
- Do not ask for or store private keys, seed phrases, OTPs, API keys, private email addresses, or private social accounts.
- Do not claim a token launched, fees were earned, or $AEON liquidity was added unless real receipts exist.

## Human Quick Start

Open `/agent` and describe the launch in one sentence:

```text
Help prepare a LAEONCH launch for Night Signal.
Symbol: NSIGNAL.
Project: https://example.invalid/night-signal.
Creator payout wallet: 0x1111111111111111111111111111111111111111.
```

Required:

- token name
- token symbol
- creator payout wallet

Optional:

- image URL
- X post URL
- website URL
- project description or project link

## Agent Workflow

1. Read this file.
2. Ask the user for token name, symbol, and creator payout wallet.
3. POST the request to `/api/agent/launch-check`.
4. If the response has missing details, ask only those questions.
5. If the response is blocked, show the blocked reason and stop.
6. If the response is ready, prepare the launch setup.
7. Save only after the user approves the details.
8. Send the user to the saved setup page.
9. Stop before any live launch action. Live execution requires separate human approval.

## Endpoint Base

Use the current app origin.

```bash
BASE_URL="${BASE_URL:-https://laeonch.ai}"
```

## Useful Files

- `/llms.txt`: short AI-readable product summary
- `/.well-known/aeon-launch.json`: machine-readable setup
- `/api/agent/manifest`: endpoint map
- `/api/agent/examples`: examples
- `/api/agent/launch-check`: check one project brief
- `/api/agent/launch-packet`: get exact prepare/save requests for one launch
- `/api/launch/prepare`: prepare the launch setup returned by the packet
- `/api/launch/record`: save only after user approval
- `/api/launch/execute`: gated live launch route for operator use only; agents should not call it
- `/api/settlement/commercial-target`: operator-only fee target math; not public sales copy
- `/api/settlement/router-plan`: optional fallback preview only if LAEONCH deliberately chooses a custom router path

## Minimal API Check

```bash
curl -sS -X POST "$BASE_URL/api/agent/launch-check" \
  -H 'Content-Type: application/json' \
  -d '{"message":"Help prepare a LAEONCH launch for Night Signal. Symbol: NSIGNAL. Project: https://example.invalid/night-signal. Creator payout wallet: 0x1111111111111111111111111111111111111111."}'
```

## Minimal Prepare Sequence

Use this only when `/api/agent/launch-check` or `/api/agent/launch-packet` says the request is ready.

```bash
curl -sS -X POST "$BASE_URL/api/agent/launch-packet" \
  -H 'Content-Type: application/json' \
  -d '{"message":"Help prepare a LAEONCH launch for Night Signal. Symbol: NSIGNAL. Project: https://example.invalid/night-signal. Creator payout wallet: 0x1111111111111111111111111111111111111111."}'
```

Then POST the returned `prepare-launch.body` to `/api/launch/prepare`.

Do not call `/api/launch/record` until the user approves the reviewed setup.

## Save Rule

Save only when all are true:

- token name is correct
- token symbol is correct
- creator payout wallet is correct
- LAEONCH settlement setup is intentional
- user approved saving the setup
- no live launch, signature, social account, or private account action was requested

## Fee Policy

Bankr has its own trading fees. LAEONCH reviews the platform setup before live launch approval.

Public agent instructions should not present creator allocation as the product promise:

- LAEONCH does not tell creators how to allocate their own proceeds.
- Exact platform fee routing belongs in launch prep and operator docs.
- Saved launch setups keep the platform settings they were created with.
- LP ownership and liquidity routing are operator-review details, not a public selling hook.

The local router rehearsal is intentionally conservative and minimal. It proves fixed recipients for one ERC20 balance, but the final production settlement can be operated by LAEONCH after claims if the Bankr fee asset shape requires manual or Safe-based routing.

Default production routing is Safe-first:

- controllable Bankr fee buckets land in the LAEONCH settlement Safe.
- backend automation prepares unsigned Safe transactions for creator payouts, operator movement, and $AEON liquidity.
- Safe owners review, sign, and execute.
- router/adapter contracts are optional fallback tooling, not the default launch path.

Pitch LAEONCH as the official Aeon launchpad powered by Bankr. Keep exact commercial terms inside launch prep and operator docs, not in outreach or marketing copy.

## Dashboard

The dashboard shows rows tied to the wallet that signed in before saving.

The dashboard is for visibility only. It does not approve a launch or transfer funds.

## Wallets and Auth

- Current auth: wallet signature.
- Later public onboarding: Privy-compatible login can be added for email, embedded wallets, and external wallets.
- Live launch execution requires separate human approval after details are confirmed.

## Mainnet Path

Before a real Bankr launch, the operator needs Bankr access, the LAEONCH fee settlement Safe, partner-fee recipient confirmation, creator payout wallet, payout handling, LAEONCH operator Safe, $AEON liquidity Safe, LP pool target, confirmed launch details, launch readiness, and receipt tracking.

The agent should stop at setup preparation. Live launch execution requires separate human approval.

## Failure Modes

- Missing details: ask only for the listed missing details.
- Blocked request: show the blocked reason and stop.
- Prepare failed: show the error plainly.
- User did not approve saving: do not save.
- Empty dashboard: the setup was not saved with that wallet session.