Test an AI provider

Check that an AI provider's key works, by calling the provider with it.

POST/workspaces/{workspace}/ai/providers/{id}/test

Credentials that do not work still answer, with ok false and message saying what went wrong. Owners only.

A key that does not work still answers 200, with ok false and message saying what went wrong.

Authentication: Required. Send an access token as Authorization: Bearer.
MCP tool: ai with action test_provider, and the same inputs
Scope: An access token needs workspace:admin.

Path parameters

Name	Type	Required	Description
`workspace`	string	Yes	The workspace’s slug, e.g. “flagon-io”.
`id`	string	Yes	The AI provider’s id.

Example request

curl -X POST https://api.g1t.sh/workspaces/flagon-io/ai/providers/ai_01kpx4n8r3g9s0v5w7x1z2a3be/test \
  -H "Authorization: Bearer $G1T_TOKEN"

Example response

A successful request answers 200 with:

{
  "ok": true,
  "message": "Anthropic answered with 3 models."
}

Errors

A failed request answers with one of these statuses and a body like {"error": {"code": "not_found", "message": "Repository not found."}}. See errors.

Status	Code	When
401	`unauthenticated`	A token is required, or the one sent is not valid.
403	`forbidden`	The token is valid but not allowed to do this, such as a member-only change, or a token without the scope it needs.
404	`not_found`	It does not exist, or you cannot see it.
409	`conflict`	The request conflicts with the current state.
422	`invalid`	The input is not valid. `message` says which field and why.