Claude
Anthropic's model family, strong at long-context coding work.
Claude is Anthropic's family of large language models. For vibe coders it is the model behind Claude Code and Claude.ai, and it handles large codebases and long instructions well.
At a glance — Claude Opus 4.1
- Cost
- $15.00 in · $75.00 out per 1M tokensPremium
- Memory
- 200K tokens — about 300 pages
- Reads
- Text · Images · Files
- Can do
- Use tools (agents)
- Structured output (not supported)
- Thinking mode
- Reliability
- 100.00% uptime, last 24h
- Released
- Aug 5, 2025
Advanced details
- API model ID
anthropic/claude-opus-4.1- Max output
- 32K tokens
- Cached input
- $1.50 per 1M
- Knowledge cutoff
- 2025-01-31
- Tokenizer
- Claude
Providers
The same model, hosted by different companies. OpenRouter picks one per request and falls back to the next if it fails.
| Provider | Input /1M | Output /1M | Cached /1M | Max output | Uptime 24h |
|---|---|---|---|---|---|
| Amazon Bedrock | $15.00 | $75.00 | $1.50 | 32K | 99.94% |
| Google · global | $15.00 | $75.00 | $1.50 | 32K | 100.00% |
Supported parameters
- include_reasoning
- max_tokens
- reasoning
- stop
- temperature
- tool_choice
- tools
- top_k
- top_p
Live from OpenRouter, refreshed hourly.
Official apps
Use it in
- Cursor
- Visual Studio Code· via the Claude Code extension
- GitHub Copilot· in the model picker
- Continue· bring your own key
- Aider· bring your own key
- Devin Desktop· formerly Windsurf
- WebStorm· via JetBrains AI Assistant
- Kilo Code· bring your own key
- OpenCode· bring your own key
- OpenRouter· one API for every model
- OmniRoute· self-hosted gateway
- Lovable· powers the app builder
- Replit· powers Replit Agent
Pairs well with
MCP Servers
Frameworks
Templates
Starter prompts
Copy one, fill in the brackets, and paste it into your tool.
Write a CLAUDE.md for this project · context
Read this repository and write a CLAUDE.md at its root for future sessions. Keep it under 60 lines and include only what you could not work out quickly from the code: - How to install, run, test and build (exact commands) - Where things live, and any folder with a rule attached - Conventions a newcomer would get wrong - Things never to do here Ask me about anything you are unsure of instead of guessing.
Find the root cause, not a patch · debugging
Something is broken. <symptom> [What you see, and the exact error message] </symptom> <steps> [How to make it happen] </steps> Do not fix anything yet. Find every place that calls the code involved, work out the actual cause, and explain it in two or three sentences. Then propose the smallest fix at the cause, plus one check that would have caught it.
UI that does not look AI-generated · design
Design [the page or component] for [who it is for]. Commit to one clear visual direction and tell me what it is in one line before you build. Avoid the defaults every AI tool reaches for: purple gradients, one font everywhere, three identical feature cards, emoji as icons. <constraints> - Use the design tokens and components already in this project - Mobile first; nothing may scroll sideways at 375px wide - Text must meet WCAG AA contrast in light and dark mode </constraints>
Plan before any code · planning
Before you write any code, read the files this touches and reply with a short plan: 1. What you will change, file by file 2. What could break, and why 3. How we will check it works Do not edit anything until I say go. <task> [Describe the feature or fix in a sentence or two] </task>
Key info
- Pricing
- Freemium
- Category
- Models
- Best for
- Beginner
Guided walkthroughs
Related reading
- Fundamentals
Reviewing code you did not write
You are going to merge a lot of code you did not type. Reviewing it is a different skill from writing it, and it is the one that actually keeps a vibe-coded…
Intermediate - Context engineering
Why your AI keeps forgetting what you told it
Models have a context window, a fixed budget of text they can consider at once. Everything competes for it: your instructions, the files you opened, the erro…
Intermediate