SECURITY & TRUST

Simple outside.
Explicit inside.

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

Trust is a collection of small proofs.

Each behavior below is attached to an API contract, account boundary, public notice, or operational surface.

01
Keys

Environment-first

Customer keys move through controlled flows. Documentation never asks developers to paste a secret into chat, source, or logs.

02
Routes

Exact by default

Requested and resolved model identity stays visible. An unsupported or mismatched route fails closed.

03
Spend

Bounded lanes

Interactive membership and prepaid Agents use separate authorization and billing policies.

04
Processing

Disclosed

Supplier processing is documented so developers can decide what request content is appropriate.

PROCESSING BOUNDARY

Know where the request can go.

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 →
01Your applicationenvironment-held key
02Newton’s gatewaypolicy + route evidence
03Inference processordisclosed handling

PUBLIC EVIDENCE

Read the source of truth.

Security details should be available before a procurement call or support ticket.

PRECISE QUESTIONS. PUBLIC ANSWERS.

Start with the contract.

Use the reference, policies, and service status to evaluate the exact control you need.

Open docs →
Advertising measurement

Newton’s can share limited page and signup events with Meta to measure ads. Prompts, outputs, API keys, and payment details are never included. Privacy choices