Wallet

Open Wallet →

Calling it

This is your own data, so a call has to say who you are. Make a token at /token and send it as a header.

curl -H "Authorization: Bearer $MU_TOKEN" \
  https://micro.mu/api/v1/wallet/address

The same method over MCP, which is what an agent speaks: wallet_address. The answer is identical.

How every call behaves →

Methods

GET /api/v1/wallet/address

Your own address on Base, to receive USDC. Created the first time you ask. Funds sent on any other chain land at the same address there and cannot be reached from here

Needs an account.

curl \
  -H "Authorization: Bearer $MU_TOKEN" \
  "https://micro.mu/api/v1/wallet/address"
GET /api/v1/wallet/balance

What your wallet holds in USDC on Base. Says so plainly when the chain could not be reached, because that is not the same as holding nothing

Needs an account.

curl \
  -H "Authorization: Bearer $MU_TOKEN" \
  "https://micro.mu/api/v1/wallet/balance"

The same methods are tools over MCP, and every service on this instance is in one reference.