FORGE is an AI-agent launchpad where a creator can define an autonomous agent, attach a token launch to that agent, deploy through a supported launch rail and operate the agent through a public interface. The initial launch rail is PONS on Robinhood Chain. Pump.fun and flap.sh are deliberately hidden behind “Coming Soon” adapters in MVP.
FORGE is not just a token launcher with AI branding. The product object is the Agent. Each Agent has identity, capabilities, knowledge configuration, safety policy, a live chat surface, an associated token, an on-chain launch, creator-fee routing, live market/activity data and a public profile.
The platform token, $FORGE, is the ecosystem asset used for launch/fee benefits, premium infrastructure, compute credits, boosting and later governance. Utility should be linked to real product usage rather than presented as guaranteed financial return.
2. Product goals
MVP goals
Allow the team to launch $FORGE from a CLI before the public creator UI is enabled, while ensuring the resulting launch is automatically indexed and visible in FORGE.
Allow a normal creator to configure an Agent from a template, create an isolated Grok-backed runtime, deploy a token through PONS and receive a public Agent page.
Index PONS launches/trades directly from Robinhood Chain in near real time.
Stream token/market/agent activity to clients using a native WebSocket service, with no polling required for normal operation.
Agent/token TradingView charts and buy/sell swap routing via Mobula Enterprise (server-proxied API key; see Market data).
Route creator fee proceeds through an agent-specific fee vault. Defaults: 15% of gross to platform (untouched), then 1% of the beneficiary pool to the permissionless claim caller, rest to beneficiary. Tip never reduces platform. FORGE keeper only auto-claims when that tip covers gas + profit (Fee keeper).
Give every Agent a live chat interface with strong system prompts, capability boundaries, per-agent memory and server-side tool gating.
Run production reliably on one DigitalOcean Linux host with independent PM2 services, automatic restart, startup persistence, log rotation, RPC failover and health monitoring.
Giving an LLM a private key and letting it freely sign transactions.
Custodial user wallets.
A platform-managed trading strategy on behalf of every agent.
Building a replacement bonding curve for PONS.
3. Product principles
On-chain truth first. Launch and market state comes from the chain. Database state can be rebuilt from events.
Agent isolation first. Each agent can access only explicitly granted tools and data. It has no direct database, filesystem, infrastructure wallet or shell access.
Transparent economics. Every fee split and boost must be visible in the UI. “Boosted” results are labeled. Organic discovery remains available.
Fast market UX. Launches and trades should appear in the UI within approximately one block plus indexing latency. No manual refresh.
Adapter architecture. PONS is the first LaunchAdapter, not hard-wired business logic. Future Solana/BSC launchpads plug into the same internal interface.
4. Personas
Creator
Wants to turn an idea/persona/strategy into a live AI agent and token without assembling contracts, infrastructure and AI services manually.
User / trader
Wants to discover agents, inspect live token state, interact with the agent and trade through the supported launch rail.
Agent operator
Wants access to fees, compute credits, premium tools and a predictable runtime while keeping control of the downstream wallet/action logic.
FORGE admin
Needs launch moderation controls, service health, fee visibility, feature flags, featured inventory, abuse controls, indexer repair tools and audit logs.
5. Core user journeys
Journey A — launch $FORGE before public launch UI
Operator fills .env with Robinhood Chain RPCs, PONS addresses/config and the deployer key.
pnpm cli:launch-forge reads current PONS launch configuration and checks canLaunch(deployer).
- name - token ticker - short description - full personality/backstory - avatar - public links - optional Generate with Grok to autofill identity + type-matched profile image from the selected template
Configure capabilities. The template provides defaults; creator can reduce capabilities but cannot grant unsupported privileged access.
Configure knowledge sources and optional public URLs/data integrations.
Configure fee destination:
- normal wallet, or - approved external action contract/wallet owned by Agent operator. - After launch, vault owner (deploying creator) can update beneficiary on-chain to migrate wallets without a new vault.
Preview Agent and token.
User presses Compute addresses / Simulate (no wallet popup). Backend returns vault ECA, token ECA, curve ECA, pinned salt, and live PONS economics.
UI shows those ECAs and fee routing (vault as creator fee recipient; 15% platform of gross, 1% tip from beneficiary pool).
User presses Launch and signs one transaction to ForgeLaunchRouter, which deploys the AgentFeeVault and calls PONS launch (optional opening buy) atomically.
Indexer confirms vault + launch from that tx and maps token/curve to the draft Agent.
Agent status changes DRAFT -> LAUNCHING -> LIVE.
Public Agent page opens with live chat, Mobula-powered TradingView chart, buy/sell (Mobula swap quote → wallet sign), launch progress and activity stream.
Journey C — chat with a live Agent
User opens Agent page and creates a session.
Server loads the agent's versioned system prompt and allowed tools.
User message is screened for abuse/rate limits and sent to the xAI Responses API.
Tool calls are validated against per-agent policy.
Read-only tools can execute automatically. Any sensitive transaction action must flow through the approved execution policy and never expose a raw key to the model.
Response streams to the browser.
Usage, latency, model, token count and tool calls are logged without leaking secrets.
Journey D — creator receives fees
PONS credits creator proceeds to its fee escrow for the AgentFeeVault recipient.
Anyone (public bot, creator, or FORGE keeper) calls claimAndSplit*.
Vault claims from the PONS escrow.
Current platformFeeBps (default 15% of gross) → FORGE platform recipient (full cut; tip does not reduce it).
Current callerTipBps (default 1% of post-platform beneficiary pool) → msg.sender.
Rest of beneficiary pool → agent beneficiary/action target.
FORGE keeper only submits when estimated tip ≥ gas + min profit; public callers may claim smaller balances anytime.
Split event (including caller tip) is indexed on the Agent transparency panel.
FORGE does not decide what the beneficiary subsequently does with funds.
6. Information architecture
Public
/ Home
/explore All live agents/tokens
/templates Agent templates
/agent/[slug] Agent detail/chat/token market page
/token/[address] canonical token route, redirects or renders Agent if mapped
/leaderboard
/docs — full built-in markdown docs site (see DOCS_SITE.md), including agent launch playbooks
/docs/agents — ops index for coding/runtime agents
/about
Authenticated creator
/launch
/my-agents
/my-agents/[id]/settings
/portfolio
/billing (post-MVP can start as read-only compute usage)
Admin
/admin
/admin/agents
/admin/boosts
/admin/indexer
/admin/fees
/admin/feature-flags
/admin/audit-log
7. Home page requirements
Visual direction: follow supplied references closely in hierarchy and atmosphere, but implement original assets and components rather than copying third-party art.
Hero:
FORGE wordmark
“WHERE AI AGENTS ARE BORN.”
subhead: create, tokenize and launch autonomous AI agents on-chain
primary CTA FORGE AN AGENT
secondary CTA EXPLORE AGENTS
status chips: No code / On-chain / AI native
original 3D/AI-rendered industrial forge scene with animated embers/parallax
Below hero:
HOT FROM THE FORGE horizontal agent cards
TRENDING AGENTS table with tabs: Top Gainers / Most Volume / New Launches
FORGE AN AGENT 3-step explainer
ad/featured slot
live protocol activity strip
Top global ticker:
horizontally scrolling eligible tokens/agents
organic slots and clearly labeled paid Boost slots
no impression should visually disguise paid inventory as organic ranking
8. Explore page
Filters:
All
New
Trending
Graduated
Trading
Research
DeFi
Social
Content
Community
Gaming
Utility
Sort:
trending score
newest
volume
market cap
activity
Cards show:
avatar
agent name/ticker
description
template tags
launch status
price/market cap/24h change when available
volume
holders if indexed/provider available
creator verification state
boosted label if applicable
9. Launch wizard
Step 1 — Agent Setup
Fields:
agent name
ticker
short description
personality/backstory
avatar generation/upload
template
capabilities
sources
Generate with Grok (required MVP): After choosing a template (and optional seed keywords), the creator can press Generate with Grok. The server uses the FORGE xAI key to produce a full identity suited to that agent type — name, ticker, short description, personality/backstory, tags, starter greeting, capability suggestions — plus one or more matching profile-image candidates (Grok Imagine / image generation). Results populate the form as editable fields; creator can regenerate all, regenerate avatar only, edit manually, or upload their own image. See Identity generation.
Right-side live preview updates instantly (including while generation streams).
Step 2 — Token / launch configuration
MVP:
launch rail locked to PONS
network displayed as Robinhood Chain
pair asset determined from approved PONS list/config
launch config fetched live, not cached permanently
creator tax / PONS economics presented exactly as returned by protocol
creator fee recipient shown as FORGE AgentFeeVault address
user beneficiary/action target shown separately
optional initial buy if supported by chosen route
full transaction preview
Future rails appear disabled with Coming Soon.
Step 3 — Agent runtime
model selection restricted to FORGE-supported models
default grok-4.7/current configured model; model name must come from server config
template prompt preview (non-secret public summary, not full safety internals)
The “discount” applies to FORGE-controlled charges only, never to third-party protocol fees unless explicitly subsidized.
Agent Boosting
Creator chooses $1,000 or $5,000 equivalent of FORGE in MVP.
UI quotes required FORGE amount using a configured oracle/DEX quote source.
User approves and burns FORGE through a dedicated burn transaction/contract.
Boost is activated only after burn confirmation.
Boost has a defined duration configured by admin.
Boost inventory:
global top ticker
Explore featured row
Agent side ad units
home featured ad units
Every placement is labeled BOOSTED/FEATURED.
Organic trending formula excludes boost spend.
Boost can increase eligible discovery visibility but cannot overwrite organic ranking everywhere.
Protocol fee allocation dashboard
The product should report, but not promise, this proposed starting framework:
staking / rewards pool: 30%
treasury & development: 20%
FORGE buybacks: 20%
agent creator incentives: 20%
ecosystem grants: 10%
Important arithmetic correction: under the stated percentages, a $1,000,000 eligible-fee example allocates $200,000 to creator incentives, not $100,000. The full distribution is $300k + $200k + $200k + $200k + $100k = $1,000,000.
Percentages are governance/config parameters, not guarantees.
Forge Reserve
Buybacks do not need to auto-burn. Purchased FORGE may be held in a transparent reserve and later used only under disclosed rules for incentives, strategic liquidity, grants or other approved purposes. Reserve wallets/contracts must be public in the transparency page.
12. Trending score
Organic trending is deterministic and independent of paid boosts. Suggested MVP score: