Build · Musegod

Build a muse into something you can use

Musegod already published the art, the soul, and the agent file. Building means pointing your app at those files. You do not have to re-mint.

Avatars

1. Read the muse from https://musegod.org/api/v1/muses/. The JSON includes art links, name, tier, and traits.
2. Use the image as the avatar in your app, Discord, or game profile.
3. If the user claims to hold it, check the owner field or the contract 0x13Ea3072b7215d4C9c2Ec4f498A08c5825129836 on Robinhood Chain. A copied picture is not ownership.

Virtual pets

1. Fetch https://musegod.org/muse/.txt and use it as the system prompt.
2. Keep that prompt in its own project so the user’s default assistant stays intact.
3. Store new chat notes in your app if you want memory. Those notes are not on the NFT unless you write an ERC-8048 update, and only the holder can do that while the keys are unlocked.
4. Do not let the pet sign transactions. The flock rules are a good default: words only, unless a human approves a spend.

Souls

The soul is the onchain context record. Builders can read it in one call, metadata(tokenId, "context"), or from the API field. The docs say the owner can correct a record by writing it again, and the contract can lock keys later. If you display a soul, show the source. After a lock, your cache may be the thing that goes stale, not the chain.

Other hooks from the docs

• Agent file: https://musegod.org/muse/.json
• Gallery index: muses/index.json
• Terrakin profile link: holder signs on the muse page, or POST /api/v1/muse-link
• Flock skill: flock.musegod.org/swarm.md
• OpenAPI: musegod.org/openapi.json

Full holder guide: How to activate your Musegod.