Changelog

Add Kimi K2.5 and Qwen 3 Max (0123)

<p align="center"> <img src="https://apertis.ai/ask-ai.png" alt="ask-ai-image" width="250" /> </p>

What's new

• AI-powered documentation search
• Ask questions in natural language and get precise, context-aware answers from Apertis docs.
• No more manual searching or jumping between pages.
• Built for integration
• The Ask AI experience is powered by the same APIs you can use in your own product.
• Easily embed an “Ask AI” assistant into your docs site, dashboard, or developer tools.
• Developer-friendly by design
• Optimized for technical questions, code usage, and API workflows.
• Responses are grounded in official documentation to reduce hallucinations.
• Faster onboarding & troubleshooting
• Help users discover features, understand APIs, and resolve issues instantly.
• Ideal for reducing support load and improving developer experience.

Why it matters

Ask AI turns documentation from a static reference into an interactive developer assistant. Whether you're building an internal tool, a public SDK site, or a customer-facing app, you can now offer the same AI-powered doc experience with minimal integration effort.

Get started

• Try Ask AI directly in Apertis Documentation
• Follow the integration guide to add Ask AI to your own application

• Before: 30-55ms
• After: 5-10ms (cache hits) / 15-25ms (cache misses)
• Estimated improvement: 40-80% latency reduction

Add comprehensive SDK features (v0.2.0) New Features:

• Vision/Image support with create_with_image() convenience method
• Audio input/output support
• Video content support
• Web Search with create_with_web_search() convenience method
• Reasoning Mode support (glm-4.7)
• Extended Thinking (Gemini) support
• Models API (list, retrieve)
• Responses API (OpenAI format)
• Messages API (Anthropic format)
• Rerank API (BAAI/bge-reranker-v2-m3, Qwen models)
• Helper utilities for base64 encoding

Includes 81 unit tests covering all new functionality.

PyPI Package: https://pypi.org/project/apertis/

Fix API response compatibility issues (v0.1.1)

• Make id, object, created fields optional in ChatCompletion
• Make id, object, created, model fields optional in ChatCompletionChunk
• Make Usage fields optional to handle empty usage objects in streaming
• Fix streaming by using httpx send() with stream=True instead of stream context manager

Tested with real API calls:

• Chat completions: working
• Streaming: working
• Embeddings: working
• Tool calling: working