Typed decisions, with a contract
A dedicated evaluation surface takes a state and 1–64 named questions. It preserves stable answer keys, declared types, and usage metadata.
This note explains the design being adapted. It does not announce a shipped Noemad API, a verified model deployment, or a currently available promotion.
The subject
A dedicated evaluation surface takes a state and 1–64 named questions. It preserves stable answer keys, declared types, and usage metadata.
What this means for Noemad
Use a separate adapter and endpoint for noul, choice, and score results. Validate ranges and returned IDs before accepting a result. A temporary zero-cost upstream offer must not become a permanent Noemad pricing promise.
Before this can go live
- Implement the contract behind the relevant frontend controls.
- Validate ownership, limits, failure recovery, and the exact provider configuration.
- Publish authoritative availability and customer terms before accepting any payment.
- Keep request, payment, usage, and result records linked to one logical operation.
What you can explore now
The interface includes the corresponding documentation and navigation. Local samples stay clearly marked, and no service availability or account balance is inferred from a static catalog.
Explore the related reference