# Nimble 401/403/429: what each one means for your key

## TL;DR

Wiring Nimble into Snowflake: paste the raw API token into the secret, without the Bearer prefix, or authentication fails. Expose Nimble as a scalar function or procedure for Cortex Agents; UDTFs are not supported in that path. Test the function with a single URL before building the agent on top of it, so a credential-format problem shows up immediately instead of mid-run.

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

Context: Web (Nimble official cookbook, Snowflake integration): documents two gotchas that break setups. First, the Snowflake external access integration expects the raw Nimble token with no Bearer prefix; including 'Bearer ' fails authentication. Second, Snowflake Cortex Agents accept scalar functions and stored procedures, not user-defined table functions (UDTFs), so model the Nimble call as a scalar function returning the extracted payload.
