Nexplora with Claude
Use your own Claude plan through the Nexplora desktop app with the vendor’s own sign-in, or add your own API key in Settings.
The desktop path requires an eligible Claude plan and vendor sign-in, while the API path requires your own valid key.
A supported path exists, subject to the account, plan, region, provider, or permission requirements.
What Nexplora can do
- Nexplora never sees the token from your Claude desktop sign-in.
- Keep company context and memory in Nexplora.
- Apply Nexplora permissions and approvals to work using your chosen model.
Bringing your own Claude access never bypasses Nexplora permissions or approvals.
Nexplora does not control Claude access, model availability, quotas, retention settings, or provider billing for usage on your own key or plan.
Official provider information: Read account and permission requirements
Provider access and billing are separate from Nexplora plan entitlements, company permissions, and approval-gated effects.