Authentication

Most users do not need to create, copy, or manage an API key first. Let your agent check sign-in status. When authentication is required, it starts device authorization and gives you an official NoxInfluencer link and user code. You can complete authorization in any browser.

New-user sign-in flow

After installing the Skill, tell your agent:

Help me get started with NoxInfluencer Skill. Check my sign-in status and guide me through signing in or creating an account if needed.

The normal flow is:

1. Your agent checks the NoxInfluencer CLI and authentication state.
2. If you are not signed in, it starts device authorization and gives you an official link and user code.
3. Open the link in any browser, sign in to an existing account or create a new one, and approve access.
4. The CLI creates or reuses access credentials and stores them in local configuration. You do not need to copy the API key through chat.
5. Your agent checks available usage, then continues with your first task.

New accounts receive a one-time allowance of 30 free Credits with no credit card required. Review your current balance and plan status in the Skills Dashboard.

Start device authorization manually

Only when your agent does not start sign-in automatically, run:

noxinfluencer login

The CLI prints an authorization link and user code, opens the link when possible, and waits for approval. For an Agent, container, or remote terminal, separate the user action from polling:

noxinfluencer login start --json
noxinfluencer login wait <login_id>

You can check one pending login without waiting:

noxinfluencer login status <login_id>

login start does not open a browser and does not print the secret device code. An agent may give you verification_uri_complete and user_code, but must not expose device_code. Use the optional noxinfluencer login --browser flow only when a local loopback callback is available.

For Chinese onboarding URLs and hints:

noxinfluencer --lang zh login

The Chinese account entry is NoxInfluencer Skills Dashboard.

API key is a fallback

Configure an API key manually only when device authorization is unavailable or your agent environment is managed centrally.

• Obtain the key from the official Skills Dashboard
• Use noxinfluencer auth --key-stdin instead of passing the key as a command argument
• Managed environments can use NOXINFLUENCER_API_KEY
• Never put an API key in chat messages, logs, screenshots, support messages, or shared files

Account access and Credits

Whether an action can run may depend on all of the following:

• Whether your account plan includes the capability
• Whether the Tool is marked available or beta
• Whether you have enough Credits
• Whether the matching underlying NoxInfluencer service quota or permission is available

The website uses Credits for plans and consumption. The CLI uses quota to show your current balance and availability. Some actions also check an underlying service quota, so a remaining Credit balance does not guarantee access to every capability.

Creator search and lookalike discovery are priced by the number of creators returned. Before a broad workflow, let your agent check current prices and recent usage:

noxinfluencer quota
noxinfluencer pricing tools --charged-only
noxinfluencer quota usage --days 7

See Credits and Quotas for details.

Skill, Remote MCP, and Rest API

• This page describes the normal Skill / CLI sign-in path
• Remote MCP is a read-only surface for MCP clients and uses its own API key or OAuth connector setup; see Remote MCP
• Rest API starts from /api-service and the current Theneo docs. It uses Rest API Credit, which is separate from the Skill's Credits

If sign-in fails

Ask your agent to check, in order:

1. noxinfluencer doctor
2. noxinfluencer login
3. noxinfluencer quota

In a remote Agent flow, rerun login start --json if the authorization expires, then wait with the new login_id. Do not reuse an expired login or ask the agent to print the secret device code.

If setup still fails, use CLI Diagnostics and Error Codes.