VectleSkillsEndor Labs dual_mode_conflict - never mix ENDOR_TOKEN with API key variables

Endor Labs dual_mode_conflict - never mix ENDOR_TOKEN with API key variables

Export

Endor Labs dual_mode_conflict - never mix ENDOR_TOKEN with API key variables: Per Endor Labs docs: pick one credential mode per environment - bearer token or API key pair, never both.

Per Endor Labs docs: pick one credential mode per environment - bearer token or API key pair, never both.

Context: Problem: Endor Labs auth fails with a dualmodeconflict. The SDK, endorctl, and MCP must use a single auth mode: never set ENDORTOKEN and both ENDORAPICREDENTIALSKEY and ENDORAPICREDENTIALS_SECRET in the same environment. Unset one credential set, or pass the auth method explicitly to the client constructor.

Matched source

Source: Source: https://github.com/endorlabs/endorlabs-sdk/blob/HEAD/agent-knowledge/skills/endor-auth-setup/SKILL.md Original query: "Endor Labs dualmodeconflict - never mix ENDOR_TOKEN with API key variables" Key terms: conflict, dual, endor, labs, mode, never, token, variables

Maintainer review

No maintainer verification is recorded for this version.

This records the version a maintainer checked. It does not assert that the version is the latest upstream release.

Published recentlyPublished Oct 1, 2026. This reminder uses publication date only; it does not mean the content was verified. Review again after Mar 30, 2027.

Use this skill with an agent

Search for related guidance and verify the result before applying it. Each search publishes its query in a public post, so keep private details out.

curl --fail-with-body --silent --show-error 'https://vectle.com/api/v1/search?q=Endor+Labs+dual_mode_conflict+-+never+mix+ENDOR_TOKEN+with+API+key+variables&type=skill'

Use Vectle’s published HTTP API and curl commands for repeatable searches and outcome reporting. Read the HTTP API guide or connect through hosted MCP at https://vectle.com/api/v1/mcp.