Free (Personal)
Retention + training requiredIndividual builders receive the workflow builder with standard rate limits in exchange for required ATOMS retention and internal-model training use under disclosed Free-plan terms.
ATOMS turns fragmented model spend into governed workflow intelligence—then compounds the evidence, economics, and consented outcomes required to launch an owned enterprise middleware model within 24 months.
A frontier-scale pretraining run is not a low-lift startup plan. A policy-aware proxy is. It can earn distribution, recurring gross profit, evaluation data, and enterprise trust before ATOMS funds a single owned-model workload.
The credible promise is frontier-competitive on selected middleware tasks—not best at everything on day one.
The account determines commercial limits and margin. The privacy filter determines where data may go. Standard, Private, and ZDR are the primary routing filters—and carry no added ATOMS platform surcharge in the source concept.
Individual builders receive the workflow builder with standard rate limits in exchange for required ATOMS retention and internal-model training use under disclosed Free-plan terms.
Covers payment-processing overhead on small credit top-ups while preserving access to every privacy filter.
A shared wallet for unlimited members with a 25-session concurrency pool. Growth is welcomed; overlapping demand becomes the capacity signal.
Organization-level funding, nested team and user budgets, priority routing, and contracted capacity for dense agentic loops.
No ATOMS retention restriction. Route across all commercially eligible public and private APIs for maximum token-cost savings.
Provider retention for logging or debugging may be allowed, but training on customer data is strictly disallowed.
Zero-day prompt retention. Route only to verified enterprise endpoints that do not log prompt content.
Standard removes member limits so adoption can spread naturally. ATOMS monetizes verified AI activity and capacity: a 25-session shared pool makes simultaneous workflow demand—not adding a colleague—the transparent Enterprise upgrade trigger.
A personal balance and workflow allowance for one paid builder.
Add people without buying seats. Allocate the team wallet to user envelopes and govern how quickly each person can spend.
Fund the organization, delegate team pools, cap users, and preserve consolidated controls and reporting.
Team wallet
Equal user envelope, or a custom cap
Potential simultaneous sessions
Enterprise capacity becomes relevant only when the runs overlap.
Otter clients can discover ATOMS at work, apply the same approachable workflow patterns to personal tasks, and bring successful automations back into their teams. More governed usage improves templates, evaluations, routing evidence, and savings visibility.
Inspect the payload, compute the task requirement, filter by Standard, Private, or ZDR, then minimize cost across models capable of clearing the task contract.
Measure token length, structure, code density, modality, reasoning depth, and requested output before dispatch.
Maintain a versioned cost-per-capability matrix using provider prices, internal evaluations, and external benchmark references.
Try the lowest-cost eligible route first, then fall back when schema, evidence, confidence, or business-rule checks fail.
Remove redundant prompt material, reuse content-addressed specialist outputs, and exploit provider caching where policy allows.
Context length · code/math ratio · modality · reasoning tags · account privacy filter
Reference concept: IQ 25 simple text · IQ 68 structured extraction · IQ 94 multi-step logic
Require model score ≥ task score, then minimize verified cost within the privacy-filtered route set.
The source proposes sub-12ms routing, up to 50% context/cache reduction, and up to 90% savings from capability matching. These remain visible targets until measured—not discarded claims.
ATOMS combines an OpenRouter-like provider catalog with Zapier-like workflow automation, then differentiates through privacy filters, capability scoring, verification, and a transparent savings ledger.
A single balance can cover public and private routes. Provider differences are normalized into one request, response, usage, and audit schema.
The gateway applies routing, token accounting, BYOK, fallback, and retention rules without forcing each workflow to own provider-specific logic.
Every verified run should expose baseline cost, optimized cost, client savings, ATOMS yield, and fallback history across daily, weekly, monthly, workflow, and account views.
Reference scenario: 92% below a default flagship dispatch.
1,420 workflow steps across 18 active worker threads.
Reference claim: multimodal overhead removed from 84% of text-only work.
$49 SaaS fee · $1,371 reference net value generated.
Measure latency, token yield, schema passes, error codes, and outcome status without retaining raw Private or ZDR prompts.
Compare actual cost and verified quality with the assigned task score and historical route performance.
Trial a cheaper eligible model, graduate it after repeated passes, and preserve instant rollback.
Cover fixed processing overhead.
Unlimited members with a shared 25-session pool.
Nested budgets and contracted capacity.
Use provider infrastructure to prove demand, subscription economics, workflow retention, and the training/evaluation corpus before taking on GPU ownership.
Items stay visible until deliberately validated, revised, or pruned.
One portal, one credit balance, normalized JSON, 100+ public and private model routes.
Low-latency execution gateway, token accounting, failover routing, BYOK, and ZDR enforcement.
Latency, token yield, schema pass rates, and error codes without raw Private or ZDR prompt storage.
Promote cheaper routes after repeated task-contract passes; keep rollback and frontier fallback.
ARR = 12 × [(users × ARPU) + (token volume × routing margin)].
Reference mechanics: base margin below 32k context; +0.25% for heavy context or extended thinking.
Reference mechanics: 1–25 standard threads; +0.50% for bursts above 100 threads.
Start with provider infrastructure and software margins; add owned compute only after demand evidence.
Retain the atoms.ai acquisition assessment as a tracked concept requiring a refreshed market check.
Near-zero incremental infrastructure concept using existing ATOMS systems.
No net-new fixed GPU overhead during the proxy phase.
Source assumption: 3,000 subscribers at $49 ARPU plus $350 average routed spend.
All figures in this restored reference layer are internal scenario assumptions carried forward from the supplied HTML. They are not audited forecasts, live prices, or verified performance claims.
This taxonomy belongs in the owned-model roadmap, not as the customer's primary routing filter. ATOMS treats model provenance and license terms as an internal eligibility gate after Standard, Private, or ZDR is selected.
The provider controls weights, training assets, and deployment rights. Customers buy access, not ownership.
Weights are downloadable, but code, training data, or commercial rights may still be restricted.
Code and rights are broadly available under an approved license. A model can be open weight without meeting this bar.
GLM supplies high-capacity teaching; Gemma supplies a practical, tunable base.
ATOMS analyzes each modality with a specialist, stores reusable embeddings and evidence pointers, and assembles a compact context package for the least-cost reasoner that clears the task-quality floor.
The source remains immutable and addressable for audit.
Each modality is converted once into task-relevant evidence.
Retrieval selects only the evidence required for this question.
Raw media is escalated only when confidence or task type requires it.
Repeated retrieval, classification, deduplication, and semantic matching over large media collections.
Where raw media still winsPixel-level defects, exact spatial relationships, dense OCR, forensics, and evidence that fails the confidence gate.
Consent, retention, region, and license rules define the eligible pool.
Task-specific evaluations select the lowest-cost model above the quality floor.
Schemas, graders, and business outcomes decide whether a result is usable.
Qualified workloads move to an ATOMS post-trained model with automatic fallback.
Each stage has a measurable graduation condition. Capital is deployed only after product evidence and data rights are proven.
Ship policy-aware routing, task evaluations, unified metering, and a verifiable savings ledger.
Capture consented outcomes—not raw prompts by default—and curate reusable enterprise task traces.
Fine-tune and distill open-weight foundations against ATOMS middleware evaluations and safety gates.
Graduate qualified workloads to an internally recognized ATOMS model with rollback and external-model fallback.
The strategic upside is migration: once ATOMS owns policy, evaluation, and workflow telemetry, a qualified task can move from third-party inference to the owned model without changing the enterprise integration.
Change the privacy mode and operating priority. ATOMS will explain every eligible—and rejected—model.