Sari la conținut

Română · beta. Traducerea a fost făcută automat și este încă în curs de revizuire. Citește pagina în engleză

perspectiva aiqbenchProduse AI

analiza aiqbench

This guide provides a practical technical reference for integrating vision-capable LLMs via API, focusing on the standardized request body structure required for multimodal inputs. It details specific implementation patterns for handling image data formats and model selection without altering the underlying integration logic.
Surse care acoperăOpenRouter, arXiv
Ce este aceastaLectura unui model asupra articolului și a acoperirii conexe, scrisă pentru aiqbench. Nu sunt cuvintele publicației.

How to Send an Image to an LLM via API (Vision Guide)

OpenRouter11 min de cititArticolul și perspectiva sunt în engleză.

To get a model to read a screenshot, you need the right request body. This guide shows the content-array pattern that works across every vision-capable model we support, when to use base64 instead of a hosted URL, and how to build multimodal RAG on top of it.

If you want a vision-capable Large Language Model (LLM) to read a screenshot, inspect a chart, or answer questions about a photo, you need to build the request body correctly. This guide covers image input only, meaning a model reading a picture you give it, not generating or editing one. The pattern is simple. Send a chat message whose content array includes a text part and an image_url part to our image understanding endpoint. After that, the request shape stays the same, and you change only the model field to use any vision-capable model we support. One model handles Optical Character Recognition (OCR) better, another reads UI screenshots more reliably, another reasons over charts more carefully. Because the input shape doesn’t change, you can test those differences without changing your integration. This guide covers sending images to multimodal models, choosing between public URLs and base64 uploads, building multimodal RAG pipelines, and the practical limits that matter once you’re in production. We support multimodal image understanding through the Chat Completions API. Body: a messages array where the user message’s content is a list of parts, one {"type": "text"} and one {"type": "image_url"}. Model: any slug with image input (e.g. anthropic/claude-opus-4.8, google/gemini-3-flash-preview).…

Extras afișat conform termenilor RSS ai publicației · 200 cuvinte · textul integral și figurile sunt pe site-ul publicației

Subiecte conexe