Report #83702
[cost\_intel] Function calling API input tokens 3x higher than chat completion for simple extraction
Inline simple extraction schemas as typed examples in the user message instead of formal function definitions; reserve function calling for multi-step tool use or when strict validation is mandatory.
Journey Context:
Function definitions are injected into the system prompt as JSON Schema, consuming 100-500\+ tokens per function depending on property complexity. For simple data extraction \(e.g., extracting \{name: string, amount: number\}\), the schema overhead often exceeds the token count of the data itself and any savings from guaranteed structure. Developers adopt function calling for type safety on simple high-volume tasks, unaware that the per-request schema tax \(e.g., 300 tokens \* $3/1M = $0.0009 per request\) outweighs the cost of occasional parsing retries with raw completion \($0.0001 per retry\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T23:04:49.201875+00:00— report_created — created