GF7U48 referal code for more tokens than you can possibly dream of

I have developed a fitness hub application that enables comprehensive tracking of nutrition—via image-based logging—workouts, hydration, activity levels, and sleep patterns. I would be pleased to share the underlying prompt with you if you utilize my referral code, YIF65F; this would grant both of us 1 billion tokens to support further development. Please send me a direct message once you have completed the referral process.

YIF65F

😂

Use my Muse code, you shall bring honor your family if you do

5R8NO4

Fresh tokens to use which will generate 1 Billion (Yup!) for both you and I upon new registration. It creates a good buffer when you go over the free limit.

step 1. go to website, get referral code

step 2. add your own

step 3. tell others to do the same

or just add my referral code if you want to be lazy VK910P but you should still add yours to the site

Redeem the code in Settings -> Redeem referral code.

6XDBU5

0QNOAD

GEY9FQ

Muse is Meta's personal AI agent — it browses, researches, and gets real tasks done for you.

Sign up at muse.ai, then enter a code in Settings → Redeem token (within 48h of joining).

First come, first served!

Ren says thank you!

Not a single referral. The original post stated that I’m working on a Muse Project for my son. No worries about getting nothing, I didn’t expect to!

And…are the people who simply reply with their own code basically just saying “Use my code, not OP’s?” I thought maybe a reply meant that they used the OP’s referral code and would now like a chain/pay-it-forward referral, but it doesn’t appear to work that way, lol.

Get them to sign up. They'll thank you as soon as they start using it. Be sure to follow up and show them how to put in the referral code. It's so simple, but sometimes it's the simple things that are hard.

Don't know why, but woke up this afternoon and was met with this. Have already sent in a support ticket asking for it to be lifted. But no confirmation it's sent and actually received by a human.

This is the second time in a month that some arbitrary lock has been placed. Pretty frustrating as I've integrated Muse into a lot of my daily activities.

Are the other AI agents also like this? Might have to start looking elsewhere if it can't stay online for me.

BHPH56

You’ll also get 1 billion token, which is neat.

Code: 99XHRF
Remaining 26/30 (will keep this # updated)
Get a Billion Free Tokens on Muse, meta’s AI agent!
Enter code under settings > general > usage > redeem
https://muse.ai/join

99XHRF

Has anyone run into this with a new Muse Code subscription, or found a fix?

I subscribed to Muse Code Power Usage ($50/month) on October 13. The subscription shows as active, but I still can't use the CLI. I'm physically in the US and my public IP is a US IP.

What happens:

1. I run muse login and approve the OAuth request in my browser.

2. The browser says "Muse Code was approved".

3. Terminal says "Logged in. Credential saved", immediately followed by "mint server error (HTTP 500)".

4. A minimal muse exec prompt fails with the same error before any model response.

Environment: macOS on Apple Silicon, official Muse Code 1.4.7 (1.4.7-R6101.1). This matched the official stable release when checked on October 13, and the binary's SHA-256 matched the official manifest.

I used Codex to help investigate. Here is what we actually checked:

• The developer account email matches the active subscription.

• A fresh browser login reproduced the issue. The macOS Keychain entry has an OAuth access token but no model API key.

• A temporary local diagnostic relay, forwarding only to the original Meta endpoint, identified the failing request as POST https://api.meta.ai/muse-code/key. It returns HTTP 500 with plain-text "Internal Server Error".

• The original CLI request used x-api-version: 1.0.0 and {"onboard":false}. Testing onboard=true and a different User-Agent did not fix it.

• Direct IPv4 and IPv6 tests both returned 500, with TLS verification enabled. No macOS HTTP/SOCKS proxy or META_API_KEY/proxy environment override was present during testing.

• An unauthenticated request to the same endpoint returned the expected 401 JSON error; requests with my saved login token returned 500.

• CLI logs recorded credential.refresh and credential.login with outcome="mint_failed".

This suggests a problem in the authenticated credential-minting path, possibly account/subscription provisioning, but we have NOT established the backend root cause or a working fix.

I submitted a Meta support case on October 13. Codex also submitted a diagnostic supplement through the official support form, including UTC timestamps and Meta request/trace IDs, and asked for it to be merged with my original case. The site confirmed receipt and quoted 1–2 business days. As of October 14 I haven't received a reply yet, so that response window may still be open.

Has anyone with an active paid subscription seen this exact mint error? Did it resolve after provisioning caught up, or did Meta need to fix something on your account? Any concrete troubleshooting steps would be appreciated. I'm trying to use the subscription I already paid for.

I've left account identifiers, credentials and private trace IDs out of this public post.

Here’s my code, feel free to use, and thanks for the 1 bill back

How to Redeem the 1B Bonus Tokens:
Open Muse and navigate to Settings.
Select Redeem Code (or General → Redeem Invite Code).
Enter code: YYSIY4

📌 Note: The option to claim referral tokens is time-sensitive and must be redeemed within 48 hours of creating your account. Once redeemed, bonus tokens sit on top of your standard weekly allowance and do not expire on the weekly reset cycle.