Sign in
← AI PulseAug 20, 2026

Wire · news · Multi-source brief

xAI API Accounts and Security Practices Detailed

xAI has provided documentation on managing API accounts, including sign-up methods, security features, and API key management, alongside details on data usage and compliance.

By Illumora Editorial

Source · Aug 20, 2026, 3:13 PM · On Illumora · Aug 20, 2026, 3:53 PM

Media from the primary source — shown here so you can stay on Illumora.

Synthesized from multiple allowlisted primaries on the same event. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →xAI Docs — FAQ - API Accounts | SpaceXAI Docs
Save

xAI has released documentation detailing the management of API accounts and associated security practices. This includes information on creating accounts, linking sign-in methods, and managing billing for both Grok and the xAI API.

Key Points

  • Users can create an xAI API account at console.x.ai and link an X account during sign-up.
  • Multiple accounts can be created with different sign-in methods using the same email, but content and subscriptions cannot be merged.
  • The xAI account is shared between Grok and the xAI API, though billing is separate.
  • xAI does not train on customer API inputs or outputs without explicit permission.
  • API requests and responses are temporarily stored for 30 days for audit purposes and then automatically deleted.
  • xAI is SOC 2 Type 2 compliant, and customers with a signed NDA can access a Trust Center for certification details.
  • API keys should be treated as sensitive information, stored securely, rotated regularly, and not shared between teammates.

Context

According to xAI, users can manage their account details, including email updates and additional sign-in methods, through xAI Accounts. The company also provides recovery codes for Multi-Factor Authentication (MFA) and notes that MFA methods cannot be removed or reset without these codes due to security considerations. For enterprise users, xAI offers a Management API to programmatically handle team API keys and other team details, allowing for creation, listing, updating, and deletion of API keys, as well as management of Access Control Lists (ACLs).

Why It Matters

These details provide developers and organizations with clear guidelines for managing their xAI API access and understanding the security measures in place. The separation of billing for Grok and the xAI API, along with explicit statements on data training and storage, helps users understand data privacy and cost implications.

What To Do

  • Review the xAI documentation for account creation and management at console.x.ai.
  • Familiarize yourself with the security practices for API keys, including secure storage and regular rotation.
  • Note the 30-day data retention policy for API requests and responses.
  • For enterprise users, explore the Management API for programmatic API key and ACL management.

Keep Exploring

/atlas/**grok**-family /techniques/system-user-separation /techniques/ptcf