For property-management reports, the cheapest LLM API is not the one with the smallest displayed token price. It is the one you can replace without changing retry, deduplication, and human-review behavior. Use a normal chat completion for summarization and moderation labels, count tokens before sending long reports, and keep the provider behind a narrow adapter. A cost-efficient model is usually the right starting point, but a 429 or an ambiguous timeout must not create a second review case.

Short answer: compare available models for the expected input length, then use /v1/chat/completions with the selected model. There is no special summarization endpoint.…