Skip to main content
Use this API when supported_endpoint_types in /v1/models for the current key includes anthropic. Read the API and model capability matrix first: the model, key group, and protocol must all match.
When to use MessagesUse this endpoint only when supported_endpoint_types includes anthropic. Use Chat Completions for OpenAI-compatible applications; if a model does not list anthropic, select one of its supported endpoints instead. not implemented normally means a protocol mismatch, not a temporary error.

Endpoint and minimum request

Use the protocol documentation for your Anthropic client for full fields, tools, streaming, and response schemas. Optional-field availability still depends on the selected model and its current capabilities.

Use the Anthropic SDK

The native SDK manages its required protocol headers. Pass a NexusAPI key to the SDK and set its Base URL without /v1:
The SDK appends /v1/messages. Do not set base_url to https://nexusapi.link/v1/messages, which can create a repeated path or 404.

Claude Code versus your own app

Troubleshooting

  • 401: Check that the key is correct, enabled, and has not been reset after exposure.
  • 404: Check whether an SDK has appended a second /v1.
  • 400: Verify with only model, max_tokens, and messages, then add optional fields gradually.
  • 500, not implemented: Confirm that supported_endpoint_types includes anthropic and that the request is using the matching endpoint.
For persistent errors, keep the Request ID and a redacted request, then use the self-check guide.