claude-3-5-sonnet-20240620 is the date-pinned version of Anthropic Claude 3.5 Sonnet, suitable for question answering, information organization, and iterative revisions using both text and images. It is especially suitable for applications that need to retain existing version configurations and should not be mixed with later Sonnet versions. Applications can be integrated using the public request format in this page's API section.
Point the Base URL to api.acedata.cloud, configure your platform API key and the model ID below, and use your compatible SDK or client.
api.acedata.cloudclaude-3-5-sonnet-20240620import os
from openai import OpenAI
client = OpenAI(
api_key=os.environ["ACEDATACLOUD_API_KEY"],
base_url="https://api.acedata.cloud/v1",
)
response = client.chat.completions.create(
model="claude-3-5-sonnet-20240620",
messages=[{"role": "user", "content": "Hello!"}],
)
print(response.choices[0].message.content)Choose an available protocol for this model. OpenAI SDK uses a Base URL ending in /v1; Anthropic SDK uses the root URL. See each guide for protocol-specific parameters, tools and response formats.
Clarify capacity, inputs and outputs, and invocation methods before choosing a model.
The date identifier specifies this version of Claude 3.5 Sonnet. When using Chat Completions or Messages, the application supplies the conversation history that needs to be retained and reads responses according to the corresponding structure.
Learn what claude-3-5-sonnet-20240620 can bring to your work.
You can submit screenshots, charts, and text questions together so that responses focus on visible content. Compared with pasting text alone, image-text messages preserve page layout and visual relationships, making them suitable for explaining interfaces and organizing screenshot information. Specify the areas of interest and the conclusions you need when asking questions to help reduce irrelevant descriptions.
Include user and assistant messages related to the current task in the messages of Messages or Chat Completions, handling the specific format according to the selected public interface. Retain the latest code, interim conclusions, and important constraints; when necessary, summarize longer histories again to avoid relying on outdated information.
The full date ID allows existing applications to continue using the same version configuration and makes it easier to record test targets. It differs from a series name without a date: when upgrading, explicitly change the model and then compare responses for the same set of inputs. A fixed version does not mean each generation will be identical word for word, nor does it guarantee permanent service availability.
Start with specific tasks to find where the model can be effective.
Provide screenshots of product pages, interfaces, or documents, and specify the fields, areas, or processes you want identified. You can request a page summary, a draft operation guide, or a list of items requiring confirmation. For dense text and key figures, crop the target area first, then verify it against the original image to avoid treating blurry content as a conclusion.
Submit existing explanatory text, business rules, or article drafts, and request that they be organized into Q&A, summaries, or revisions for specified readers. Adjust wording and structure through follow-up questions, making this suitable for content applications with existing Claude 3.5 Sonnet workflows. Delivery requirements should clearly specify facts to retain, parts that may be rewritten, and the output format.
Prepare representative questions, text-and-image examples, and historical responses for applications already using this dated version, and use the same materials to check performance after prompt changes. Deliverables may include records of response differences, omissions, and formatting deviations. When comparing newer models, keep inputs consistent rather than judging migration results solely by model names.
Choose based on task complexity, input materials, and expected results.
If an application originally used 20240620 and its prompts and evaluations were built around it, it can be retained for maintenance and regression testing. 20241022 is another dated version and cannot be substituted as an alternative spelling of the same ID. Before switching, compare image-and-text understanding, response structure, and adherence to business rules; do not assume that newer versions produce the same output as older ones.
New projects should not remain tied to this version long-term merely because the Claude 3.5 name is familiar. Anthropic has retired this dated version on the platforms it operates and recommends Claude Sonnet 4.6 as a replacement; this lifecycle arrangement does not equal the service status of this platform. Both entry points on this platform still list this model, but this does not constitute a commitment to continued availability. Compare candidate models using real tasks; if retaining the older version, the focus should be on compatibility with existing behavior rather than treating it as a Sonnet with the latest capabilities.
Based on the characteristics of claude-3-5-sonnet-20240620, first validate small tasks whose results can be checked.
You can ask directly: Using the charts and raw data, write a customer-facing explanation of the changes, retaining metric units and time ranges, and identify the parts that cannot be explained from the materials.
Keep the fixed-version invocation ID; verify numbers against the raw data, and separate visual observations from causal conclusions.
Use the full model ID claude-3-5-sonnet-20240620, first confirm the public request format and available parameters on the API page, then connect the application. Retain result parsing, exception handling, and relevant evidence, and use the same set of real samples to assess whether it is suitable for continued use.
Before formal use, understand the scope of output quality and capabilities.
Answers to common questions when using claude-3-5-sonnet-20240620.
No. They are different dated versions of Claude 3.5 Sonnet, and you should use each one's full ID when making calls. Keep the original version configuration when maintaining older applications; when preparing to switch, compare answers and formatting using the same materials, and do not treat the two dates as interchangeable aliases.
Combine a text question with clear images in the text-and-image content blocks supported by the selected endpoint, and specify the areas of interest and expected output. Chat Completions uses text and image_url, while Messages uses its native image content blocks; do not use PDF or video URLs as image_url.
Applications that already use the OpenAI messages structure can use Chat Completions; if you need Claude-native content blocks, thinking, or tool_use/tool_result workflows, check Messages API support for this model. Handle the two request, response, and parameter formats separately, and retain the full model ID.
Do not infer this from the model family name. This dated version and later Sonnet models must be assessed separately, and reasoning_effort in generic requests does not mean it has the corresponding thinking level. If a task depends on specific reasoning controls, choose a specific model that explicitly supports that capability.
It is better suited for maintaining existing version configurations and comparison testing. This model has been retired from Anthropic-operated platforms, and the official recommended replacement is Claude Sonnet 4.6. This platform's two calling endpoints still list this ID, but that does not mean it will remain available permanently. New projects should also evaluate newer candidate models and decide on a migration plan based on real text-and-image tasks and business acceptance results.
Choose a development approach or application suited to this model and follow its setup guide.
OpenAI Chat Completions API
SDK installation, authentication and examples
Claude Code CLI Setup Guide
Coding tool setup · requires a Coding Plan application key
Using Ace Data Cloud with Cherry Studio
Chat client setup · Base URL, API key and model
Using Ace Data Cloud with ChatBox
Chat client setup · Base URL, API key and model