> ## Documentation Index
> Fetch the complete documentation index at: https://docs.purps.lol/llms.txt
> Use this file to discover all available pages before exploring further.

# Prepare a Pons launch

> Step 1: the message to sign with your EVM wallet (`personal_sign`, EIP-191). Pons is the one launchpad that still signs a message before the build, because launching there is invite-only and the signature is how the invite is checked before anything is spent. The message carries a `launches:` line that spells the launch out in words: name, ticker, pair, creator tax and first buy. Send `devBuy` and `creatorTaxBps` here too when you will send them to submit; they are part of those words.



## OpenAPI

````yaml /openapi.json post /pons/launches/prepare
openapi: 3.1.0
info:
  title: PURPS API
  version: 2.0.0
  description: >-
    Everything purps.lol can do, as JSON. Read the coin list, a coin's full page
    and the launchpad; launch coins on purps.lol, pump.fun and Pons; wire an
    existing pump.fun coin's fees into a strategy; steer a coin you own. No key,
    no signup. A launch is one call that returns unsigned transactions: the
    launch transaction can only land with your wallet's signature, and that is
    the proof. The few writes that need a message signature (Pons launches,
    wiring a strategy onto a coin, creator authority) come as a prepare/submit
    pair. Every transaction is signed in your wallet, never by us. Every
    response is `{ ok: true, data }` or `{ ok: false, error }`. Cross-origin
    requests are allowed from any site. Every answer from the API itself carries
    `RateLimit-Limit` and `RateLimit-Policy`; uncached ones (writes, prepare and
    submit, refusals) carry `RateLimit-Remaining` and `RateLimit-Reset` as well.
    The 503 while the API is paused and the 410 on old v1 write addresses carry
    neither.
servers:
  - url: https://purps.lol/api/v2
security: []
tags:
  - name: Coins
    description: Read what the site shows.
  - name: Launch on purps.lol
    description: Launch a coin on purps.lol. Build, sign, send, poll.
  - name: Launch on pump.fun
    description: Launch straight on pump.fun with fees wired to a strategy.
  - name: Launch on Pons
    description: Launch through Pons, the launchpad on Robinhood Chain.
  - name: Redirect a pump.fun coin
    description: Point an existing pump.fun coin's creator fees at a strategy.
  - name: Manage a coin
    description: Attach a strategy to a coin launched without one. Creator-signed.
  - name: Creator authority
    description: >-
      Steer a purps.lol coin you own: act on a position, change its strategy,
      ask for authority, or hand the coin on. Every move is signed by the
      owner's wallet and published on the coin's Changes tab.
  - name: Transactions
    description: Send a signed Solana transaction through our relay and watch it land.
paths:
  /pons/launches/prepare:
    post:
      tags:
        - Launch on Pons
      summary: Prepare a Pons launch
      description: >-
        Step 1: the message to sign with your EVM wallet (`personal_sign`,
        EIP-191). Pons is the one launchpad that still signs a message before
        the build, because launching there is invite-only and the signature is
        how the invite is checked before anything is spent. The message carries
        a `launches:` line that spells the launch out in words: name, ticker,
        pair, creator tax and first buy. Send `devBuy` and `creatorTaxBps` here
        too when you will send them to submit; they are part of those words.
      operationId: preparePonsLaunch
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PonsTerms'
      responses:
        '200':
          description: What to sign.
          content:
            application/json:
              schema:
                type: object
                properties:
                  ok:
                    type: boolean
                    enum:
                      - true
                  data:
                    $ref: '#/components/schemas/Prepared'
        '400':
          description: Every failure carries the same envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '429':
          description: Every failure carries the same envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    PonsTerms:
      type: object
      properties:
        name:
          type: string
          description: 1 to 32 characters.
          required: true
        symbol:
          type: string
          description: 1 to 10 characters.
          required: true
        pairToken:
          type: string
          description: A pair from /pairs `pons`. Omit or the zero address for ETH.
        creatorWallet:
          type: string
          description: The EVM wallet that signs and sends.
          required: true
        devBuy:
          type: string
          description: >-
            Your own first buy, in ETH, as a decimal string. Part of the signed
            words when sent, so send the same value to submit.
        creatorTaxBps:
          type: integer
          description: >-
            A creator tax on every trade, basis points, up to 2000. Default 0.
            Part of the signed words when sent, so send the same value to
            submit.
    Prepared:
      type: object
      properties:
        ts:
          type: integer
          description: Unix seconds. Send it back unchanged with the signature.
        message:
          type: string
          description: >-
            The exact text to sign. Sign the UTF-8 bytes as they are: no prefix,
            no hashing on Solana; `personal_sign` on Robinhood Chain.
        expiresInSeconds:
          type: integer
          description: How long the signature stays valid. 300.
        hash:
          type: string
          description: >-
            Pons launch prepare only: the terms' hash, as embedded in the
            message. For your records.
        configHash:
          type: string
          description: >-
            Strategy and Pons register prepare only: the hash of `config`
            exactly as you sent it, as embedded in the message.
    Error:
      type: object
      properties:
        ok:
          type: boolean
          description: Always false on a failure.
        error:
          type: string
          description: >-
            A short reason in plain words: `coin not found`, `too many
            requests`, `invalid wallet signature`.

````