Skip to content

Conversation

@shingonoide
Copy link
Contributor

Summary

  • Refactor ZHIPU adapter to ZAI adapter
  • Implement namespace-based routing for regular vs coding endpoints
  • Regular models: glm-4.6 → credit-based API
  • Coding models: zai::glm-4.6 → subscription API (auto-routed)
  • Add clean example c07-zai.rs without migration details
  • Simplify user-facing API by hiding endpoint complexity

Test plan

  • Test with example: ZAI_API_KEY=... cargo run --example c07-zai
  • Verify regular API routing (glm-4.6)
  • Verify coding API routing (zai::glm-4.6)
  • Update adapter tests from tests_p_zhipu to tests_p_zai
  • Ensure backward compatibility

- Rename zhipu adapter to zai adapter
- Implement namespace-based routing for regular vs coding endpoints
- Regular models: "glm-4.6" → credit-based API
- Coding models: "zai::glm-4.6" → subscription API
- Add comprehensive example c07-zai.rs
- Update adapter kind detection to handle "zai" namespace
- Remove dual-endpoint complexity from user-facing API
@jeremychone jeremychone merged commit 5a1df3c into jeremychone:main Oct 22, 2025
@jeremychone
Copy link
Owner

@shingonoide Thank you for the clean commit. I trust that zai should be the right name for the zhipu service.

@jeremychone jeremychone added the PR-MERGED Added for PR that somehow did not get the Merge label Oct 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

PR-MERGED Added for PR that somehow did not get the Merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants