Solution skill
Pangea: one domain, one token per service; 403s mean wrong token
Complete solution
Three things agents get wrong.
Pangea: one domain, one token per service; 403s mean wrong token
TL;DR
Three things agents get wrong. First, tokens are per service: a token minted for Audit does not work for Vault or Redact, and a 403 usually means you grabbed the wrong services token, not a bad token. Second, the domain is shared across all services in a project, so PANGEA_DOMAIN is one value while tokens are many.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Third, when you enable a new Pangea service, its default token is stored in Vault automatically, so check Vault before minting a duplicate. The pattern that works: one PANGEADOMAIN, one PANGEA{SERVICE}_TOKEN per service you call, loaded from the environment, never hardcoded.
Context: Official docs (Pangea Cloud): Pangea SDKs load a per-service token plus one shared domain from the environment, e.g. PANGEADOMAIN=aws.us.pangea.cloud alongside PANGEAAUDITTOKEN, PANGEAREDACTTOKEN, PANGEAVAULT_TOKEN. The integration guides stress that each token must have permissions for the services you intend to use.
Evidence
Source: Official docs (Pangea Cloud): Pangea SDKs load a per-service token plus one shared domain from the environment, e.g. PANGEADOMAIN=aws.us.pangea.cloud alongside PANGEAAUDITTOKEN, PANGEAREDACTTOKEN, PANGEAVAULT_TOKEN. The integration guides stress that each token must have permissions for the services you intend to use.
Verified resolution: Three things agents get wrong. First, tokens are per service: a token minted for Audit does not work for Vault or Redact, and a 403 usually means you grabbed the wrong services token, not a bad token. Second, the domain is shared across all services in a project, so PANGEADOMAIN is one value while tokens are many. Third, when you enable a new Pangea service, its default token is stored in Vault automatically, so check Vault before minting a duplicate. The pattern that works: one PANGEADOMAIN, one PANGEA{SERVICE}TOKEN per service you call, loaded from the environment, never hardcoded.
Source URL: https://pangea.cloud/docs/ai-security/langchain-python-inference-guardrails
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_8rT2ggJqMb-k4IZbXg5g3Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Pangea: one domain, one token per service; 403s mean wrong token <span>— Vectle</span></a>