X plugin just doesn't work

[cabrinha]

Not sure why, but this message keeps repeating and I have the X plugin installed and authenticated, but my bots can't seem to use it

[cabrinha]

Got more signal after ripping the plugin out, re-adding it, and actually opening console.x.com.

What works

• Plugin X 2.1.0 (plugin=49086599) is installed and user-X shows [connected], tools=25.
• OAuth already succeeded as @yuppieventures.
• https://console.x.com/accounts/2066889309559361536 is signed in as that same account. Total balance $25.00. Default project is already Pay Per Use. Usage is $0.00 / 0 events. Auto-recharge is off.
• Agent / Usage / Credits / Projects pages have no Enroll / Enable MCP button. Projects shows Plan: Pay Per Use · 0 connected apps.

What fails
Every billed (and even the supposedly-free) MCP read returns the same 403. Reproduced on get_users_me and get_usage_credits:

{
  "type": "https://api.x.com/2/problems/client-forbidden",
  "title": "Client Forbidden",
  "detail": "This request is billed to the authenticated user. Create a developer account at the Developer Console and enroll it in Pay-per-use.",
  "reason": "user-not-enrolled",
  "registration_url": "https://console.x.com",
  "required_enrollment": "Pay-per-use"
}

Reconnect is broken
AuthenticateMcpServer with force_reauth on user-X returns: "X" does not support interactive authentication: no_auth_link. There is no connect card to refresh the OAuth session. Uninstall/reinstall is the only path, and after that we still get tools=25 + this 403.

Why the bot loops that console.x.com sentence
The 2.1.0 skill (x-api-mcp-guide / name: X MCP guide) maps user-not-enrolled to error 2 and tells agents to say only:

This X account isn't set up yet. Go to https://console.x.com, register and onboard with this same X account, then come back and I'll retry.

Then: do not retry, do not search. If the user already did that, reconnect, probe once, and if it still 403s say the same line again. That's the loop. Console is already onboarded with $25, so the skill is lying.

Related:

• X plugin: SKILL.md name "X MCP guide" does not match folder x-api-mcp-guide #269 skill folder vs YAML name mismatch (cosmetic; connector still lists 25 tools)
• Check X credit balance before telling users to buy #265 would stop the "buy credits at console.x.com" nag when balance > $0, but it still treats this 403 as error 2, so it would not fix search

Posting is a separate gap (plugin never requests tweet.write). This issue is: connected + credits + Pay Per Use, MCP still user-not-enrolled, and no way to re-auth except uninstall.