SN 114. Rank 10 of 32 by emission
SOMA
SOMA is a Bittensor subnet focused on context compression for AI agents.
In their own words · raw.githubusercontent.comSN114 SOMA is a packing contest for AI agents, where miners compete to fit the same conversation into a smaller suitcase so the model reads fewer words and the bill comes down without the answer getting worse.
The commodity, explained from zero
An AI agent is a program that asks a language model for the next step, over and over, sending it the whole conversation so far each time: the task, the files it opened, the commands it ran. Models charge per token, roughly per word, for everything they read, so an agent that works for an hour pays again and again to re-read its own history. The README says it plainly: "Modern AI agents repeatedly send large amounts of context to language models."
SOMA sells the packing: a compressor sits in front of the model and shortens the context. The unit of value is tokens not sent. The front page shows the price of one model, DeepSeek V4 Pro, at 1.32 dollars per million tokens without SOMA and 1.19 with it; four other models are marked "coming soon". A chart shows daily savings of up to about 220,000 tokens over five days, with no date.
The stated buyers are "AI teams" that are "paying for repeated context, not better intelligence". Three tools are listed: SOMARIZER for documents, a compressor for the OpenClaw coding agent, and a SOMA app. No customer is named.
Why it is on Bittensor at all
Decentralization here means the compressor is chosen by open contest rather than written in-house. Anyone can submit a compression method, and the network tests it on real coding tasks against the uncompressed version; the README describes the goal as "the maximum useful compression an AI agent can sustain while continuing to complete real work". On cost, ownership, or access against a centralized compressor, the materials say nothing yet. The comparison breaks here too: a packing contest judges the suitcase, but SOMA judges the trip, scoring whether the agent still finished the job.
How the work gets done
Miners submit compression code; they do not run servers, and the task's inputs and outputs change from one competition to the next. Validators, the judges who decide pay, run standard software-engineering benchmarks (SWE-bench Verified and two exploration and editing variants, weighted 50, 25 and 25 percent) with and without each miner's compressor, then score the trade between tokens saved and tasks still solved; output tokens count three times input, and ratio credit is capped at fourfold (read from the scoring formula). The winner of each benchmark combination takes that slice of emission, the subnet's share of new tokens, and a set portion is burned. The incentive page is dated 15 July 2026.
How you would know it works
The front page's savings chart and price comparison are the only artifact, and the chart carries no date. The docs describe SOMA Bench, a benchmark a reader can run, but publish no results table. SOMARIZER can be tried.
What is missing
There is no API reference; the docs cover miners, validators, and benchmarks only. The miner setup guide is from May 2026 and the incentive rules changed in July. Hardware is stated for validators, not miners, and registration cost is not given. There is no status page or SLA; support is a contact form, an email, and Discord. Nothing states how a miner is dropped.
Go deeper
Sources for this explainer
Metaphor: a packing contest for AI agents. Every claim is drawn from the evidence set or the subnet's own materials; "(inferred)" marks a conclusion rather than a quote. Corrections.
How we scored it
Four audiences, four questions each, scored on what a first-time reader can find in five minutes. Method in the rubric.
- subnet_name
- SOMA
- github_repo
- github.com
- subnet_contact
- x.com
- subnet_url
- thesoma.ai
- discord
- discord.gg
- description
- Context compression layer delivered through MCP infrastructure
- additional
- not set
Stakers and validators●●●●● 3.8
Should I allocate here? · rank 6 of 32 for this audience
Q1What it is●●●●● 4
Cut Token Costs Keep The Quality
with a per 1M token price for one model with and without SOMA, README says a subnet focused on context compression for AI agents, matches the chain description, unit is tokens saved rather than a stated commodity so took the lower score
Q2Who it is for●●●●● 3
Save Tokens
chart of daily token savings up to 220k over five days on the front page, no date, no named customers, no revenue statement
Q3How it resists gaming or fails●●●●● 4
named incentive page dated 15 Jul 2026 two clicks from the docs root with benchmark weights 50/25/25, a layered winner takes element share formula and a burn ratio, no anti-gaming section and no failure modes, a separate prompt editing rules page holds the miner rules
Q4Identity and documentation●●●●● 4
identity 6 of 7 (additional not set), github, url and discord fields are links, subnet_contact is the X account which the contact page also lists, no staking page but a SOMA Lock Program page states terms for locking alpha
Miners●●●●● 3.0
Can I compete, and what wins? · rank 25 of 32 for this audience
Q1What it is●●●●● 3
build a solution that reduces the amount of context processed by the agent while preserving its ability to successfully complete the underlying task
miner setup page says args and return types vary by competition, the compression page (Feb 2026) gives injected text plus a ratio in and compressed text out, no schema
Q2Who it is for●●●●● 2
4 CPU cores, 16 GB RAM, 500 GB SSD storage
appears under the Validators heading, no miner hardware statement, registration command given with no cost (chain burn 0.25 TAO today), no competitiveness statement
Q3How it resists gaming or fails●●●●● 4
scoring page with weighted token formula, compression ratio clamp, penalty floor and constants table, incentive page gives winner per element shares, no worked example, no immunity or deregistration policy
Q4Identity and documentation●●●●● 3
miner setup guide last updated 27 May 2026, release v1.0.0 2026-05-20, repo pushed 2026-09-09, incentive page changed 15 Jul 2026 after the guide, guide defers to per competition requirements
Buyers and enterprises●●●●● 3.5
Can I use this today? · rank 10 of 32 for this audience
Q1What it is●●●●● 4
Official SOMA application for AI agents
plus SOMARIZER and a Compressor for OpenClaw listed as tools on the front page, app.thesoma.ai is a JS dashboard, no API endpoint or example found
Q2Who it is for●●●●● 4
AI teams are paying for repeated context, not better intelligence
with Deepseek V4 Pro at $1.32 / 1M against $1.19 / 1M with SOMA, other models marked coming soon, no pricing page beyond the front page
Q3How it resists gaming or fails●●●●● 3
contact form, thesoma@dendrite.holdings and a Discord invite on the contact page, no status page (status.thesoma.ai does not resolve), no SLA, no response time
Q4Identity and documentation●●●●● 3
no API reference in the docs which cover miners, validators and benchmarks only, the contact page lists https://x.com/SomaSubnet which matches the chain subnet_contact
Newcomers●●●●● 3.3
What is this and why does it matter? · rank 20 of 32 for this audience
Q1What it is●●●●● 4
a compression layer that cuts token costs without cutting output quality
on the front page, README opens with a one sentence definition, consistent with the chain description
Q2Who it is for●●●●● 2
AI teams are paying for repeated context, not better intelligence
frames the difference as cost versus redundant context, nothing on what decentralization changes or a comparison with a centralized compressor
Q3How it resists gaming or fails●●●●● 3
token savings chart on the front page without a date, a live SOMARIZER tool, benchmark docs describe how to run SOMA Bench with no published results table
Q4Identity and documentation●●●●● 4
subnet_name SOMA matches the site, description is a noun phrase without a finite verb, url resolves, docs and contact pages serve as about and learn pages
How this score came to be. Verified means the scorer fetched the page and the words are on it; inferred means concluded from code, absence, or a third party. The link badge is a separate automated check made before publication.
Something wrong? Corrections of fact are applied as they arrive during the window; score disputes are batched at its close. How to file one · GitHub issue · email.