- Real Lexe SDK client credentials (
lexeClientCredentials) - AgenticMail master keys (
mk_…) or minted tokens (ak_…) - Bearer tokens of any kind,
lnp1…payer proofs of real payments, or full invoice strings that identify your node
Use placeholder strings (PASTE_YOUR_…) in issues and PRs. Local config
(config.json, config.env) is gitignored — keep it that way.
Please report privately: open a GitHub security advisory ("Report a vulnerability") or email the maintainer. Do not open a public issue for suspected security problems.
Include: affected endpoint/tool, the request shape (redacted), and the behavior you observed.
- The server is designed so a public host does not hold a node key:
clients send their own Lexe identity as
Authorization: Bearerand it is forwarded per request. Deployments that bakelexeClientCredentialsintoconfig.jsonshould treat that file as a secret. payMaxSats/LEXE_PAY_MAX_SATSis an outbound payment cap forlexe.pay;0means uncapped. Public hosts should set a cap.