Differences

This shows you the differences between two versions of the page.

View differences: Side by SideInline Go

Link to this comparison view

Both sides previous revisionPrevious revision 2026/04/19 22:16 gwyntel Added rate-limit evolution and v3 experiment details2026/04/19 05:05 gwyntel update limits with payg caveat2026/04/19 04:30 gwyntel What changed: Fixed "fix set of per-hour" → "fixed set of 5-hour" (typo) Added Founder's Packs section — 50% more ($36/wk, 750/5hrs) at same $30/mo price Added History: Rate Limit Changes section — old system (135/5hrs + 500 tool calls/day = 1,148/day) vs2026/04/12 22:56 spiffytech [Subscription Limits] Request cost scaling2026/04/12 22:28 spiffytech [Subscription Limits] Enumerate small models2026/04/11 16:21 amolith [Additional Limits] 2026/04/11 16:20 amolith [Additional Limits] 2026/04/11 16:18 amolith [Additional Limits] typo2026/04/11 16:07 amolith [Additional Limits] 2026/04/11 16:07 amolith 2026/04/10 19:13 spiffytech [Subscription Pricing] 2026/04/10 19:13 spiffytech [Subscription Pricing] Ehhhh I thought I didn't need to spell this out but someone's gonna ask about it if I omit it, aren't they?2026/04/10 18:55 spiffytech [Subscription Limits] Concurrency2026/04/10 18:54 spiffytech [Subscription Pricing] Mention concurrency2026/04/10 01:06 xenolandscapes 2026/04/10 01:03 xenolandscapes [Profitability] 2026/04/10 00:50 xenolandscapes [Profitability] 2026/04/10 00:37 xenolandscapes [Profitability] 2026/04/09 18:55 xenolandscapes 2026/04/09 17:55 xenolandscapes 2026/04/09 17:54 xenolandscapes 2026/04/09 17:40 xenolandscapes createdGo		2026/04/19 22:16 gwyntel Added rate-limit evolution and v3 experiment details2026/04/19 05:05 gwyntel update limits with payg caveat2026/04/19 04:30 gwyntel What changed: Fixed "fix set of per-hour" → "fixed set of 5-hour" (typo) Added Founder's Packs section — 50% more ($36/wk, 750/5hrs) at same $30/mo price Added History: Rate Limit Changes section — old system (135/5hrs + 500 tool calls/day = 1,148/day) vs2026/04/12 22:56 spiffytech [Subscription Limits] Request cost scaling2026/04/12 22:28 spiffytech [Subscription Limits] Enumerate small models2026/04/11 16:21 amolith [Additional Limits] 2026/04/11 16:20 amolith [Additional Limits] 2026/04/11 16:18 amolith [Additional Limits] typo2026/04/11 16:07 amolith [Additional Limits] 2026/04/11 16:07 amolith 2026/04/10 19:13 spiffytech [Subscription Pricing] 2026/04/10 19:13 spiffytech [Subscription Pricing] Ehhhh I thought I didn't need to spell this out but someone's gonna ask about it if I omit it, aren't they?2026/04/10 18:55 spiffytech [Subscription Limits] Concurrency2026/04/10 18:54 spiffytech [Subscription Pricing] Mention concurrency2026/04/10 01:06 xenolandscapes 2026/04/10 01:03 xenolandscapes [Profitability] 2026/04/10 00:50 xenolandscapes [Profitability] 2026/04/10 00:37 xenolandscapes [Profitability] 2026/04/09 18:55 xenolandscapes 2026/04/09 17:55 xenolandscapes 2026/04/09 17:54 xenolandscapes 2026/04/09 17:40 xenolandscapes createdGo
limits [2026/04/19 05:05] – update limits with payg caveat gwyntel		limits [2026/04/19 22:16] (current) – Added rate-limit evolution and v3 experiment details gwyntel
Line 101:		Line 101:
	Synthetic also provide //unlimited// access to [[models:nomic-embed-text-15|Nomic Embed Text 1.5]], an embedding model, and two LORAs they trained for [[harnesses/octofriend]], ''[[https://huggingface.co/syntheticlab/diff-apply|hf:syntheticlab/diff-apply]]'' and ''[[https://huggingface.co/syntheticlab/fix-json|hf:syntheticlab/fix-json]]''. Like any model from Synthetic, they're usable in any harness. ''diff-apply'' applies find-replace style diffs to code and ''fix-json'' fixes broken JSON tool calls. They require particular input/output formats, so be sure to check the model cards.		Synthetic also provide //unlimited// access to [[models:nomic-embed-text-15|Nomic Embed Text 1.5]], an embedding model, and two LORAs they trained for [[harnesses/octofriend]], ''[[https://huggingface.co/syntheticlab/diff-apply|hf:syntheticlab/diff-apply]]'' and ''[[https://huggingface.co/syntheticlab/fix-json|hf:syntheticlab/fix-json]]''. Like any model from Synthetic, they're usable in any harness. ''diff-apply'' applies find-replace style diffs to code and ''fix-json'' fixes broken JSON tool calls. They require particular input/output formats, so be sure to check the model cards.
		+
		+	===== Rate-Limit Evolution =====
		+
		+	<WRAP center round info 60%>
		+	Based on public statements from Synthetic staff. The rate limiting system has gone through several iterations due to abuse vectors.
		+	</WRAP>
		+
		+	^ Phase ^ System ^ Problem ^
		+	| **v1** | X requests per 5 hours + free tool calls | Users formatted any request as a tool call to get free requests. 3 users consumed >1/3 of total capacity. |
		+	| **v2** | Tool calls count as percentage of requests (e.g. 10%) | Percentage-based discount could still be abused for ~10x the quota. |
		+	| **v3** (current) | Weekly token quota ($24/week per pack) + 500 requests per 5 hours | Token-based weekly limit eliminates tool call abuse. Requests weighted by output token cost. |
		+
		+	The **rate-limit-v3 experiment** launched on April 7, 2026 after three weeks of opt-in testing. Key changes:
		+
		+	- **5-hour requests**: 500 per pack (up from 135), weighted by output token cost
		+	- **Weekly tokens**: $24.00 worth of compute per pack (replaces daily tool call limits)
		+	- **Tool calls**: No longer separately counted — all usage flows through the weekly token quota
		+	- **Founder's packs**: 50% more ($36/week tokens, 750 requests/5 hours)
		+	- **Concurrency**: 1 at a time per pack (2 for "small models": Nemotron 3 Super & GLM-4.7-Flash)
		+
		+	<WRAP center round tip>
		+	The weekly token quota means you don't need to think about "saving" tool calls vs regular requests anymore. Everything is just tokens. Unused 5-hour requests may eventually get "refunded" into the weekly token quota (proposed but not yet confirmed).
		+	</WRAP>
		+
		+	=== Why Request-Based, Not Token-Based? ===
		+
		+	Synthetic chose request-based limits over pure token-based limits for simplicity:
		+
		+	- Token-based pricing encourages gaming (deleting conversation history to save quota, splitting context)
		+	- Request count follows a predictable pattern relative to cost
		+	- With the weekly token quota, the worst of both approaches is mitigated