Picsart API Platform
← All models

Claude Opus 5

New

Anthropic · Text · Image → Text

Next-generation Opus model for complex reasoning and long-form analysis.

Model ID: claude-opus-5Workflow: claude/v1/messages
Vision
Try on Playground ↗

Overview

Alongside the unified model APIs, we expose compatibility APIs that take each vendor's original parameters exactly as the vendor defines them — nothing renamed, nothing reshaped on the way through.

That makes them the shortest path onto Picsart if you already work with the vendor directly: the request bodies you've already written keep working as they are. You keep their parameter names and defaults, and you get the vendor's full parameter set rather than the subset that is shared across every model.

The cost is that a request is written for one vendor — switching models later means rewriting it, and results come back in the vendor's own shape. When you'd rather write once and change models freely, use the unified API.

Make a request

Call the workflow with ai.apis.run() in TypeScript, or hit /workflows/{workflow}/execute directly — params is passed through untouched either way.

These endpoints are addressed by workflow name rather than model id: the one in this model's header, since one model runs as one workflow. Authentication is unchanged — your Picsart API key as a bearer token (see Authentication).

ts
import { createClient, ApiRunMode } from '@picsart/ai-sdk';

const ai = createClient({
  apiKey: process.env.PICSART_API_KEY,
  apiUrl: 'https://api.picsart.com',
});

// Calls the 'claude/v1/messages' workflow directly — params are sent as-is.
const { result, usage } = await ai.apis.run('claude/v1/messages', {
  model: "claude-opus-4-8",
  messages: [
    {
      role: "user",
      content: []
    }
  ]
}, {
  mode: ApiRunMode.SYNC,
});

console.log(result); // workflow-specific output
console.log(usage?.credits); // credits charged

Parameters

10 parameters, sent inside params. These are the vendor's own names, so they line up one-for-one with the vendor's documentation. Required ones must be supplied; the rest fall back to their defaults.

ParameterTypeRequiredDefaultDetails
model
Claude model to use
stringyes—
claude-opus-4-8claude-opus-5claude-opus-5-5claude-sonnet-4-5claude-sonnet-4-6claude-sonnet-5claude-sonnet-5-5claude-haiku-4-5claude-fable-5claude-fable-5-1
messages
Conversation messages
ClaudeMessageParam[]yes——
└role
Message role
stringyes—
e.g. user
└content
Message content: a string or an array of content blocks. Passed through to the provider as-is.
ClaudeContentBlock[]yes——
└type
Content block type
stringyes—
texttool_usetool_resultimagethinkingfiledocument
└text
Text content
stringno——
└cache_control
Cache control
objectno——
└id
Unique ID for the tool call
stringno——
└name
Tool name
stringno——
└input
JSON input for the tool
string | number | integer | boolean | array | objectno——
└tool_use_id
The corresponding tool_use id
stringno——
└content
Tool result content
ClaudeToolResultContentText[]no——
└thinking
Internal thinking text
stringno——
└signature
Signature is required when echoing thinking back
stringno——
└source
Content source
objectno——
max_tokens
Maximum number of tokens to generate
numberno—
e.g. 1024
temperature
Sampling temperature, between 0 and 2
numberno1
0–2
system
System prompt as a string or array of syste blocks
string | number | integer | boolean | array | objectno——
tools
List of tools available to the model. Passed through to the provider as-is.
ClaudeToolSchema[]no——
└name
Tool name
stringyes——
└description
Short description of the tool
stringno——
└input_schema
JSON Schema for the tool input
string | number | integer | boolean | array | objectyes——
└type
stringyescustom—
tool_choice
Controls which (if any) tool is called by the model. "auto" lets the model decide; "any" forces a tool call; { type: "tool", name } forces a specific tool.
ClaudeToolChoiceToolParam | stringno——
service_tier
Specifies the processing type used for serving the request. Passed through to the provider as-is.
stringno—
autoflexprioritydefault
context_management
Context management options. Passed through to the provider as-is.
objectno——
└edits
List of context management edits to apply
ContextManagementEdit[]yes——
└type
clear_thinking_20251015 or clear_tool_uses_20250919
stringyesclear_tool_uses_20250919—
└trigger
When to trigger this edit
objectno——
└keep
What to keep when applying the edit: a criterion object or a keyword such as "all".
ContextCriterion | stringno——
└clear_at_least
Minimum to clear when applying the edit
objectno——
└exclude_tools
Exclude these tool names from clearing
string[]no——
└clear_tool_inputs
Whether to clear the tool uses
booleannofalse—
options
objectno——
└safety_checks
Safety check settings
objectno——
└enabled
Whether to run content moderation. Defaults to true.
booleanno——
└drive
Save result to Picsart Drive
objectno——
└name
File name in Picsart Drive
stringyes——
└attributes
Custom attributes to attach to the file
objectno——
└folder
Target folder in Picsart Drive
objectno——
└inputs_transformation
Input transformation settings
objectno——
└downscale_oversized_images
Whether to downscale oversized input images. Defaults to false.
booleanno——

Response

Over HTTP the output arrives inside a status envelope, at response.result. ai.apis.run() unwraps that envelope for you and resolves to { result, usage } instead. Either way the resultitself is the vendor's own shape.

json
{
  "result": {},
  "usage": {
    "credits": 1
  }
}