xint-phased-credential-activation-model
xint unlocks in three discrete phases tied to credential availability: Phase 1 (xAI API key only — 8 commands including analyze, ai-search, report, article, collections), Phase 2 (+ X Bearer Token — 11 commands: search, profile, tweet, thread, trends, watch, stream, media, users, reposts, watchlist), Phase 2b (+ OAuth 2.0 Client ID — 17 command families: engagement, analytics, growth, moderation, bookmark KB). MCP server policy tier must be upgraded from read_only to engagement when Phase 2b credentials are added.
Related
- xint-three-phase-credential-unlock-model
- xint-phased-credential-model-three-tiers
- xint-phased-credential-deployment-model
- xint-phase1-deploys-with-existing-xai-key
- xint-mcp-credential-tier-separation-required
- xint-oauth-pkce-callback-and-required-scopes
- xint-three-phase-credential-model-for-capability-gating
- xint-mcp-policy-tier-must-match-credential-phase
- xai-console-vs-x-developer-portal-are-completely-different
- xint-credential-phasing-model-three-tiers
- xint-mcp-policy-tiers-must-match-credential-phases
- xai-console-vs-x-developer-portal-are-separate
- xint-three-phase-credential-activation-model
- xint-oauth-pkce-callback-url-and-required-scopes
- xint-oauth-pkce-callback-server-binds-to-port-3333-not-8477
- xint-mcp-policy-must-upgrade-to-engagement-after-oauth
- xint-phase-credential-mapping
- xint-mcp-defaults-to-read-only-must-pass-engagement-policy
- xint-mcp-default-policy-read-only-engagement-requires-explic
- xint-x-developer-portal-distinct-from-xai-console