APIClaw Toolset API
The Toolset API from APIClaw — 1 operation(s) for toolset.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/apiclaw:apiclaw-toolset-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: LiteLLM Toolset API
description: 'Proxy Server to call 100+ LLMs in the OpenAI format. **Customize Swagger Docs**
👉 ```LiteLLM Admin Panel on /ui```. Create, Edit Keys with SSO. Having issues? Try ```Fallback Login```
💸 ```LiteLLM Model Cost Map```.
🔎 ```LiteLLM Model Hub```. See available models on the proxy. **Docs**'
version: 1.105.1
tags:
- name: Toolset
paths:
/toolset/{toolset_name}/mcp:
get:
summary: Toolset Mcp Route
description: 'Namespace a toolset as its own MCP endpoint.
Connecting to /toolset//mcp exposes exactly the tools defined in
the toolset. Access is enforced: non-admin API keys must have the toolset
listed in their object_permission.mcp_toolsets grant list, or the request
will be rejected with a 403.'
operationId: toolset_mcp_route_toolset__toolset_name__mcp_get
parameters:
- name: toolset_name
in: path
required: true
schema:
type: string
title: Toolset Name
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Toolset
patch:
summary: Toolset Mcp Route
description: 'Namespace a toolset as its own MCP endpoint.
Connecting to /toolset//mcp exposes exactly the tools defined in
the toolset. Access is enforced: non-admin API keys must have the toolset
listed in their object_permission.mcp_toolsets grant list, or the request
will be rejected with a 403.'
operationId: toolset_mcp_route_toolset__toolset_name__mcp_patch
parameters:
- name: toolset_name
in: path
required: true
schema:
type: string
title: Toolset Name
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Toolset
post:
summary: Toolset Mcp Route
description: 'Namespace a toolset as its own MCP endpoint.
Connecting to /toolset//mcp exposes exactly the tools defined in
the toolset. Access is enforced: non-admin API keys must have the toolset
listed in their object_permission.mcp_toolsets grant list, or the request
will be rejected with a 403.'
operationId: toolset_mcp_route_toolset__toolset_name__mcp_post
parameters:
- name: toolset_name
in: path
required: true
schema:
type: string
title: Toolset Name
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Toolset
head:
summary: Toolset Mcp Route
description: 'Namespace a toolset as its own MCP endpoint.
Connecting to /toolset//mcp exposes exactly the tools defined in
the toolset. Access is enforced: non-admin API keys must have the toolset
listed in their object_permission.mcp_toolsets grant list, or the request
will be rejected with a 403.'
operationId: toolset_mcp_route_toolset__toolset_name__mcp_head
parameters:
- name: toolset_name
in: path
required: true
schema:
type: string
title: Toolset Name
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Toolset
options:
summary: Toolset Mcp Route
description: 'Namespace a toolset as its own MCP endpoint.
Connecting to /toolset//mcp exposes exactly the tools defined in
the toolset. Access is enforced: non-admin API keys must have the toolset
listed in their object_permission.mcp_toolsets grant list, or the request
will be rejected with a 403.'
operationId: toolset_mcp_route_toolset__toolset_name__mcp_options
parameters:
- name: toolset_name
in: path
required: true
schema:
type: string
title: Toolset Name
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Toolset
delete:
summary: Toolset Mcp Route
description: 'Namespace a toolset as its own MCP endpoint.
Connecting to /toolset//mcp exposes exactly the tools defined in
the toolset. Access is enforced: non-admin API keys must have the toolset
listed in their object_permission.mcp_toolsets grant list, or the request
will be rejected with a 403.'
operationId: toolset_mcp_route_toolset__toolset_name__mcp_delete
parameters:
- name: toolset_name
in: path
required: true
schema:
type: string
title: Toolset Name
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Toolset
put:
summary: Toolset Mcp Route
description: 'Namespace a toolset as its own MCP endpoint.
Connecting to /toolset//mcp exposes exactly the tools defined in
the toolset. Access is enforced: non-admin API keys must have the toolset
listed in their object_permission.mcp_toolsets grant list, or the request
will be rejected with a 403.'
operationId: toolset_mcp_route_toolset__toolset_name__mcp_put
parameters:
- name: toolset_name
in: path
required: true
schema:
type: string
title: Toolset Name
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Toolset
components:
schemas:
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
input:
title: Input
ctx:
type: object
title: Context
type: object
required:
- loc
- msg
- type
title: ValidationError
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
securitySchemes:
APIKeyHeader:
type: apiKey
description: Bearer token
in: header
name: x-litellm-api-key
HTTPBearer:
type: http
scheme: bearer
x-provenance:
method: harvested
publisher: APIClaw
source: https://apiclaw.biz/openapi.json
note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
stamped by stamp-openapi-provenance.py (roadmap#793)