Newton’sKeys
Environment-first
API keys move through controlled flows. Documentation never asks builders to paste a secret into chat, source, or logs.
SECURITY & TRUST
Clear controls.
Visible results.
See how Newton’s protects API keys, processes requests, records model usage, and stops spending when credits run out.
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.
Models
Exact by default
The requested and resolved model stay visible. If Newton’s cannot confirm the requested model, the request returns an error instead of using another model.
Credits
Prepaid boundary
A request needs enough purchased credits before it can run. Newton’s does not create an open-ended usage bill.
Processing
Disclosed
Provider processing is documented so builders can decide what request content is appropriate.
PROCESSING BOUNDARY
Know where your request can go.
Newton’s sends request content to the configured inference provider for the selected model. Start with non-sensitive data and review the privacy notice before production use.
Read the processing notice →01Your applicationenvironment-held key
→02Newton’s APIrequest controls + Activity
→03Inference providerdisclosed handling
PUBLIC EVIDENCE
Read the source of truth.
Security details should be available before a technical review or support ticket.
API CONTRACT
Activity and response recordsRequest ID, requested and resolved model, fallback state, usage, cost, and remaining credits.
↗POLICYUsage boundariesPrepaid spend, rate limits, concurrency, and restriction behavior.
↗NOTICEPrivacy and processingWhat Newton’s processes, why a provider may receive a request, and what builders should avoid sending.
↗OPERATIONSPublic service statusAPI, account creation, and credit-purchase availability.
↗PRECISE QUESTIONS. PUBLIC ANSWERS.
Start with the contract.
Use the reference, policies, and service status to evaluate the exact control you need.