Skip to main content

Your Cats

The homepage wallet lookup section lets anyone enter an address and resolve the cats currently exposed by the CCAT ownership contract.

Lookup flow​

  1. The user enters a wallet address on clankercats.com.
  2. The frontend requests /api/cats-wallet?wallet=<address>.
  3. That route calls OwnerUpegsPage(owner, 0, 500) on the CCAT contract 0xD7800C338228a6eeb37cF74133732Fb6aE05915F.
  4. The frontend renders each returned pair through /api/cat-render?id=<id>&seed=<seed>&thumb=1.

Wallet list endpoint​

GET /api/cats-wallet?wallet=<address>

Response shape:

[
  { "id": "1", "seed": "61427657765452807143428" },
  { "id": "3", "seed": "66150024248322452226050" }
]

Behavior:

  • wallet must match a 0x-prefixed 40-byte hex address.
  • Invalid input returns 400 with { "error": "invalid wallet address" }.
  • The route is rate-limited to 30 requests per minute per IP.
  • Successful responses are cached with Cache-Control: public, max-age=60.

Count endpoint​

GET /api/cat-count?wallet=<address>

This route exists for lightweight ownership checks. It calls OwnerUpegsCount(address owner) on the same CCAT contract and returns the total number of cats for the wallet.

Notes​

  • The docs here describe the app's current ownership lookup implementation, not a generalized indexer.
  • The wallet view is chain-specific to Base because the contract reads are wired through the app's Base client.