Authdog

API keys and M2M for LangChain

Last updated Oct 22, 2026
View as Markdown

Read the token from runtime context. Leave it out of tool arguments and the system prompt. The client secret stays in the process that minted the token.

The exchange is in Agent frameworks.

Which credential

Credential Use it when
Agent identity A named agent inside a project that already has users. Agents is sales-gated until access is approved.
M2M application The caller is a job, or Agents access is not approved yet. Same client_credentials grant.
Personal access token One person's script. Keep it off an unattended caller.
Service account Authdog REST automation. Not the bearer this hook checks.

To act for a person, keep this hook and present an RFC 8693 token. sub stays the user. act names the agent. The planned sample uses a token whose subject is the agent.

Read To learn how to
Custom channel auth for LangChain Refuse a missing bearer
Machine identity Choose the credential
LangChain See the hook

Learn more