How do I access Claude Fable 5.2?
Pick it in Claude, or use claude-fable-5-2 in the Claude API.
In Claude, open the model picker and check that it shows the full version number before you start. If the model is missing, check whether your plan or seat includes Fable access. Anthropic describes eligible paid plans and seats in its release announcement. The announcement does not publish a universal message allowance you can apply to every account.
Which route should I check first?
- Interactive work
- Start in Claude if you want to work through a document or task in chat. Check the model picker in the workspace you intend to use.
- Repeatable jobs
- Start with the Claude API if you need to send requests from a script. Use the exact model ID in your request.
- Existing cloud integration
- Use the ID listed for your provider in the official model ID table. Don't reuse an ID from another provider.
A three-step check before a real job
- Confirm the route. Record the workspace or provider and the exact model shown there. If you can't select it in Claude, start with the plan or seat. If a script can't reach it, check the provider's model ID and the project attached to your credential.
- Check data handling. The Claude Platform overview specifies 30-day retention and says zero data retention requires express authorization from Anthropic. If your project requires zero retention, stop before sending any real data and confirm that authorization for your setup.
- Run a small, non-sensitive trial. Ask it to extract the owner and due date from this made-up note: “Nora owns the invoice check; the note gives no deadline.” A useful result names Nora and leaves the date unknown. In a script, record the model returned by the API alongside the result. This checks the request path and your handling of missing fields; it doesn't establish a success rate for real jobs.
For example, if your team plans to extract dates from hundreds of internal notes, use the sample first to verify that your code accepts a missing date. Then check retention before moving to real notes. That separates a problem in your workflow from an access problem, without uploading any internal material to find out.