xint-phase1-deploys-with-existing-xai-key
xint Phase 1 (8 command families: analyze, ai-search, report, article, collections, costs, health, capabilities) runs entirely on the xAI API key already present in X-Pulse config. No new credentials are needed for immediate deployment. Phase 2 requires X Bearer Token; Phase 2b requires OAuth 2.0 Client ID from X Developer Portal.
Related
- xint-phased-credential-model-three-tiers
- xint-phased-credential-deployment-model
- xint-mcp-credential-tier-separation-required
- x-api-v2-credentials-not-available-at-session
- x-pulse-xint-complementary-not-replacement
- xint-phase1-health-shows-error-without-bearer-token
- xint-three-phase-credential-unlock-model
- xint-phase1-health-check-shows-expected-failure
- xint-phased-credential-activation-model
- xint-three-phase-credential-model-for-capability-gating
- xai-console-vs-x-developer-portal-are-completely-different
- xint-health-shows-failure-in-phase-1-expected-behavior
- xai-console-vs-x-developer-portal-are-separate
- x-api-402-credits-depleted-not-auth-failure
- xai-console-and-x-developer-portal-are-completely-separate-p
- x-api-v2-pay-per-use-tier-requires-prepaid-credits-before-ca