Anthropic
Claude's Messages API behind the same policed-route pattern as the OpenAI proxy, cache-tier pricing included.
Where Anthropic lands
Composite scores out of 10, from benchmark runs where every provider faces the identical task corpus. Rank is within that capability's field. Full method: how we measure.
Anthropic sits outside the web-access benchmark — the search/scrape/crawl corpora don't exercise a model inference API, so this page carries catalog facts without a scorecard.
The honest pitch
Pick it for Claude's models specifically, with prompt-cache pricing tiers read straight from each response and billed to the one balance.
Skip it for anything outside the gateway's admitted surface: only a fixed, current Claude model list and a closed set of request fields are admitted here.
About Anthropic
The Claude Messages API is reachable through a route that mirrors the OpenAI proxy’s shape: a fixed, current model list, a closed set of admitted request fields, and per-account tracking of the files and message batches a customer creates. Anthropic’s own usage counts already reflect prompt-cache reads and writes, so billing reads those tiers directly from the response rather than re-deriving them. Batches don’t carry a completion webhook on Anthropic’s side, so they settle on a recurring poll instead; an account can also register its own Claude API key to bill that provider directly.
Reaching it through NativePort
Identical paths, parameters and responses to Anthropic's own documentation — the gateway holds the upstream credential and meters your balance at Anthropic's real published usage price.
curl https://api.nativeport.ai/anthropic/<native-path> \ -H "Authorization: Bearer $NATIVEPORT_API_KEY"