Your APIs become tools, without the wrappers
Point almyty at a schema and it generates a typed, callable tool for every operation. The services you already run — including the old SOAP ones nobody wants to touch — become things an agent can use.
More than the easy formats
OpenAPI is table stakes. SOAP and Protobuf are the point.
Anyone can parse OpenAPI and GraphQL. almyty also reads SOAP/WSDL and Protobuf/gRPC — the legacy and internal services nobody wants to touch become tools too. Or skip schemas entirely and point it at an npm package.
Tool types
Generated when it can be, hand-written when it should be
API tools
Auto-generated from an imported schema. One tool per operation, typed from the spec.
HTTP tools
Define a request by hand when you want a tool that does not map cleanly to a schema operation.
JavaScript tools
Run custom logic in a sandbox backed by worker threads, isolated from the rest of the platform.
GraphQL tools
Target a specific query or mutation directly, with the variables you choose to expose.
LLM tools
Wrap a model call as a reusable tool — classification, extraction, drafting — and call it like any other.
npm packages, as tools
Point almyty at an npm package — stripe, @aws-sdk/client-s3, lodash. It installs it in a sandbox, reads the types, and generates a tool per function. No schema needed.
Tool hub
A catalog your team can search
Generated and hand-built tools land in one hub, so the next person finds the tool instead of rebuilding it. Install them straight into your editor, or group them into a gateway and publish.
# find a tool across your gateways
$ npx @almyty/skills search "create user"
# install a gateway's tools into your editor
$ npx @almyty/skills install acme/petstore
# run one directly from the terminal
$ npx @almyty/skills run acme/petstore/get-pet --id 3