Skip to main content
sesame hostnames queries the broker and returns the list of API hostnames that have credentials stored in your Sesame vault. Run it before starting an agent session to confirm every provider your agent depends on is configured — if a hostname is missing from the list, the broker will reject requests to it rather than pass them through unauthenticated.

​
Example output

The broker only injects credentials for hostnames that appear in this list. If you send a sesame request to a hostname that is not configured in your vault, the broker rejects the request before it reaches the provider. Add the missing provider’s credentials in the Sesame dashboard first.

​
Adding a new hostname

To add credentials for a provider that is not yet in your vault:
  1. Open the Sesame dashboard at getsesame.dev.
  2. Navigate to Secrets → Add Secret.
  3. Select the provider or enter the hostname manually.
  4. Paste your API key or OAuth token and save.
  5. Run sesame hostnames again to confirm the hostname now appears in the list.
Credentials are stored encrypted in the Sesame vault and are never transmitted to your device or exposed in CLI output. The sesame hostnames command only returns the hostname strings, not the secrets themselves.

​
Using hostnames with sesame request

Once you have confirmed a hostname is configured, pass it to sesame request as part of the full URL:
Make sesame hostnames the first step in your agent’s startup check. If a required hostname is missing, fail fast with a clear error rather than discovering the missing credential mid-task.