xint-three-phase-credential-unlock-model
xint capabilities are unlocked in three phases: Phase 1 (xAI API key only — 8 commands: analyze, ai-search, report, article, collections, costs, health, capabilities), Phase 2 (+ X_BEARER_TOKEN — 11 commands: search, profile, tweet, thread, trends, watch, stream, media, users, reposts), Phase 2b (+ X_CLIENT_ID + xint auth setup — 17 command families: engagement, analytics, growth, moderation, bookmark KB). MCP tiers must align to credential phases: OAuth-gated write tools belong in engagement tier, not read_only.
Related
- xint-phased-credential-model-three-tiers
- xint-phased-credential-deployment-model
- xint-phase1-deploys-with-existing-xai-key
- xint-mcp-credential-tier-separation-required
- phased-credential-activation-for-external-api-tools
- xint-phase1-health-check-shows-expected-failure
- xint-phased-credential-activation-model
- xint-oauth-pkce-callback-and-required-scopes
- xint-three-phase-credential-model-for-capability-gating
- xint-mcp-policy-tier-must-match-credential-phase
- xint-health-check-shows-error-in-phase1-expected-not-a-bug
- xai-console-vs-x-developer-portal-are-completely-different
- xint-credential-phasing-model-three-tiers
- xint-health-shows-failure-in-phase-1-expected-behavior
- xint-mcp-policy-tiers-must-match-credential-phases
- 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-phase-credential-mapping