{"_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-email","urls":{"read":"https://miscsubjects.com/api/articles/cloudflare-os-email/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-email/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-email/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-email/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-email/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-email/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-email/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-email","title":"Cloudflare email is three products, not one mail stack","register":"technical","tags":["cloudflare","architecture","email","cloudflare-os"],"updated_at":"2026-07-26T06:23:25.501Z","body_excerpt":"# Cloudflare email is three products, not one mail stack\n\nCloudflare can forward inbound mail, run code on it, and send transactional mail. Each capability has a different setup gate. A verified forwarding address is not an onboarded sending domain.\n\n| Product surface | Direction | What it does | Prerequisite | What it does not replace |\n| --- | --- | --- | --- | --- |\n| Email Routing | Inbound | Maps an address or catch-all to a verified destination or Worker | Domain onboarded for routing; routing MX, SPF, and DKIM records | A mailbox, outbound sender, campaign system |\n| Email Workers | Inbound, plus constrained reply/forward | Runs an `email()` handler over the raw message | Active route bound to a deployed Worker; destinations verified before forwarding | General arbitrary outbound on the free plan |\n| Email Service / Email Sending | Outbound | Sends transactional mail through a Worker binding, REST, or SMTP | Sending domain onboarded; Paid plan for arbitrary recipients; `send_email` binding for Workers | Marketing automation, customer subaccounts, full ESP operations |\n\nVerified destinations are free on every plan; arbitrary recipients require Workers Paid. Paid includes 3,000 outbound messages per account each month, then costs $0.35 per 1,000. Inbound is unlimited, although processing consumes Worker resources.\n\n[[embed:source:s1]]\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## The setup begins with DNS, not code\n\nFor inbound routing, the dashboard path is:\n\n`Cloudflare dashboard → account → Compute → Email Service → Email Routing → Onboard Domain`\n\nFor `example.com`, Cloudflare creates this root-domain shape:\n\n```txt\nMX  @  route1.mx.cloudflare.net\nMX  @  route2.mx.cloudflare.net\nMX  @  route3.mx.cloudflare.net\nTXT @  \"v=spf1 include:_spf.mx.cloudflare.net ~all\"\nTXT cf2024-1._domainkey  \"v=DKIM1; h=sha256; k=rsa; p=<Cloudflare public key>\"\n```\n\nCloudflare assigns MX priorities. Merge the Cloudflare `include:` into an existing SPF record; two SPF records are invalid, and SPF has a ten-lookup ceiling.\n\n[[embed:source:s2]]\n\nFor outbound Email Sending, onboarding is separate:\n\n`Cloudflare dashboard → account → Compute → Email Service → Email Sending → Onboard Domain`\n\nThe outbound records live under `cf-bounce.example.com`, leaving the inbound root MX records alone:\n\n```txt\nMX  cf-bounce  route1.mx.cloudflare.net\nMX  cf-bounce  route2.mx.cloudflare.net\nMX  cf-bounce  route3.mx.cloudflare.net\nTXT cf-bounce  \"v=spf1 include:_spf.mx.cloudflare.net ~all\"\nTXT cf-bounce._domainkey  \"v=DKIM1; h=sha256; k=rsa; p=<Cloudflare public key>\"\nTXT _dmarc  \"v=DMARC1; p=none; rua=mailto:dmarc@example.com\"\n```\n\nCloudflare says DNS commonly settles in 5–15 minutes but can take up to 24 hours. The practical gate is that the Email Sending screen shows the domain onboarded and DNS queries return the records. Start DMARC at `p=none` if other providers still send for the domain; enforce only after their identities align.\n\n[[embed:source:s3]]\n\n## Routing rules, verified destinations, and the catch-all\n\nForwarding requires a destination address that the recipient has verified. The dashboard path is:\n\n`Compute → Email Service → Email Routing → Destination Addresses`\n\nCloudflare emails that address a verification link. A routing rule pointing at an unverified destination remains disabled. Once verified, create a rule under:\n\n`Compute → Email Service → Email Routing → Routing Rules → Create routing rule`\n\nThe action is send to a verified address, send to a Worker, or drop. If two rules use the same pattern, only the f","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"Cloudflare email comprises separate inbound forwarding, inbound code processing, and outbound transactional sending surfaces with different prerequisites.","tier":"system","section":"Cloudflare email is three products, not one mail stack","interaction_risk":false,"status":"active","source_ids":["s1","s3","s4","s5"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"Arbitrary-recipient sending requires Workers Paid; verified-destination sends are free, and paid accounts include 3,000 outbound messages per month before $0.35 per 1,000.","tier":"system","section":"Cloudflare email is three products, not one mail stack","interaction_risk":false,"status":"active","source_ids":["s1","s8"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"Email Routing and Email Sending onboard separately and publish different root-domain and cf-bounce DNS records.","tier":"system","section":"The setup begins with DNS, not code","interaction_risk":false,"status":"active","source_ids":["s12","s2","s3"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"A routing rule aimed at an address stays disabled until that destination address is verified.","tier":"system","section":"Routing rules, verified destinations, and the catch-all","interaction_risk":false,"status":"active","source_ids":["s4"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"An Email Worker can parse an inbound MIME stream, store its attachments in R2, and forward to a verified destination.","tier":"system","section":"A runnable inbound Worker that parses MIME and stores attachments","interaction_risk":false,"status":"active","source_ids":["s5","s6","s7"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c6","text":"The raw message stream must be consumed once or buffered before multiple consumers inspect it.","tier":"system","section":"A runnable inbound Worker that parses MIME and stores attachments","interaction_risk":false,"status":"active","source_ids":["s5","s6"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c7","text":"Reply and forward are constrained inbound actions; forwarding requires verified destinations and replies fail above 100 References entries.","tier":"system","section":"Replying is not the same as arbitrary sending","interaction_risk":false,"status":"active","source_ids":["s4","s8"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c8","text":"Sending to arbitrary recipients requires an onboarded sending domain, Workers Paid, a send_email binding, an aligned from-domain, and compliance with message limits.","tier":"system","section":"New outbound mail uses Email Service","interaction_risk":false,"status":"active","source_ids":["s1","s3","s8","s9"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c9","text":"The live miscsubjects implementation has working inbound DNS and code paths while its own endpoint still reports Email Sending onboarding as incomplete.","tier":"system","section":"The site's own split proves why the prerequisite must be visible","interaction_risk":false,"status":"active","source_ids":["s10","s11"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c10","text":"SPF authenticates the envelope sender path, DKIM signs message content, DMARC requires aligned SPF or DKIM, and ARC carries an intermediary's observed authentication chain.","tier":"system","section":"SPF, DKIM, DMARC, and ARC in plain language","interaction_risk":false,"status":"active","source_ids":["s12","s2"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c11","text":"Independent operators report Microsoft or Outlook blocking Cloudflare Email Routing relay IP ranges even when authentication work was in place.","tier":"system","section":"The Outlook reports are real, but they are not a universal result","interaction_risk":false,"status":"active","source_ids":["s13","s14","s15"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c12","text":"Those reports demonstrate a failure mode but do not measure prevalence or prove that every Outlook destination will reject Cloudflare routing.","tier":"system","section":"The Outlook reports are real, but they are not a universal result","interaction_risk":false,"status":"active","source_ids":["s13","s14","s15"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c13","text":"A successful Worker invocation or send call is not delivery proof; operators must inspect Email Sending logs, SMTP outcomes, and the destination.","tier":"system","section":"The Outlook reports are real, but they are not a universal result","interaction_risk":false,"status":"active","source_ids":["s16","s17"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c14","text":"Cloudflare does not currently document a SendGrid-equivalent API-created subaccount product for customer-owned verified sending domains.","tier":"system","section":"Where Cloudflare Email Service still is not SendGrid","interaction_risk":false,"status":"active","source_ids":["s18","s3"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c15","text":"Building templates, bounce workflows, suppressions, tenant analytics, and marketing controls on Workers turns a send integration into an email-platform project.","tier":"system","section":"Where Cloudflare Email Service still is not SendGrid","interaction_risk":false,"status":"active","source_ids":["s18","s19","s8"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c16","text":"Cloudflare's low transactional unit price is attractive when one owned domain sends application mail, but it does not by itself replace an ESP's operational features.","tier":"system","section":"Cost is attractive; replacement scope is the constraint","interaction_risk":false,"status":"active","source_ids":["s1","s20"],"why_material":"This changes the setup, architecture, delivery proof, or provider decision.","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/email-service/platform/pricing/","title":"Email Service pricing","quote":"Workers Paid 3,000 included per month, then $0.35 per 1,000 emails","summary":"The current separation between free verified-destination sends, paid arbitrary-recipient sending, and unlimited inbound routing.","claim_ids":["c1","c16","c2","c8"]},{"id":"s2","type":"publisher_documentation","url":"https://developers.cloudflare.com/email-service/reference/troubleshooting/","title":"Email Service troubleshooting","quote":"Having multiple SPF records on your domain is not allowed and will prevent Email Service from working properly.","summary":"The exact SPF, DKIM, DMARC, local attachment, and provider-delivery checks.","claim_ids":["c10","c3"]},{"id":"s3","type":"publisher_documentation","url":"https://developers.cloudflare.com/email-service/configuration/domains/","title":"Email Service domain configuration","quote":"Before using Email Sending, configure your domain.","summary":"The current dashboard path and separate DNS record sets for Email Sending and Email Routing.","claim_ids":["c1","c14","c3","c8"]},{"id":"s4","type":"publisher_documentation","url":"https://developers.cloudflare.com/email-service/configuration/email-routing-addresses/","title":"Email routing rules and addresses","quote":"Until a destination address is verified, any routing rule that points to it stays disabled.","summary":"The verified-destination prerequisite, rule order, Worker binding, catch-all, and subaddressing behavior.","claim_ids":["c1","c4","c7"]},{"id":"s5","type":"specification","url":"https://developers.cloudflare.com/email-service/api/route-emails/email-handler/","title":"Email handler Workers API","quote":"Use postal-mime to parse the MIME structure of an incoming email.","summary":"The runtime interface for raw messages, forwarding, replying, rejecting, and MIME parsing.","claim_ids":["c1","c5","c6"]},{"id":"s6","type":"source_repository","url":"https://github.com/postalsys/postal-mime","title":"postal-mime source repository","quote":"PostalMime is a browser-friendly and serverless email parser.","summary":"The maintained MIME parser used in the runnable attachment-to-R2 example.","claim_ids":["c5","c6"]},{"id":"s7","type":"hn","url":"https://news.ycombinator.com/item?id=47932438","title":"Show HN: Webhook API – inbound email –> webhook","quote":"I’m using Cloudflare Email Routing with a catch-all address that triggers a Worker. The Worker parses the email and stores the attachments in R2.","summary":"Running catch-all Email Routing into an Email Worker that parses messages and lands attachments in R2, and reports it works well for that job. Positive — the receive-and-process path, which is the part that does work.","claim_ids":["c5"]},{"id":"s8","type":"specification","url":"https://developers.cloudflare.com/email-service/platform/limits/","title":"Email Service limits","quote":"Reply References entries 100","summary":"The current per-message, per-zone, routing, verified-destination, and reply limits.","claim_ids":["c15","c2","c7","c8"]},{"id":"s9","type":"publisher_documentation","url":"https://developers.cloudflare.com/email-service/platform/limits/","title":"Email Service quotas and onboarding limits","quote":"Before you onboard a sending domain, you can send emails only to verified destination addresses in your account.","summary":"The account-side onboarding boundary and conservative daily quota model.","claim_ids":["c8"]},{"id":"s10","type":"first_party_code","url":"https://miscsubjects.com/api/email/send","title":"Live miscsubjects email endpoint","quote":"Enable Email Sending on miscsubjects.com in CF dashboard (Pages cannot bind send_email)","summary":"The production endpoint reports the inbound routes and the currently unmet sending-domain prerequisite.","claim_ids":["c9"]},{"id":"s11","type":"independent_measurement","url":"https://miscsubjects.com/a/cloudflare-os-email","title":"Live DNS measurement","quote":"miscsubjects.com resolved route1, route2, and route3.mx.cloudflare.net plus SPF, DKIM, and DMARC on 2026-07-26.","summary":"A read-only first-party DNS measurement, explicitly not a delivery test.","claim_ids":["c9"]},{"id":"s12","type":"specification","url":"https://developers.cloudflare.com/email-service/reference/postmaster/","title":"Email Service postmaster reference","quote":"ARC allows intermediate email servers, such as forwarders, to attach a record of the original authentication results to a message.","summary":"Cloudflare's SRS, ARC, DKIM, SPF, DMARC, authentication, and SMTP behavior.","claim_ids":["c10","c3"]},{"id":"s13","type":"hn","url":"https://news.ycombinator.com/item?id=45373715","title":"Cloudflare Email Service: private beta","quote":"Cloudflare's email routing has been abused by malicious users for so long that I can no longer reliably use it with my domain, most times Outlook just blocks Cloudflare IP ranges and emails never get routed to my Outlook mail box.","summary":"Long-time Email Routing user who can no longer rely on it because Outlook blocks Cloudflare's forwarding IP ranges, so forwarded mail silently never arrives. Negative — deliverability, the one thing Email Routing has to get right.","claim_ids":["c11","c12"]},{"id":"s14","type":"hn","url":"https://news.ycombinator.com/item?id=48837913","title":"DKIM2 and DMARCbis Have Landed","quote":"They intermittently block Cloudflare email routing IPs too.  All of these security measures and still it comes down to the IP address of your sender.","summary":"Did SPF/DKIM/DMARC correctly, checked blacklists, waited months, and still found Microsoft bouncing entire IP ranges — including, intermittently, Cloudflare Email Routing's. Independent corroboration of the deliverability problem. Negative.","claim_ids":["c11","c12"]},{"id":"s15","type":"independent_report","url":"https://dariusz.wieckiewicz.org/en/when-things-start-to-fail-cloudflare-email-routing/","title":"When things start to fail: Cloudflare Email Routing","quote":"Microsoft is blocking some of Cloudflare's outgoing Email Routing servers.","summary":"An independent operator account of Outlook delivery failures through Cloudflare forwarding infrastructure.","claim_ids":["c11","c12"]},{"id":"s16","type":"publisher_documentation","url":"https://developers.cloudflare.com/email-service/reference/troubleshooting/","title":"Cloudflare Email Service troubleshooting","quote":"Cannot serialize value: [object ArrayBuffer]","summary":"The documented symptom-to-check paths for authentication, provider filtering, bounces, and local binary attachments.","claim_ids":["c13"]},{"id":"s17","type":"stackoverflow","url":"https://stackoverflow.com/questions/79733052/cannot-send-emails-from-cloudflare-worker","title":"Cannot send emails from Cloudflare worker","quote":"I have following code which handles contact form submission which was created with the help of docs, but emails are not getting delivered. I have verified email address in Email routing.","summary":"Followed the official cloudflare:email / EmailMessage sending docs with a verified address and env vars loaded, and mail simply never arrives with no error surfaced. Unanswered. Negative — the outbound side of Email Workers is the part that cannot be relied on.","claim_ids":["c13"]},{"id":"s18","type":"hn","url":"https://news.ycombinator.com/item?id=45376469","title":"Cloudflare Email Service: private beta","quote":"We use sendgrid today, and create subaccounts through it (entirely with API calls) to allow our customers to add and verify their own domains","summary":"A SendGrid customer asking whether Cloudflare's email product can do API-created subaccounts with customer-owned verified sending domains and intact DKIM/SPF. States the concrete capability gap that keeps them off Cloudflare email. Negative-leaning — what it cannot do.","claim_ids":["c14","c15"]},{"id":"s19","type":"reddit","url":"https://old.reddit.com/r/CloudFlare/comments/1u90bev/building_an_email_platform_on_workers_d1_r2/","title":"Building an email platform on Workers + D1 + R2 + Queues — would like architecture feedback","quote":"I’m building Lumimail, an AGPL-3.0 self-hosted email platform that runs inside a user’s own Cloudflare account.","summary":"An entire email platform built on Workers, D1, R2 and Queues, deployed into each user's own Cloudflare account. 24 comments of architecture critique covering Queues behaviour and D1 sizing; the closest match to running email plus admin surfaces on the Cloudflare-only stack.","claim_ids":["c15"]},{"id":"s20","type":"publisher_pricing","url":"https://resend.com/pricing","title":"Resend pricing","quote":"Choose a plan that works for you.","summary":"A current alternative transactional-email plan surface for whole-product comparison.","claim_ids":["c16"]}],"anecdotal_sources":[{"id":"s19","type":"reddit","url":"https://old.reddit.com/r/CloudFlare/comments/1u90bev/building_an_email_platform_on_workers_d1_r2/","title":"Building an email platform on Workers + D1 + R2 + Queues — would like architecture feedback","quote":"I’m building Lumimail, an AGPL-3.0 self-hosted email platform that runs inside a user’s own Cloudflare account.","summary":"An entire email platform built on Workers, D1, R2 and Queues, deployed into each user's own Cloudflare account. 24 comments of architecture critique covering Queues behaviour and D1 sizing; the closest match to running email plus admin surfaces on the Cloudflare-only stack.","claim_ids":["c15"]}],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"cloudflare-os-email","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":16,"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":16,"claims_total":16,"sources":20,"anecdotal":1,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}