Baseten

Export secrets to a Baseten team's secrets for your models.

Connection

What	This provider
Vendor	Baseten
Key	`baseten-secrets`
Availability	`available`. You can connect it today.
Credential we hold	`baseten-key`
Values read back	no
Activation	`immediate`

Direction	What it does
`export`	We write names and values from your environment into the store.

Baseten returns no value once it holds one, so we can write here and cannot read back.

immediate. The running app sees a new value at once.

Direction	Policies you can pick
`export`	`create_only`, `overwrite`, `overwrite_and_prune`

How syncs work says what each one does.

Paste a credential from the vendor. We seal it and never show it again.

Field	Label	Kind	Required	What it is
`apiKey`	API key	secret; we mask it here and seal it	yes	In Baseten, open Organization settings, then API keys. Use a team key with Manage and call all team models.

You set these when you connect. Every mapping on the connection shares them.

Field	Label	Kind	Required	Advanced	What it is
`teamId`	Team ID	text	yes	no	Call GET https://api.baseten.co/v1/teams with your key and copy your team's id.

You answer these once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`namePrefix`	Secret name prefix	text	yes	no	We name each secret PREFIX_KEY and only touch secrets under this prefix. A sync owns its prefix: pruning deletes every team secret named PREFIX_ anything, including ones this sync did not write.

We probe for these when we verify the connection.

Permission	Directions	Blocking	Without it
`View secret metadata`	every direction	yes	Preview cannot list the team's secrets.
`Manage team secrets`	`export`	yes	Export cannot write anything.