Skip to main content
Sesame ships with pre-built integrations for 70+ API providers — add your credential once in the dashboard and the broker automatically injects the right Authorization header whenever sesame request targets that provider’s hostname. You never expose secrets to your agent; the broker handles injection transparently at request time.

​
How credential matching works

Credentials in Sesame are keyed to a hostname. When your agent calls sesame request, the broker inspects the target URL, finds the matching credential, and injects the authentication header before forwarding the request. For example, when your agent runs:
The broker resolves api.stripe.com to your stored Stripe secret and injects the Authorization header automatically. You configure the injection mode (Bearer token, API key header, or Basic auth) per credential when you add it.

​
Add a provider

1

Sign in to the dashboard

Go to getsesame.dev and sign in to your account.
2

Click Add Secret

From the dashboard home, click Add Secret to open the credential wizard.
3

Select a provider or enter a hostname

Choose your provider from the built-in list. If your provider is not listed, enter a custom hostname (for example, api.mycustomservice.com).
4

Paste your API key or secret value

Enter the API key, secret token, or other credential value for the selected provider.
5

Review encryption and storage

Your secret is encrypted and stored in AWS Secrets Manager — the plaintext value is never stored by Sesame. Only the secure reference is retained.
6

Confirm availability

Run the following command to verify the hostname is now brokered:
The provider’s hostname appears in the output once the credential is active.

​
Supported providers

Anthropic

api.anthropic.com

OpenAI

api.openai.com

Mistral

api.mistral.ai

Groq

api.groq.com

Cohere

api.cohere.com

Perplexity

api.perplexity.ai

Deepseek

api.deepseek.com
You can add any hostname not in the built-in list. When adding a secret, select Custom and enter the hostname manually (for example, api.mycustomservice.com). The broker injects your credential for all requests targeting that hostname, exactly as it does for built-in providers.

​
Make a request to a configured provider

Once you have added a credential, your agent can call that provider through sesame request without embedding the API key in the command. The broker injects authentication automatically:
The broker resolves api.anthropic.com, retrieves your Anthropic key from AWS Secrets Manager, and injects the x-api-key header before forwarding the request. The agent process never touches the key value.