xint-phased-credential-model-three-tiers
xint capabilities are gated by credential availability across three phases: Phase 1 (xAI API key only, already available) unlocks 15+ capabilities including x_search, analyze, report, article extraction, and xAI Collections. Phase 2 (+ X Bearer Token) unlocks direct X API v2 read ops: search with exact metrics, profile, tweet, thread, trends, watch, stream, media. Phase 2b (+ OAuth 2.0 Client ID) unlocks write/engagement ops: like, bookmark, follow, engage (AI growth engine), analytics, timing heatmaps. System should auto-detect available credentials and expose only valid commands.
Related
- xint-vs-xpulse-capability-gap-56-commands
- 2026-04-04-oracle-001-self-architecture-analysis
- docker
gws-capability-expansion-nova(archived)- google-httponly-cookies-require-network-tab-not-console
- x-api-v2-credentials-not-available-at-session
- phased-credential-activation-for-external-api-tools
- xint-phased-credential-deployment-model
- xint-xai-geo-proxy-via-base-url-env-override
- xint-mcp-credential-tier-separation-required
- xint-phase1-deploys-with-existing-xai-key
- xint-three-phase-credential-unlock-model
- xint-phased-credential-activation-model
- xint-oauth-pkce-callback-and-required-scopes
- xai-geoblock-env-var-override-for-xint
- xint-three-phase-credential-model-for-capability-gating
- xai-console-vs-x-developer-portal-are-completely-different
- xint-credential-phasing-model-three-tiers
- xint-three-phase-credential-activation-model
- xai-console-vs-x-developer-portal-different-platforms
- xint-mcp-must-specify-engagement-policy
- xint-x-developer-portal-distinct-from-xai-console