Skip to content
MetaioLab MetaioLab Docs
Open metaiolab.com

Claude Code

Claude Code is the clearest example of why MetaioLab should not be described as “OpenAI-compatible only.”

What was verified

Section titled "What was verified"

On March 8, 2026, the Anthropic-compatible HTTP endpoint was tested successfully at:

  • POST https://metaiolab.com/v1/messages
  • model used: gpt-5.4
Section titled "Recommended route for Claude Code"
  • Client base URL: https://metaiolab.com
  • Actual request route used by Anthropic-style clients: /v1/messages
  • Model discovery route: /v1/models

Do not set ANTHROPIC_BASE_URL=https://metaiolab.com/v1 unless the specific client expects that format. In the normal Anthropic pattern, the client appends /v1/messages itself.

Environment setup

Section titled "Environment setup"
Terminal window
export ANTHROPIC_BASE_URL="https://metaiolab.com"
export ANTHROPIC_API_KEY="sk-your-token"

Why this works

Section titled "Why this works"

MetaioLab’s Anthropic-compatible path responds correctly to:

  • x-api-key
  • anthropic-version
  • Anthropic-style messages payloads

Operational advice

Section titled "Operational advice"
  • Publish at least one verified model in customer onboarding docs.
  • Right now, gpt-5.4 is a validated example.
  • Keep your customer instructions explicit: Claude-style client → Anthropic-compatible path.

Troubleshooting

Section titled "Troubleshooting"

Claude Code still hits Anthropic directly

Section titled "Claude Code still hits Anthropic directly"
  • Re-check ANTHROPIC_BASE_URL
  • Re-run /status
  • Restart the terminal session if needed

Authentication fails

Section titled "Authentication fails"
  • Make sure the value is your MetaioLab token, not an Anthropic console key.
  • Make sure the token is enabled for the target model.

Model list is empty

Section titled "Model list is empty"
  • Verify the token can access at least one Claude-compatible model mapping.

References

Section titled "References"