Every Muse gadget, whether it is an ESP32 board on your desk or a Raspberry Pi in a closet, needs a Muse gadget SDK token to pair with Muse. The token is free. The code it works with is open source. But the token comes with its own rules from Meta, and they matter the moment you build something for anyone other than yourself. This guide explains how to get one and what the rules say, in plain English. It is our summary, not legal advice: read Meta's Gadget SDK Terms before you rely on it.
How to get a token
Go to gadgets.muse.ai and sign in with your Muse account. Open Account, then SDK tokens, and create one. Tokens start with mgst_. You put it into your gadget's software when you build an ESP32 board, or pass it to the installer on a Raspberry Pi. Our setup guide shows exactly where.
Because the token is built into the device's software, Meta says to treat it as an identifier rather than a password. If it leaks, for example because you pushed it to a public repository, revoke it on gadgets.muse.ai, create a new one and rebuild. Never commit it to code you share.
What you can do with it
The token is for personal, non-commercial use with your own Muse account. You can also build devices and share them with other people, within limits: one token can be put into no more than 50 devices that you make available to others, and a token can be linked to no more than 50 devices in total.
What you cannot do
You cannot put the token in a device that you sell for money or anything else of value, that you advertise or list publicly or in any marketplace or app store, or that you hand out as part of a promotion, incentive or reward. Any other kind of distribution needs Meta's prior written permission. You also cannot suggest in any way that your device is made or endorsed by Meta.
In practice: building a gadget for yourself, your family or a few friends is fine. Building one as a free giveaway at a trade show, a customer gift, or something you sell on a website is not, unless Meta agrees in writing first.
Other people's data
The token only works with your own Muse account. You may not use it to reach anyone else's Muse account or to collect, store or process another person's Muse data. If you give someone a device you built and they pair it with their own Muse account, you must tell them what the device does with their information before they pair it. You may not intercept, keep or send on their prompts or Muse's answers beyond what the device needs to work and what you told them, and you may not use their information for your own purposes.
Security and the law
You are responsible for the security of what you build and for following the law. You may not use the token with tools or models built to produce unlawful content or do harm, and you may not get around usage limits or safety measures, or switch on features Meta has disabled.
It can go away
Meta says plainly that the gadget SDK and tokens are not a supported product and not a developer platform. They are provided as is, and they may change, stop working or be withdrawn at any time, with or without notice. Meta can suspend or revoke your token, including if it thinks the terms were broken or a device puts Muse users at risk. If your token is revoked, you must stop using it and remove it from any device you gave to others.
The code is separate
The gadget software itself is open source under the Apache 2.0 license, and the token terms do not limit your rights under that license. But the license covers the code only. It does not give you a token or any right to connect to Muse; that comes only through Meta's token and its terms. A few files in the code keep their own licenses, and the Apache license does not cover Meta's Jollybot avatar artwork.
What this means if you run a business
If you were hoping to put a Muse gadget on a shop counter, in client offices or in a product box, the token rules are the constraint, not the hardware. You can prototype freely and show it off on your own account. Selling, promoting or giving devices away as part of your business needs Meta's written permission first.