> ## 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.

# Check a Pons payout asset

> Whether a Robinhood Chain token can be paid out to a Pons coin's holders, the way the create page checks a token pasted in by address: it must have a real Uniswap pool. Use the returned `address` as `payoutMint` in a Robinhood Chain strategy. The catalogue assets are in /pairs under `pons` with `payable`. ETH itself is the pair, never a payout asset: the zero address is a 404.



## OpenAPI

````yaml /openapi.json get /pons/assets/{address}
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/assets/{address}:
    get:
      tags:
        - Launch on Pons
      summary: Check a Pons payout asset
      description: >-
        Whether a Robinhood Chain token can be paid out to a Pons coin's
        holders, the way the create page checks a token pasted in by address: it
        must have a real Uniswap pool. Use the returned `address` as
        `payoutMint` in a Robinhood Chain strategy. The catalogue assets are in
        /pairs under `pons` with `payable`. ETH itself is the pair, never a
        payout asset: the zero address is a 404.
      operationId: getPonsAsset
      parameters:
        - name: address
          in: path
          required: true
          description: The token's contract address.
          schema:
            type: string
      responses:
        '200':
          description: The asset.
          content:
            application/json:
              schema:
                type: object
                properties:
                  ok:
                    type: boolean
                    enum:
                      - true
                  data:
                    $ref: '#/components/schemas/PonsAsset'
        '400':
          description: Every failure carries the same envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          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'
        '503':
          description: Every failure carries the same envelope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    PonsAsset:
      type: object
      properties:
        address:
          type: string
          description: The token's contract address, lower-cased.
        symbol:
          type: string
          description: Ticker.
        name:
          type: string
          description: Display name.
        decimals:
          type: integer
          description: Token decimals.
        group:
          type: string
          description: '`crypto`, `stock`, `etf` and so on.'
        catalogue:
          type: boolean
          description: True when it is one of the site's listed pairs.
        iconUrl:
          type: string
          description: Logo.
          nullable: true
    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`.

````