{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"cloudflare-os-workers","urls":{"read":"https://miscsubjects.com/api/articles/cloudflare-os-workers/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/cloudflare-os-workers/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/cloudflare-os-workers/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/cloudflare-os-workers/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/cloudflare-os-workers/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/cloudflare-os-workers/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/cloudflare-os-workers/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"cloudflare-os-workers","title":"One missing alarm guard turned a $5.75 workload into $34,895","register":"essay","tags":["cloudflare","architecture","durable-objects","cloudflare-os"],"updated_at":"2026-07-26T06:07:31.875Z","body_excerpt":"Most of a Cloudflare build is one Pages deployment answering one request and forgetting everything between requests. Some jobs cannot be written that way: a schedule with no caller, a counter two clients must not race on, a timer that fires in four hours, a session that remembers what it did last turn. Those need a Worker of their own, and sometimes a Durable Object.\n\nA Durable Object is the expensive answer. It is also the one that produced a $34,895 invoice for a founder with zero users. Read the money section before you write the alarm.\n\n## Evidence status\n\n**Observed** marks first-party measurements or runtime receipts from the named environment.\n**Derived** marks arithmetic calculated from cited inputs. **Specified** marks vendor or standards\ndocumentation. **Implemented** and **deployed** name code and live-state evidence, respectively.\n**Reproduced** means the stated procedure was rerun. **Externally attested** marks operator reports;\nthose reports show that an experience occurred, not that it is universal.\n\n## Three things can serve a request, and only one of them remembers\n\n| | Pages Function | Standalone Worker | Durable Object |\n| --- | --- | --- | --- |\n| Who addresses it | a URL path on the Pages project | its own route, `workers.dev` name, or a service binding | a Worker holds a stub obtained from an id; it has no public address |\n| Holds state | no | no | yes: private SQLite storage, plus in-memory state while awake |\n| Survives the request | no | no, unless woken by cron, a queue, or email | yes; stays in memory until idle, hibernates, reconstructed on next request |\n| How many run at once | as many as there is traffic | as many as there is traffic | exactly one per id, worldwide, single-threaded |\n| Billed as | Workers requests + CPU time | Workers requests + CPU time | its own line: requests, wall-clock duration at 128 MB, per-row storage |\n| Woken by | an HTTP request | HTTP, `scheduled`, `queue`, `email` | a request from a Worker, or its own alarm |\n\nRows three and four decide it. If two callers must not interleave on the same piece of state, you need something that exists exactly once and runs one thing at a time. That is a Durable Object, and nothing else on the platform is that.\n\nStorage alone is not a reason. [D1 and KV](/a/cloudflare-os-d1) already store things and cost less to operate. Scheduling alone is not a reason: a cron trigger on a plain Worker is cheaper, and [queues, workflows and cron](/a/cloudflare-os-async) covers which of those three fits.\n\n[[embed:source:s15]]\n\n## A Durable Object is one addressable single-threaded instance, and D1 is one of them\n\nCloudflare's concepts page: \"Each Durable Object has a globally-unique name, which allows you to send requests to a specific object from anywhere in the world,\" and \"Durable Objects are single-threaded and cooperatively multi-tasked, just like code running in a web browser.\"\n\n[[embed:source:s1]]\n\nPrecisely, in the order the pieces matter:\n\n1. **A namespace** is a class you exported and declared in your Wrangler config. `DirectoryDO` is a namespace.\n2. **An id** picks one instance inside it. `env.DIRECTORY_DO.idFromName('main')` derives the same id from the same string every time, anywhere on earth.\n3. **The instance** for that id exists exactly once. Requests queue; they do not run concurrently.\n4. **Its storage** is private to that id. Nothing else reads it except by asking that instance.\n5. **Its location** is fixed near wherever it was first created, and does not move.\n\nPoint 5 is the cost nobody plans for. A Durable Object is not at the edge the way a Worker is. The community tracker at where.durableobjects.live, which continuously creates and destroys objects to sample placement, reported Durable Objects available in **10.8% of Cloudflare points of presence** on the day this page was measured. Your Worker runs next to the reader; the object it talks to may not.\n\n[[embed:source:s17]]\n\n[[embed:source:s18]]\n\nThe Workers architect is blunter t","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"A Durable Object is the only compared Cloudflare primitive that combines a globally addressable single instance, serialized execution and private persistent storage.","tier":"system","section":"Three things can serve a request, and only one of them remembers","interaction_risk":false,"status":"active","source_ids":["s1","s18"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"A stateless scheduled job belongs in a standalone Worker with a Cron Trigger; storage or scheduling alone does not justify a Durable Object.","tier":"system","section":"Three things can serve a request, and only one of them remembers","interaction_risk":false,"status":"active","source_ids":["s15"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"Each Durable Object id names one globally unique, single-threaded instance whose storage is private to that instance.","tier":"system","section":"A Durable Object is one addressable single-threaded instance, and D1 is one of them","interaction_risk":false,"status":"active","source_ids":["s1","s16"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"The independent placement tracker reported Durable Objects available in 10.83% of Cloudflare points of presence when measured.","tier":"system","section":"A Durable Object is one addressable single-threaded instance, and D1 is one of them","interaction_risk":false,"status":"active","source_ids":["s17"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"Cloudflare's Workers architect says D1 is a singleton Durable Object wrapper and raw Durable Objects avoid repeated long-haul query round trips, while D1 read replicas remain a real advantage.","tier":"system","section":"A Durable Object is one addressable single-threaded instance, and D1 is one of them","interaction_risk":false,"status":"active","source_ids":["s16","s7","s8"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c6","text":"An unconditional setAlarm call across more than 60 preview deployments produced roughly 930 billion daily row reads and a $34,895 invoice with zero users.","tier":"system","section":"$34,895 with zero users: an alarm that rescheduled itself on every wake-up","interaction_risk":false,"status":"active","source_ids":["s3","s4","s9"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c7","text":"Safe alarm startup checks getAlarm before setAlarm, verifies that any stored time is still in the future, caps the loop and deletes the alarm on termination.","tier":"system","section":"$34,895 with zero users: an alarm that rescheduled itself on every wake-up","interaction_risk":false,"status":"active","source_ids":["s11","s4","s9"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c8","text":"Durable Object alarms are delivered at least once and receive up to six automatic retries after handler failures.","tier":"system","section":"Alarms fail in two documented ways, and both are silent","interaction_risk":false,"status":"active","source_ids":["s4"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c9","text":"In local development, hot reload can leave an alarm visible in storage while preventing it from firing until the development server restarts.","tier":"system","section":"Alarms fail in two documented ways, and both are silent","interaction_risk":false,"status":"active","source_ids":["s10"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c10","text":"A stale past alarm timestamp can make a scheduling guard skip every future alarm and permanently deadlock the job.","tier":"system","section":"Alarms fail in two documented ways, and both are silent","interaction_risk":false,"status":"active","source_ids":["s11"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c11","text":"A plain accepted WebSocket bills Durable Object duration for the connection lifetime; the Hibernation API permits idle suspension without disconnecting clients.","tier":"system","section":"WebSockets bill for wall-clock time, and the documented fix is a rewrite","interaction_risk":false,"status":"active","source_ids":["s12","s2","s3","s5"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c12","text":"At current rates, the stated six-million-request monthly workload costs $5.75 while remaining inside the included duration and SQLite row allowances.","tier":"system","section":"What it costs, at today's published rates","interaction_risk":false,"status":"active","source_ids":["s3","s6"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c13","text":"Operators report both multi-million-user SQLite deployments at low cost and tick-based games with negligible alarm cost, with real-time sockets as the stated boundary.","tier":"system","section":"The case for and against, from people running them","interaction_risk":false,"status":"active","source_ids":["s13","s14"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c14","text":"The production application separates seven standalone Workers from its Pages request layer because timers, consumers, state classes, private services and independent routes need separate deployment boundaries.","tier":"system","section":"Seven Workers sit outside the main deployment, each for a stated reason","interaction_risk":false,"status":"active","source_ids":["s19"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c15","text":"Pages Durable Object and service bindings reference Worker scripts that must already exist, so referenced Workers deploy before Pages.","tier":"system","section":"The binding-order failure: a deploy that errors on a binding to a script never uploaded","interaction_risk":false,"status":"active","source_ids":["s1","s19"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c16","text":"The DirectoryDO schema is initialized inside blockConcurrencyWhile and callers reach the singleton named main through an id-derived stub.","tier":"system","section":"What a real Durable Object in this build does, read from the source","interaction_risk":false,"status":"active","source_ids":["s16","s20"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c17","text":"In the twelve-run interleaved measurement, median latency was 272 ms for a standalone Worker, 237 ms for a Pages Function and 276 ms for the Durable Object path.","tier":"system","section":"Measured here: the Durable Object hop is not the latency you think it is","interaction_risk":false,"status":"active","source_ids":["s19","s20"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c18","text":"The live Durable Object response returned a stable 64-hex id for DirectoryDO, while the live registry held 54 slugs and 157 logged intents at measurement time.","tier":"system","section":"Measured here: the Durable Object hop is not the latency you think it is","interaction_risk":false,"status":"active","source_ids":["s20"],"why_material":"This changes the compute choice, cost, deployment order, or failure response.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"s1","type":"publisher_documentation","url":"https://developers.cloudflare.com/durable-objects/concepts/what-are-durable-objects/","title":"What are Durable Objects?","quote":"allows you to send requests to a specific object from anywhere in the world.","summary":"Defines globally unique addressing, single-threaded execution and private attached storage.","claim_ids":["c1","c15","c3"]},{"id":"s2","type":"publisher_documentation","url":"https://developers.cloudflare.com/durable-objects/concepts/durable-object-lifecycle/","title":"Durable Object lifecycle","quote":"Currently, it is after 10 seconds of inactivity while in this state.","summary":"Documents creation, activity, hibernation eligibility, eviction and reconstruction.","claim_ids":["c11"]},{"id":"s3","type":"publisher_documentation","url":"https://developers.cloudflare.com/durable-objects/platform/pricing/","title":"Durable Objects pricing","quote":"Durable Objects that are idle and eligible for hibernation are not billed for duration","summary":"The current request, duration, SQLite row and storage rates used in both bill calculations.","claim_ids":["c11","c12","c6"]},{"id":"s4","type":"specification","url":"https://developers.cloudflare.com/durable-objects/api/alarms/","title":"Durable Object alarms API","quote":"Alarms have guaranteed at-least-once execution and are retried automatically","summary":"The single-alarm contract, at-least-once delivery, retry budget and constructor guard.","claim_ids":["c6","c7","c8"]},{"id":"s5","type":"publisher_documentation","url":"https://developers.cloudflare.com/durable-objects/best-practices/websockets/","title":"Use WebSockets with Durable Objects","quote":"Allows the Durable Object to hibernate without disconnecting clients when idle.","summary":"The recommended Hibernation WebSocket API, lifecycle and event-handler conversion.","claim_ids":["c11"]},{"id":"s6","type":"publisher_documentation","url":"https://developers.cloudflare.com/workers/platform/pricing/","title":"Cloudflare Workers pricing","quote":"10 million included per month","summary":"The ordinary Worker request and CPU allowances compared with Durable Object billing.","claim_ids":["c12"]},{"id":"s7","type":"hn","url":"https://news.ycombinator.com/item?id=48611834","title":"Temporary Cloudflare accounts for AI agents","quote":"It's almost always better to use Durable Objects storage, rather than D1. Even if you only want a single global database, it's better to implement that as a singleton Durable Object, than by using D1.","summary":"The Workers architect states D1 is literally a singleton Durable Object wrapping SQLite, so raw DOs give you code co-located with the database and near-zero query latency. Says D1 exists mainly for familiarity, with read replicas the one remaining D1 advantage. Positive on DOs, blunt about D1.","claim_ids":["c5"]},{"id":"s8","type":"hn","url":"https://news.ycombinator.com/item?id=48611834","title":"Temporary Cloudflare accounts for AI agents","quote":"Pages were slow due to the multiple round trips to storage on each page since Claude Code used D1. Despite repeated prompting Claude Code had no suggestions for how to improve within the CF platform.","summary":"A builder moved from D1 toward Postgres after tooling failed to surface the Durable Object design; negative evidence about discoverability.","claim_ids":["c5"]},{"id":"s9","type":"hn","url":"https://news.ycombinator.com/item?id=47787042","title":"Durable Object alarm loop: $34k in 8 days, zero users, no platform warning","quote":"My DO agent's onStart() handler called this.ctx.storage.setAlarm() on every wake-up without checking whether an alarm was already scheduled.","summary":"Pre-launch solo founder posts a full postmortem: setAlarm() called unconditionally on every DO wake-up, multiplied by 60+ preview deployments each spawning independent DO instances, peaked at ~930 billion row reads/day and produced a $34,895 invoice with zero users. No platform warning fired. Negative.","claim_ids":["c6","c7"]},{"id":"s10","type":"github","url":"https://github.com/cloudflare/workerd/issues/3566","title":"🐛 BUG: Durable Object Alarms not triggering after a code reload","quote":"The alarm triggers as expected, but as soon as the code has changes and the worker reloads, then the alarm stops triggerring.","summary":"A 5-second DO alarm fires normally under wrangler dev until a hot reload, after which it silently stops even though ctx.storage.getAlarm() still shows the alarm present. Negative — alarms as a fragile primitive in the dev loop.","claim_ids":["c9"]},{"id":"s11","type":"github","url":"https://github.com/opennextjs/opennextjs-cloudflare/issues/929","title":"[BUG] Durable Objects alarm not firing due to stale past alarms remaining in storage","quote":"no new alarm is set, creating a deadlock where","summary":"One failed alarm handler leaves a past timestamp in DO storage forever, so all later scheduling calls skip setting a new alarm and cache purges silently stop working. A permanent deadlock from a single transient failure. Negative.","claim_ids":["c10","c7"]},{"id":"s12","type":"stackoverflow","url":"https://stackoverflow.com/questions/79336461/trying-to-use-websocket-hibernation-api","title":"Trying to use Websocket Hibernation Api","quote":"I have a Cloudflare Worker that uses Durable Objects and WebSocket. However, the costs of WebSocket are high, so I decided to implement the Websocket Hibernation API","summary":"Hit real WebSocket duration billing on Durable Objects and tried to move to the Hibernation API to cut it, then could not get the hibernation code to work at all. Negative on both DO WebSocket cost and the ergonomics of the documented fix.","claim_ids":["c11"]},{"id":"s13","type":"hn","url":"https://news.ycombinator.com/item?id=48946048","title":"SQLite Is All You Need","quote":"We serve multi million MAU on sqlite orchestrated through durable objects. It's not the most complex thing in the world but it goes further than CRUD. It costs us such a small amount of money for what it does.","summary":"Runs multi-million monthly-active-user traffic on SQLite inside Durable Objects and says their previous Postgres cluster was orders of magnitude more expensive. Positive, at real scale.","claim_ids":["c13"]},{"id":"s14","type":"hn","url":"https://news.ycombinator.com/item?id=47785298","title":"Show HN: I rebuilt a 2000s browser strategy game on Cloudflare's edge","quote":"DO alarms handle the time-based stuff (fleet arrivals, combat resolution, resource ticks) so there's no persistent connection cost. so far costs have been negligible","summary":"Answering a direct question about DOs being prohibitively expensive for an MMO: because the game is tick-based rather than realtime, request rate per player is single-digit-per-minute and alarms replace persistent connections, so cost is negligible. Says websockets + stateful server would be right for anything realtime. Positive with a clearly stated boundary.","claim_ids":["c13"]},{"id":"s15","type":"publisher_documentation","url":"https://developers.cloudflare.com/workers/configuration/cron-triggers/","title":"Cron Triggers","quote":"Cron Triggers allow users to map a cron expression to a Worker using a scheduled() handler that enables Workers to be executed on a schedule.","summary":"Why a scheduled stateless job belongs in a plain Worker rather than a Durable Object.","claim_ids":["c2"]},{"id":"s16","type":"specification","url":"https://developers.cloudflare.com/durable-objects/best-practices/access-durable-objects-storage/","title":"Access Durable Object storage","quote":"the Durable Object itself, which runs on the same machine as the SQLite database","summary":"The front-end Worker, stub and co-located SQLite pattern used by the code walkthrough.","claim_ids":["c16","c3","c5"]},{"id":"s17","type":"independent_measurement","url":"https://where.durableobjects.live/","title":"Where Durable Objects Live","quote":"Data displayed on this site is updated every 5 minutes.","summary":"A continuously updated independent placement tracker that creates and destroys objects around the world; the article records the measured 10.83% value.","claim_ids":["c4"]},{"id":"s18","type":"publisher_documentation","url":"https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/","title":"Durable Objects: Easy, Fast, Correct — Choose three","quote":"Durable Objects: Easy, Fast, Correct","summary":"Cloudflare's engineering explanation of how the actor model serializes work while colocating compute and state.","claim_ids":["c1"]},{"id":"s19","type":"runtime_receipt","url":"https://miscsubjects.com/api/durable/slug.list","title":"Production Worker and Durable Object inventory","quote":"\"count\":54","summary":"First-party repository and Wrangler inventory, plus a live registry read; exact commands and deployment timestamps are published in the article.","claim_ids":["c14","c15","c17"]},{"id":"s20","type":"runtime_receipt","url":"https://miscsubjects.com/api/durable/ping","title":"Live DirectoryDO response","quote":"\"do\":\"DirectoryDO\"","summary":"First-party live response proving the Pages Function reaches the named Durable Object and returns its stable object identity.","claim_ids":["c16","c17","c18"]}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"cloudflare-os-workers","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":18,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":18,"claims_total":18,"sources":20,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}