Skip to content

docs: Our Tools - which tools are available; restore tool_blocked (AIM-768) - #590

Open
domdalty-ops wants to merge 5 commits into
mainfrom
AIM-768/docs/our-tools-hidden-tools
Open

domdalty-ops wants to merge 5 commits into
mainfrom
AIM-768/docs/our-tools-hidden-tools

Conversation

@domdalty-ops

@domdalty-ops domdalty-ops commented Oct 5, 2026 •

Copy link
Copy Markdown

Summary

The Our Tools page (hidden, #585–#588) was written before the pilot started hiding tools. Since then only tools that keep no state between calls are offered: tools that create lasting resources, call or message people, look up data about people, or collect data from social networks are hidden from search, and calling one by id answers 403 tool_blocked.

  • Intro and description: no longer offer "social media search" / "social data".

  • New section Which tools are available: what is not offered and why, and the restricted form of the browser tools (no saved logins or stealth mode, 30 steps / 240 s; 5-minute browser sessions).

  • Error table: 403 tool_blocked is back. docs: Our Tools - drop the tool_blocked row (AIM-768) #588 dropped it, but it is exactly what a customer gets for a hidden tool id.

  • max_cost_usd: required not only for result-priced tools but also for tools that cost more than the $0.25 default (pricing.requires_max_cost says so); a max_cost_exceeded that names run_limit_usd cannot be fixed by raising max_cost_usd (aimlapi/aimlapi#6687).

  • After the triad audit (aimlapi/aimlapi ADR 0015): a tool that runs in one call is never cut — past ~110 s the run answers 202 running, keeps going and is charged when it ends; every run with output carries "untrusted": true; tools whose cheapest call costs more than a single run may cost are not offered; a browser session's connection details are in that run's answer only; a run_limit_usd refusal asks for a smaller input.

No tool or vendor is named. The text follows the internal decision record (ADR 0014 in aimlapi/aimlapi).

🤖 Generated with Claude Code

domdalty-ops and others added 4 commits October 5, 2026 13:19
…M-768)

Stateful, people-data and social-media tools are hidden (ADR 0014), so the
page no longer offers social media search, says what is not offered and
why, and lists 403 tool_blocked again - the answer for a hidden tool id.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…IM-768)

A tool that costs more than the $0.25 default needs max_cost_usd too, and
search/inspect now say so in pricing.requires_max_cost; a max_cost_exceeded
that names run_limit_usd cannot be fixed by raising max_cost_usd.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Triad audit on dev (F-9, F-16): the browser agent is sent a 30-step limit
and charged per step it takes, but its provider ends a run on its own time
budget (268-392 s observed), so "at most 240 seconds" was not true; a quick
tool answers when it finishes (up to ~65 s) whatever wait_ms says; a failed
run is not charged; idempotency keys are per API key.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ble tools (AIM-768)

Owner decisions after the triad audit (aimlapi/aimlapi ADR 0015): a sync tool
is never cut - past ~110 s the run answers 202 running and is charged when it
ends; every run with output carries "untrusted": true; tools whose cheapest
call is above the per-run limit are not offered; a browser session's
connection details are in that run's answer only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
main renamed the page (Our Tools -> Toolbox, quickstart/our-tools.md ->
quickstart/toolbox.md, "your AI" -> "your LLM") and added a Quickstart: MCP
section, which collided with this branch's edit to the same opening line.

Resolved by keeping both: main's naming, this branch's wording of the tool
list ("news search, company and domain data"). Everything else from this
branch — the untrusted flag, the 202/wait_ms rules, "Which tools are
available", tool_blocked — came through untouched.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants