Hume AI subpackage_tools API is one of 9 APIs that Hume AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
Tagged areas include subpackage_tools. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, pricing, and an AsyncAPI specification.
This API exposes
9 operations
across 3 paths,
and defines 11 schemas.
It is described by OpenAPI 3.1.0, at version 1.0.0.
Requests are made against a single base URL, https://api.hume.ai.
9 operations3 paths11 schemas2 DELETE3 GET2 PATCH2 POST
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.hume.ai
Authentication
API Key
Resource Areas
1
Authentication & Security 1
Hume AI subpackage_tools API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as X-Hume-Api-Key (bearerAuth).
Paths & Operations 9
Across 3 paths, the API surfaces 9 operations — 2 DELETE, 3 GET, 2 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.
subpackage_tools 9
POST
/v0/evi/tools
Create tool
create-tool1 parambody→ 201
GET
/v0/evi/tools
List tools
list-tools5 params→ 200
GET
/v0/evi/tools/{id}
List tool versions
list-tool-versions5 params→ 200
POST
/v0/evi/tools/{id}
Create tool version
create-tool-version2 paramsbody→ 201
PATCH
/v0/evi/tools/{id}
Update tool name
update-tool-name2 paramsbody→ 200
DELETE
/v0/evi/tools/{id}
Delete tool
delete-tool2 params→ 200
GET
/v0/evi/tools/{id}/version/{version}
Get tool version
get-tool-version3 params→ 200
PATCH
/v0/evi/tools/{id}/version/{version}
Update tool description
update-tool-description3 paramsbody→ 200
DELETE
/v0/evi/tools/{id}/version/{version}
Delete tool version
delete-tool-version3 params→ 200
Schemas 11
The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are return_user_defined_tool (11 properties), posted_user_defined_tool (5 properties), posted_user_defined_tool_version (4 properties), return_paged_user_defined_tools (4 properties). Each schema is shown below with its type and property counts.
posted_user_defined_tool
object
A tool to be posted to the server
5 properties2 required
return_paged_user_defined_tools
object
A paginated list of user defined tool versions returned from the server
4 properties4 required
ReturnUserDefinedToolToolType
string
tools_update-tool-name_Response_200
object
Empty response body
posted_user_defined_tool_name
object
A tool name change to be posted to the server
1 property1 required
tools_delete-tool_Response_200
object
Empty response body
tools_delete-tool-version_Response_200
object
Empty response body
posted_user_defined_tool_version_description
object
A tool version description to be posted to the server
1 property
posted_user_defined_tool_version
object
A new version of an existing tool to be posted to the server
4 properties1 required
return_user_defined_tool
object
A specific tool version returned from the server
11 properties8 required
ReturnUserDefinedToolVersionType
string
Specification
The full machine-readable OpenAPI contract behind this narrative.
