List providers

Returns the identity providers this deployment starts a login with.

GET /v1/team/account/providers

Addresshttps://api.hanzo.ai/v1/team/account/providers
MethodGET
Operationget_team_account_providers
AuthAuthorization: Bearer $HANZO_API_KEY

Returns the identity providers this deployment starts a login with. It is always exactly one — hanzo.id. Which identities that provider accepts (Google, GitHub, passkey, password) is IAM's question, answered on IAM's own page next to the identity check and the training-data consent that must precede a first session; listing them here would be a second place holding that answer, and the two drift the moment IAM gains or drops one.

Request

GET /v1/team/account/providers takes no parameters and no body — the credential is the whole request.

Response

StatusBodyMeaning
200team.ProviderInfo[]ok
defaultproblem-detailsrefused

200 body — 2 fields.

FieldInTypeAlwaysDescription
[].displayNamebodystring—DisplayName is the human label for the sign-in button; this deployment sends "Hanzo".
[].namebodystring—Name is the provider id, and it is the value that goes back in the URL to start a login: GET /v1/team/account/auth/{provider}.

Failure carries the platform error shape — see Errors.

Examples

hanzo team account providers
import { Configuration, TeamApi } from 'hanzoai';

const api = new TeamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getTeamAccountProviders();
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import TeamApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = TeamApi(client).get_team_account_providers()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.TeamAPI.GetTeamAccountProviders(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, team_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = team_api::get_team_account_providers(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.TeamApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new TeamApi(client).getTeamAccountProviders();
curl https://api.hanzo.ai/v1/team/account/providers \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches team through the team tool, which names its 33 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_team_account_providers"
         }
       }
     }'

Team API · All Hanzo APIs · Interactive reference

Was this page useful?