Tools

Tool servers the platform offers this account, with their approved tools#

GET /v1/account/tool-catalog

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Response 200

Errors: 400, 401, 403, 404, 409, 429, 500, with an ErrorBody body.

Example

curl -X GET "$ANSWERSTACK_API_URL/v1/account/tool-catalog" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

Turn on a managed server, or connect this account to a catalog server: with no sign-in, an API key, or an OAuth sign-in URL#

POST /v1/account/tool-catalog/{serverId}/connect

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Path parameters

Request body

application/json, required.

Response 201

Errors: 400, 401, 403, 404, 409, 422, 429, 500, with an ErrorBody body.

Example

curl -X POST "$ANSWERSTACK_API_URL/v1/account/tool-catalog/{serverId}/connect" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

The account's MCP tool servers, with how many tools wait for review#

GET /v1/account/tool-servers

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Response 200

Errors: 400, 401, 403, 404, 409, 429, 500, with an ErrorBody body.

Example

curl -X GET "$ANSWERSTACK_API_URL/v1/account/tool-servers" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

Add a tool server. No sign-in: saved and discovered. API key: saved once the key works. OAuth: saved as pending, with a sign-in URL#

POST /v1/account/tool-servers

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Request body

application/json, required.

Response 201

Errors: 400, 401, 403, 404, 409, 422, 429, 500, with an ErrorBody body.

Example

curl -X POST "$ANSWERSTACK_API_URL/v1/account/tool-servers" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "string",
  "url": "string"
}'

Find out whether a server needs no sign-in, an API key, or OAuth#

POST /v1/account/tool-servers/probe

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Request body

application/json, required.

Response 200

Errors: 400, 401, 403, 404, 409, 422, 429, 500, with an ErrorBody body.

Example

curl -X POST "$ANSWERSTACK_API_URL/v1/account/tool-servers/probe" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "url": "string"
}'

Rename a tool server#

PATCH /v1/account/tool-servers/{serverId}

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Path parameters

Request body

application/json, required.

Response 200

Errors: 400, 401, 403, 404, 409, 429, 500, with an ErrorBody body.

Example

curl -X PATCH "$ANSWERSTACK_API_URL/v1/account/tool-servers/{serverId}" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "string"
}'

Remove a tool server, its tools and its credential#

DELETE /v1/account/tool-servers/{serverId}

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Path parameters

Response 200

Errors: 400, 401, 403, 404, 409, 429, 500, with an ErrorBody body.

Example

curl -X DELETE "$ANSWERSTACK_API_URL/v1/account/tool-servers/{serverId}" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

List the tools on the server now: new ones wait for review, changed ones stop until reviewed#

POST /v1/account/tool-servers/{serverId}/discover

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Path parameters

Response 200

Errors: 400, 401, 403, 404, 409, 429, 500, with an ErrorBody body.

Example

curl -X POST "$ANSWERSTACK_API_URL/v1/account/tool-servers/{serverId}/discover" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

Sign in to a server again: a new API key, or a new OAuth sign-in. Probes first, so a server that changed how it signs in is handled#

POST /v1/account/tool-servers/{serverId}/reconnect

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Path parameters

Request body

application/json, required.

Response 200

Errors: 400, 401, 403, 404, 409, 422, 429, 500, with an ErrorBody body.

Example

curl -X POST "$ANSWERSTACK_API_URL/v1/account/tool-servers/{serverId}/reconnect" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

The tools the account's servers offer, and where each one stands#

GET /v1/account/tools

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Query parameters

Response 200

Errors: 400, 401, 403, 404, 409, 429, 500, with an ErrorBody body.

Example

curl -X GET "$ANSWERSTACK_API_URL/v1/account/tools" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

Calls per tool, error rate, p95 latency, last use, and the playbooks that bind it. Visibility, not billing: tool calls are included#

GET /v1/account/tools/usage

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Query parameters

Response 200

Errors: 400, 401, 403, 404, 409, 429, 500, with an ErrorBody body.

Example

curl -X GET "$ANSWERSTACK_API_URL/v1/account/tools/usage" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

One tool: its definition, any waiting change, and what the review should look at#

GET /v1/account/tools/{toolId}

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Path parameters

Response 200

Errors: 400, 401, 403, 404, 409, 429, 500, with an ErrorBody body.

Example

curl -X GET "$ANSWERSTACK_API_URL/v1/account/tools/{toolId}" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

Approve the definition you reviewed, with the description our model will read and what the tool does#

POST /v1/account/tools/{toolId}/approve

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Path parameters

Request body

application/json, required.

Response 200

Errors: 400, 401, 403, 404, 409, 422, 429, 500, with an ErrorBody body.

Example

curl -X POST "$ANSWERSTACK_API_URL/v1/account/tools/{toolId}/approve" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "reviewedHash": "string",
  "description": "string",
  "effect": "read"
}'

Decide a tool is not to be used#

POST /v1/account/tools/{toolId}/reject

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Path parameters

Request body

application/json, required.

Response 200

Errors: 400, 401, 403, 404, 409, 429, 500, with an ErrorBody body.

Example

curl -X POST "$ANSWERSTACK_API_URL/v1/account/tools/{toolId}/reject" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

Run an approved tool with sample arguments. A tool that changes something needs confirm: true, because it acts on the real system#

POST /v1/account/tools/{toolId}/try

Authentication: Bearer token: Authorization: Bearer <token> (Supabase access token).

Path parameters

Request body

application/json, required.

Response 200

Errors: 400, 401, 403, 404, 409, 422, 429, 500, with an ErrorBody body.

Example

curl -X POST "$ANSWERSTACK_API_URL/v1/account/tools/{toolId}/try" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "arguments": {},
  "confirm": true,
  "retry": {
    "inputResponses": {}
  }
}'