早鸟价(12 月 25 日截止),订阅期间一直锁定:Go $10/月(原价 $20),Plus 用 Opus 5.5 只要 $30/月(原价 $50)立即订阅 →
文本对话1M 上下文

Claude Fable 5

在线试用 Claude Fable 5,体验细致写作、谨慎综合和高质量长篇内容创作。在接入 API 前,查看 token 定价并测试提示词。

价格 / 100 万 token省 50%
官方AIReiter
输入$10.00$5.00
输出$50.00$25.00
缓存读$1.00$0.50
缓存创建$12.50$6.25
说明文档
输入
限制回复长度。推理模型也会把思考计入其中。
claude-fable-5
输出

A codebase you don't know is a risk, not a hurdle. The plan should burn down that risk in order: understand, run, trace, spike, then make the change small enough that "production-ready" is a property you can demonstrate, not a hope.

Here are the first five steps, with the evidence you collect at each.

Step 1 — Get it building and the baseline green (half day)
Read the README, the manifest(s), the CI config, and any architecture docs. Boot the app locally, run the full test suite, run the linter/typechecker.
Evidence: The exact commands that reproduce a clean build and a passing test suite from a fresh checkout (recorded output, not memory of it). A one-page map you wrote yourself: where the entry points are, the layers, the build/test toolchain, and the main risks to your feature (e.g. "this touches cron jobs and payments").

Step 2 — Trace the smallest end-to-end slice that resembles your feature (half day)
Don't start with your feature. Pick a neighboring one that already works and follow it from entry to persistence. Note the conventions along the way: how errors surface, how config is injected, how logging is done, how tests are written.
Evidence: An annotated trace — file → function → what it does — for that slice. A written list of "conventions I must follow" (not intuitions; things you observed in real code). A named shortlist of the 3–5 files you will actually touch. If you can't produce this trace, you're not ready to write code.

Step 3 — Spike the core path (day 2)
Build the ugly version: hardcoded values, no error handling, no tests. The purpose is to confirm the path you traced in step 2 is real and to surface what you didn't know you didn't know.
Evidence: A working spike demonstrating the feature's central data path, alongside a list of every assumption the spike broke and what you corrected. That correction list is the most valuable document in this whole plan.

Step 4 — Write the contract before the code (half of day 2 / day 3)
Once the spike proves the path, pin down what production needs: the inputs/outputs, the error cases, where it sits in the conventions from step 2. Then write the tests — they'll be red, but they're the specification.
Evidence: A one-to-two-page design doc, an agreed interface/API shape (with the team if there is one), and a red test suite that encodes intended behavior. If you can't write the contract without consulting the code, you haven't finished step 2.

Step 5 — Implement in small, verified increments (days 3–4)
Replace the spike with the real thing in small commits, each one keeping the suite green, leaning on the existing patterns. Run lint/tests/typecheck per commit — CI, not just locally — and exercise the actual path against a real instance (staging or a local environment that isn't stubbed).
Evidence: A branch with progressive commits, each green in CI; coverage on the new code; something that proves it works against reality (a test result, a log trace, a screenshot); and a review by at least one person who knows the codebase. The review counts as evidence — an unfamiliar codebase has tribal knowledge you cannot extract from the files alone.

Steps 6+ would be the things that actually make it "shipped": a migration plan and its rollback, feature flagging, observability, the release and post-release verification. But the first five get you to a reviewed, green, working slice in staging — which is the point at which you can say "this will work in production" with evidence behind it, instead of a guess.

生成耗时42.7s
输入 Token134
输出 Token2,354
token / 秒55.13
TTFT-

运行会以此提示词打开 AI Chat,需要登录并有积分。

模型详情

在 Playground、API 请求和内部工作流中使用相同的模型 key。

模型 ID
claude-fable-5
供应商
Anthropic
协议
Anthropic Messages
上下文窗口
1,000,000 Token
最大输出
128,000 Token
输入 Token
500 credits / 1M Token
输出 Token
2,500 credits / 1M Token
缓存读取
50 credits / 1M Token
缓存写入
625 credits / 1M Token

Claude Fable 5 能做什么

当你需要结构、语气、综合能力和修订质量比快速初稿更重要的细腻长篇创作时,选择 Claude Fable 5。

长篇写作

以一致的结构和语气撰写连贯的报告、叙述和文档。

细腻改写

在改变语气、受众、长度或编辑侧重点的同时保留原意。

资料综合

将多份文档整合为易读的简报,同时不丢失重要差异。

编辑修订

在生成更强版本之前,先对结构、清晰度、衔接和论证质量进行评估。

Claude Fable 5 使用场景

最适合重视细腻表达、连贯性和谨慎修订的编辑、研究和沟通工作流。

报告与白皮书

构建具有连贯论点和一致术语的长文档。

品牌与编辑工作

根据明确受众调整语气和结构。

研究简报

整合研究发现,同时保留不确定性和来源差异。

文档修订

通过评估、重组和改写来改进草稿。

用 3 步试用 Claude Fable 5

  1. 01

    选择你的设置

    设置模型支持的响应控制和上传选项。

  2. 02

    发送提示词

    描述任务,添加相关上下文,并查看流式响应和 token 使用情况。

  3. 03

    连接 API

    使用文档中的端点和你的 API key,将同一模型接入你的产品。

使用 Claude Fable 5 API 构建

管理 API 密钥 →

从交互式测试到生产集成,使用可预测的控制和用量报告顺利过渡。

01熟悉的协议

使用为此模型配置的 API 协议,包括可用的流式传输。

02用量可见性

在每次响应后跟踪输入 token、输出 token 和已消耗的积分。

03模型专属控制

传入支持的生成参数,而不是依赖通用默认值。

04一个账户和余额

通过同一个 AIReiter 账户和计费系统测试并使用受支持的文本模型。

常见疑问

01Claude Fable 5 最擅长什么?

此处将其定位为适合长篇写作、细腻改写、综合整理和编辑修订。

02Claude Fable 5 能保留特定写作风格吗?

提供具有代表性的示例和明确的语气约束,然后在游乐场中比较修订结果。

03Claude Fable 5 仅适用于创意写作吗?

不,它也可以用于报告、研究简报、文档和其他结构化长篇工作。

04Claude Fable 5 如何定价?

当前的输入和输出 token 费率显示在 playground 上方。

05我可以通过 API 使用 Claude Fable 5 吗?

可以。请按照链接中的 API 文档操作,并使用页面上的 model ID。