Equip an AI assistant
Use task descriptions to identify tools an assistant could call, then prepare the required inputs in your application.
Find and run tools from a catalog of 1,700+ tools across 55+ vendors. Access them through your Gomry key, with usage billed in one place.
Explore available capabilities through a shared catalog, then add the tools that fit your workflow. Your application controls which tools run and what inputs they receive.
Use task descriptions to identify tools an assistant could call, then prepare the required inputs in your application.
Review candidate tools and their requirements before implementing a workflow around one vendor’s offering.
For tools that return a running job, check progress and collect the output when it is ready. Polling adds no charge.
| When you are considering | How ToolsAPI fits |
|---|---|
| Integrating vendors individually | ToolsAPI provides a shared access and billing layer for the tools in its catalog. Separate vendor accounts and credentials are not required. |
| Switching between catalog tools | Each tool retains its own input format. ToolsAPI exposes that schema; your application still prepares the correct arguments. |
| Planning execution costs | Review listed prices before a run. For tools charged per result, the final amount depends on the results returned. |
Tool execution is billed by metered tool cost. Discovery and inspection are billed per lookup. For tools priced per result, the final cost depends on the results returned.
Enable the service for your project, grant the required API key permissions and set a monthly budget in the Cloud console.
View current pricing ↗With ToolsAPI enabled for your project and the required key permissions, you can use the tools in its catalog. Access does not extend to every API offered by those vendors.
No. A run can complete even when the underlying tool finds no match. Check both the run status and the tool’s response before deciding whether to retry.