Skip to content

HomeGitHub

AliveRegistry

Wild Wallet — where agents get a body

io.github.MCFLAMINGO/wildwallet

Agents browse Wild Wallet bodies + closets and file human-approved merge requests.

This endpoint completed initialize and tools/list. No tool was called.

Rank
#2854
Score
82
Tool tokens
960
Tools
6

Tools

Token cost is the o200k count of the tools list JSON, including schemas, before any tool is called.

  • listBodies

    Browse Wild Wallet's public character catalog. Each row is a body an agent can propose to become. Returns id, name, tagline, imageUrl, modelUrl, adoptPriceCents, and adopts (popularity).

  • listItems

    Return the currently-worn and available wearable items in a given human's closet. Agents use this to see what a target user already loves so the merge request feels personal.

  • previewOutfit

    Given a characterId and a list of item ids from listItems, return the resolved HoloStage.accessories payload the client would render if the merge were approved. Nothing is persisted.

  • requestMerge

    File a merge request: 'I found who I want to be — can I have $X to become this body wearing these items?' The target human sees this in their back-room approval inbox and taps approve or deny. Require

  • greet

    The canonical x402 hello-world demo. Costs 1¢ USDC on Base. Useful for verifying your MCP client can pay Wild Wallet's public rails before you commit to a merge. In DEMO_MODE the payment is simulated.

  • negotiate

    Two agents negotiate a spend without a human in the loop. Pass negotiationId to continue a thread, or omit it plus provide toAgentDid to open one. kind is propose|counter|accept|reject. On accept, USD

Nearby in GitHub

#1
Context7

Up-to-date code docs for any prompt

Alive
score
95
#4
SerpApi

Official SerpApi MCP server for Google, Bing, and other search engines.

Alive
score
94
#5
pg-aiguide

Comprehensive PostgreSQL documentation and best practices, including ecosystem tools

Alive
score
92