Appearance
Parameter sanitization
Rikaii normalizes OpenAI-compatible chat payloads before they reach any upstream provider. This is a developer-facing reliability feature: your integration can send one JSON shape; the platform enforces caps and removes fields that would otherwise produce 400 Bad Request or silent drops on non-OpenAI endpoints.
Silent capping (token limits)
Each catalog model has a maximum generation length enforced by the upstream vendor. If your request asks for more than the target model allows—for example:
json
{ "max_tokens": 500000 }when the routed model only supports 64,000 output tokens, Rikaii silently caps the effective limit to 64,000 (and proceeds) instead of forwarding an invalid value that could fail the whole request.
The same principle applies when you use max_completion_tokens (OpenAI’s newer knob): the platform resolves max_tokens and max_completion_tokens to a single safe outbound value per upstream rules.
You are not required to vendor-specific limit tables in your app; you may still choose conservative limits for latency and cost.
Parameter stripping (cross-provider compatibility)
When a request is routed to Anthropic, DeepSeek, or other non-OpenAI HTTP APIs, fields that exist only in OpenAI’s schema may be removed or mapped rather than forwarded verbatim.
Examples of parameters that may be stripped or ignored when the active upstream does not support them include:
logit_biasseed- Other OpenAI-only knobs that have no stable equivalent on the target API
The platform does not require you to branch your client code per vendor for these cases: unsupported keys are handled so that the same payload can move between providers behind your routing rules.
Tool calling, streaming, and core sampling fields (temperature, top_p, stop, etc.) are forwarded or mapped according to the active provider adapter.
What you should do as an integrator
- Prefer documented fields in Chat completions.
- Treat HTTP 200 responses as authoritative; assume limits may be clamped without a warning field.
- For strict reproducibility (
seed,logit_bias), pin routes to providers that support those features via BYOK or explicit routing configuration.