Environment-first
Customer keys move through controlled flows. Documentation never asks developers to paste a secret into chat, source, or logs.
SECURITY & TRUST
A gateway earns trust by making its boundaries legible: where the key lives, what route ran, how the request settled, and when the system refuses to continue.
CONTROL SURFACES
Each behavior below is attached to an API contract, account boundary, public notice, or operational surface.
Customer keys move through controlled flows. Documentation never asks developers to paste a secret into chat, source, or logs.
Requested and resolved model identity stays visible. An unsupported or mismatched route fails closed.
Interactive membership and prepaid Agents use separate authorization and billing policies.
Supplier processing is documented so developers can decide what request content is appropriate.
PROCESSING BOUNDARY
Newton’s currently uses Yunwu as an inference processor. Request content may pass through that processor and onward to model providers. Start with non-sensitive data and review the privacy notice before production use.
Read the processing notice →PUBLIC EVIDENCE
Security details should be available before a procurement call or support ticket.
PRECISE QUESTIONS. PUBLIC ANSWERS.
Use the reference, policies, and service status to evaluate the exact control you need.