Native Anthropic Tools: Web Search, Web Fetch, and Code Execution

StackJack Automations (managed agents that run on your behalf) can use three capabilities built into the Anthropic platform itself, alongside your connector tools. These are called native tools because Anthropic executes them directly — they never touch your MSP products or your connector credentials.

Automations are on by default for every workspace. If you do not see the Automations area in your portal, StackJack has suspended it for your account — contact StackJack support.

The three native tools

You enable each one with a toggle in the automation builder. The compact rows show the current cost basis: credits per search for web search, tokens only for web fetch, and container time for code execution.

Not connector-plan-gated

Unlike connector tools, native tools have no connector plan tier. The shipping product does not apply a connector plan gate to them: whether your connectors are on Free, Pro, or Business is irrelevant, and any tenant with Automations enabled can turn on any native tool for any agent.

The reason is how they're billed. Connector tool calls are covered by your per-connector StackJack subscription, so tiers apply. Native tools are Anthropic platform usage — searches, fetched-content tokens, and sandbox runtime. Managed-key runs settle that usage through StackJack credits; bring-your-own-key runs are charged directly by Anthropic and do not reserve or consume StackJack credits. Since usage is already metered this way, there is no connector-plan tier to apply.

See Credits and bring-your-own Anthropic key for how usage is funded and where current rates appear.

What this means when designing automations

• Enabling native tools does not change which connector tools the agent can call — those are still governed by your connector plans and the agent's tool selection.
• Native tool usage does not count against any connector's monthly call allowance.
• Cost control for native tools is usage-based: the agent only incurs native-tool usage when it actually searches, fetches, or executes code during a run. Managed-key usage settles from StackJack credits; bring-your-own-key usage appears on your Anthropic account.
• A positive credit balance is not enough to launch a managed-key run. StackJack reserves the run's full estimated cost up front and refuses the launch when the balance is below that whole amount, so a balance that looks non-zero can still be too small to start. Top up to cover the reservation, not just to get above zero.
• A run that already ended as "Credit exhausted" does not resume when you buy credits. That status is final for that run. Buying credits lets you start a new run, and lets the next scheduled occurrence go ahead — it does not restart the one that stopped. See Credits and bring-your-own Anthropic key.