Executor is a layer that sits between chat and a whole catalog of external tools and APIs, so instead of wiring up credentials for each one separately, you configure them once in Executor and Neotask calls them through a single policy layer. That means tasks that would otherwise need several separate tool connections — each with its own auth setup — can run through one consistent path, with Executor handling the credential management underneath.
Once a tool or API is set up in Executor, describe the task in chat; the agent routes the request through Executor's catalog and policy layer instead of a dedicated per-tool integration.
No — that's the point of Executor: configure a tool once and the agent calls it through the shared catalog and policy layer afterward.
It's a layer — a policy and catalog system that sits in front of whatever external tools and APIs you've configured.
$0/mo
Download without a card and start for free.
$50/mo
The full personal agent platform for one person.
$100/mo
One company workspace with room to add your team.
$200/mo
Multiple workspaces and capacity for larger teams.
Explore: Skills · Glossary · Solutions · Use cases · Examples · Comparisons · Templates · Blog · Docs