NEWTON’SEnvironment-first
Customer keys are created and shown through controlled flows. Documentation never asks developers to paste secrets into chat, source, or logs.
SECURITY & TRUST
Simple outside.
Explicit inside.
A gateway earns trust by making its boundaries legible: how keys move, what route ran, what was charged, and what happens when a condition is not safe to continue.
CONTROL SURFACES
Trust is a collection of small proofs.
These are product behaviors, not decorative promises. Each one is reflected in the API contract, dashboard, or public status surface.
Exact by default
The requested model and resolved model remain visible. Newton’s does not silently substitute an undisclosed route.
Bounded lanes
Membership and prepaid Agents use separate policies. Agents authorization stops when the funded balance cannot cover the request.
Disclosed supplier
Newton’s currently uses Yunwu as an inference processor. Requests may be passed to model providers; review the privacy notice before sensitive production use.
PUBLIC EVIDENCE
Read the source of truth.
Security details should be discoverable without a sales conversation.
Receipt contract
See request IDs, model identity, usage, billing mode, fallback status, and settled cost behavior.
Read receipts →Fair-use boundaries
Understand interactive membership, prepaid Agents, rate limits, concurrency, and abuse protections.
Read fair use →Privacy and processing
Review what Newton’s processes, why suppliers may receive requests, and what developers should avoid sending.
Read privacy →Ask a precise question.
For security reviews, start with the public contracts and contact the team with the exact control you need to evaluate.