How can I control tool access and spending for each AI agent?

Consider a research agent that reads search and SEO data, and a creative agent that generates media. Both can use the workspace balance, but their keys can allow different tools and carry different caps. Choose those controls from the supported key settings and check their saved values.

A prompt saying do not exceed the budget is an instruction to the agent. An enforced key cap is a backend control. Use both where appropriate, and keep the human approval required for the requested task.

A spending cap depends on an enforceable reservation. Tools billed at actual cost without a guaranteed maximum cannot be used through a capped key. Do not remove a cap just to make a blocked operation run; inspect the contract and choose an acceptable operation or policy.

A provider rate limit serves a different purpose. It controls request throughput, not your task's total cost. Read the actual error and retry guidance before deciding whether to retry.

Review the saved permissions and limits in the workspace, then let the agent discover and inspect suitable tools. Those read-only steps do not prove that a paid operation would succeed, but they avoid spending just to check a connection.

For an authorized production task, retain the run ID and inspect the resulting receipt. Rotate or revoke the relevant credential when its job ends, while preserving the evidence needed to review prior spending.

Supported paid tools use Agentik's prepaid workspace balance. Inspect the selected tool's pricing units and maximum before approving a run; a reservation can differ from its settled charge. Funding fees, taxes and your model's usage are separate. Current terms are on the Pricing and Billing pages linked below.

For a workspace with research and creative agents, configure two execution keys. The research key can be restricted to selected data operations while the creative key can use selected generation tools. Choose optional caps deliberately and verify the saved settings.

The table is a proposed permission design, not a statement that these controls are already configured. A tool without an enforceable maximum may not work with a capped key.

Connect Claude Code, then use this prompt with your connected assistant. Keep credentials in the authorized connection.

Agentik publishes this guide. References below describe the product, its billing and the alternatives discussed. This page was updated on 19 October 2026; provider terms and tool availability can change.

• Key limits
• Pricing and caps
• Billing contracts