Agent Tools

Agent Tools are protocol-agnostic, extensible product APIs (same family as /v1/me) under POST /v1/tools/* for desktop agents after a model tool call. They are not part of OpenAI / Anthropic / Gemini chat protocols.

The surface grows over time. Shipping today — web tools:

Tool	Endpoint	Notes
Web Search	POST /v1/tools/web-search	Search result list
Web Fetch	POST /v1/tools/web-fetch	Fetch one URL body
Web Deep Search	POST /v1/tools/web-deep-search	Search + read; heavier and usually more expensive

Dependencies and limits

• You must supply third-party engine API keys (see the Admin whitelist).
• Exactly one Active engine per tool; calls return 503 when the Active engine has no key.
• Per-call billing; failures are not charged against the user budget.

What to do in Admin

1. Open Tools → Configuration.
2. Maintain each engine catalog for the tools you use: API key + unit cost (currency follows system billing currency).
3. Pick the Active engine; engines without a saved key cannot be activated.
4. Call /v1/tools/* with a user sk-…; inspect Tools → Invocations or Request logs (provider_id=octafuse-tools).

Minimal client call

curl -sS "$GATEWAY_URL/v1/tools/web-search" \
  -H "Authorization: Bearer sk-your-api-key" \
  -H "Content-Type: application/json" \
  -d '{"query":"OctaFuse gateway","count":5}'

Full fields and engine whitelists: GitHub · user API.

Next

• Image generation / edit
• System config · Request logs