Choose a launch venue, with the fee disclosed and a config prepared
onchain_agent_route_launchUSE WHEN an agent or a builder is about to launch a token and wants the venue chosen on published facts, with the fee disclosed before anything is signed. Venues covered: Clanker v4, Bankr, Virtuals, Zora creator coins. NOT FOR a swap (use onchain_agent_route_swap or onchain_agent_swap instead), a liquidity pool (use onchain_agent_route_lp), or generating a launch-prep repo (use onchain_agent_create_agent with the token-launch-prep template).
RULE ENFORCED: a launch route is a RECOMMENDATION. chosen_by names every fact it was chosen on, each with the venue page it was read from and the date it was read (facts_as_of). A fee schedule says nothing about what a token will do after it launches, and nothing here is a security review or an audit. null is unknown and never zero — a venue that publishes no per-party fee split is unread, not generous.
NON-CUSTODIAL: this tool NEVER deploys, signs, holds keys or moves funds. For the Clanker lane it returns a PREPARED CONFIG in the documented clanker-sdk v4 deploy() shape (the SDK is deliberately not a dependency of this service) which the caller reads and signs itself. Other venues are recommend-only: named, with a stated reason why no config is emitted.
THE FEE: Sato's slice is one entry in the venue's own reward-recipient list — the deployer takes 10000 - bps, Sato takes bps, and the two always total 10000. It is disclosed in fee on EVERY response, including when it is 0, and at 0 no Sato recipient appears in the config at all. A launch that is never signed pays nothing.
RETURNS (json): { route_id, goal, chain, venue: { slug, name, lane, pool_fee_pct, creator_share_pct, programmable_fee_split, facts: [{ fact, source_url, as_of }], unconfirmed, docs_url }, reason, chosen_by: [{ signal, value, source_field }], checked_at, alternatives: [{ slug, name, behind_on }], fee: { bps, recipient, basis, disclosed }, prepared_deploy, prepared_deploy_unavailable, facts_as_of, caveat, rules }. When no venue documents the chain: { unavailable, tried, supported_chains, supported_goals, checked_at, caveat }.
Example: { chain: "Base", goal: "agent_token", name: "Example Agent", symbol: "EXMPL", deployer: "0x…" }
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| goal | Yes | What is being launched. Matched against what each venue's own documentation covers. | |
| name | No | Token name. Required for a prepared deploy config; the caller's to choose, never invented here. | |
| chain | Yes | Chain display name as the directory writes it, e.g. 'Base', 'Arbitrum'. | |
| symbol | No | Token symbol. Required for a prepared deploy config. | |
| deployer | No | The 0x address that will sign the deploy and hold the creator reward share. Without it no config is prepared — it cannot be inferred. | |
| response_format | No | Text format; structuredContent is JSON either way. | markdown |
| max_pool_fee_pct | No | Reject venues whose PUBLISHED pool fee exceeds this percentage. A venue that publishes no fee is not excluded — unknown is not disqualifying. | |
| require_programmable_fee_split | No | Only venues documenting a programmable third-party recipient split. |