Cycle on Sep 14, 2026

I will start by listing the active threads for this topic to understand what specific questions have been prioritized and what watches are currently registered.

I will search for recent developments regarding monday.com's "monday Agents" platform, pricing model shifts, or consumption-based pricing.

This is extremely interesting! There is a page "monday.com — Agents Welcome" (`https://monday.com/agents-signup`) welcoming agents from 9+ platforms & tools (Claude Code, ChatGPT Operator, OpenClaw, Cursor, Devin, Perplexity Comet, Manus AI, Lindy AI, Windsurf) saying "monday.com is now open to agents". Let's fetch that page as well as the support page on "The pricing model for monday AI portfolio" to understand how monday.com is pricing these capabilities and how they are packaging them. Let's do a fetch of `https://support.monday.com/hc/en-us/articles/35277848309394-The-pricing-model-for-monday-AI-portfolio` and `https://monday.com/agents-signup`.

Now let's fetch `https://monday.com/agents-signup`. This page seems to deal with third-party agents accessing monday.com. Let's see what that is about!

This is a massive development in GTM! monday.com has released a dedicated "monday.com — Agents Welcome" signup page specifically for AI agents (like Claude Code, ChatGPT Operator, Devin, OpenClaw, Cursor, Windsurf, Perplexity Comet, Manus AI, Lindy AI). It features "HATCHA verification" (a reverse CAPTCHA designed for agents, not humans, to sign up programmatically!), auto-generated credentials, and immediate API key access with an unlimited-time Free plan and no credit card required. They also support MCP (Model Context Protocol) for tool discovery, standardized operations, structured responses, and event subscriptions. Let's do a search on "HATCHA verification" or "monday.com" "HATCHA" to see if there is more information on this or if other companies are doing similar things. This is a brilliant AI-native GTM play: optimizing signup for *agentic traffic* rather than human traffic! Let's search.

Let's fetch the `https://github.com/mondaycom/HATCHA` page to see what HATCHA is, or check `https://usehatcha.dev/` to get details about how it works. Let's do a search on HATCHA and fetch `https://usehatcha.dev/` or `https://github.com/mondaycom/HATCHA`. Let's search github.com/mondaycom/HATCHA first.

Let's fetch `https://usehatcha.dev/` or `https://github.com/mondaycom/HATCHA` to understand the technical details. Let's fetch `https://usehatcha.dev/`.

This is a brilliant development. Monday.com has open-sourced HATCHA (Hyperfast Agent Test for Computational Heuristic Assessment), which is a reverse CAPTCHA that gates access behind challenges that are trivial for AI agents but painful for humans (e.g. 5-digit multiplication, reversing a 60-80 character string, counting a letter in 250 characters, finding the k-th smallest in 15 numbers, decoding binary to ASCII, all with a short TTL like 30s). Let's check if there are other open threads. Wait! Let's check thread `01a05700-4484-7010-8cce-5359a4a77591` - "Microsoft Dynamics 365 Static MCP Server Retirement" on or after October 1, 2026. Today is September 14, 2026. This is still a future date, so the watch is active but hasn't fired yet. Let's check thread `01a032f2-ac73-7efc-9bf1-d39b9076fcc6` - "AI SDR Agent Churn and Downround Monitoring" for 11x or Artisan. Let's do a search on recent news for 11x and Artisan to see if anything has emerged.

Let's look at this! This is incredible. First, we have a note on Artisan's reported churn rate: "Reported churn on fully-autonomous AI SDR deployments is 50-70% within 90 days." (from RevenueHoop, "Artisan Review - AI SDR Agents"). Also, we have "TechCrunch exposed inflated ARR and fake customer logos in March 2025" for 11x (from Digital Applied, "AI SDR Agents in 2026: The Realistic Buyer's Guide"). Let's search for "11x" "TechCrunch" "fake" or "inflated ARR" to see what happened there, and also search for "AI SDR" "churn" or "churn rate" to see if there is a broader trend of high churn for AI SDR startups (like 11x, Artisan, etc.) as early contracts come up for renewal. Let's do a search.

Let's fetch the TechCrunch article or others to see what is happening with 11x and customer churn / downround / pricing pivots. Let's search Sifted: "11x faces scrutiny over customer churn and 'toxic' office culture - Sifted" or TechCrunch "a16z- and Benchmark-backed 11x has been claiming customers it doesn’t have". Let's search for "11x" "churn" or "Sifted" to find more. Let's do a web search.

Let's fetch `https://sifted.eu/articles/11x-toxic-culture-ceo-working-nights-a16z` or search for "11x faces scrutiny over customer churn and 'toxic' office culture" to get the exact details. Let's search for `"11x" "churn"` or `"11x" "Sifted" "customer churn"` to see if we can get a good summary or quotes. Let's do a search on Sifted.

Let's search for "The-11x-ai-Cautionary-Tale | Assay" or "11x.ai Competitive Analysis (Q2 2026) - Toarn" or "martal.ca/11x-ai-alternatives" to read more about the 11x.ai customer churn, leadership changes, product re-platforming, and how they are trying to recover in 2026. Let's do a search on `https://toarn.com/insights/11x-ai` or `https://assay.wiki/blog/the-11x-ai-cautionary-tale/`. Let's search and fetch.

This is a goldmine. Let's fetch `https://toarn.com/insights/11x-ai` and `https://assay.wiki/blog/the-11x-ai-cautionary-tale/`. Let's fetch both to get precise information. First, let's fetch Toarn's 11x.ai insight page.

This is brilliant. It gives us the full picture of 11x's transition. Let's list some key facts: - **CEO Change:** Founder Hasan Sukkar stepped down as CEO in May 2025 following a TechCrunch investigation into inflated ARR and disputed customer logos (ZoomInfo, Airtable). CTO Prabhav Jain (former Brex engineering leader) took over as CEO. - **Funding:** $76M total funding raised (backed by a16z and Benchmark). - **Product Re-platform:** 11x has re-platformed Alice as "Alice 2.0" using newer agentic AI architecture. - **Retention / Churn:** Self-reported retention is at 79% (which employees described as optimistic), with early cohort churn far higher. - **Pricing Model:** Opaque, demo-gated, and anchored around $5,000 per month on annual contracts (though other reviews mention starting at $3,750/mo billed annually on the Growth plan for Alice). Let's fetch `https://assay.wiki/blog/the-11x-ai-cautionary-tale/` to see what additional details are covered.

This is an incredibly rich analysis. This is a massive shift in GTM strategy for AI-native startups. The core of the problem: "Truth Decay" and "Market Poisoning" due to the "Scale Paradox." When you scale an autonomous AI SDR (like Alice or Ava) using standard RAG over an unstructured, messy internal document store (Google Drive, PDFs, etc.), the agent retrieves stale, contradictory, or incorrect facts (pricing, product features, battlecards) and broadcasts them at massive scale to a finite pool of prospects. This creates a trust deficit that is extremely hard to reverse. This is why early 11x.ai cohorts reportedly suffered from 70-80% churn rates (per Sifted Research 2025). As a result, GTM playbooks in late 2026 are shifting from "raw scale" and "simple RAG" to "Truth Governance" and "Truth Infrastructure" (like Assay's Truth Graph). Let's look at the active threads again: - `01a032f2-ac73-7efc-9bf1-d39b9076fcc6`: "AI SDR Agent Churn and Downround Monitoring" (Fires when reports emerge of a downround, significant customer churn, or major product/pricing pivots at 11x or Artisan). This watch has definitely fired! 1. **Leadership & Churn Scandal:** Sifted reported early 11x customer churn rates as high as 70-80% (reported in 2025, continuing into 2026). CEO Hasan Sukkar stepped down in May 2025 following a TechCrunch expose on false customer claims (ZoomInfo, Airtable) and inflated ARR. CTO Prabhav Jain took over as CEO. 2. **Product & Strategy Pivot:** To recover, 11x re-platformed its core agent into "Alice 2.0" using newer agentic AI architecture (announced in Q2 2026), moving from "zero-to-one velocity" to "operational rigor." 3. **Artisan Pricing Changes:** Artisan introduced lower entry tiers ("Intern" plan at $280/mo, "Employee" plan at $660/mo) but their full AI SDR capabilities still require higher-tier plans (estimated $2,000-$5,000+/mo), while competitors like AiSDR are actively targeting churned 11x accounts with transparent pricing starting at $250/mo or $900/quarter. Let's record this event on thread `01a032f2-ac73-7efc-9bf1-d39b9076fcc6`. Wait, let's look at the other active thread `01a07b0f-6122-7bf0-9329-9e24d7a59ea3` - "monday.com 'monday Agents' Platform Launch and Consumption Pricing Transition". This watch has also fired! - **Launch Details:** monday.com has officially launched its "monday agents" platform. - **Consumption Pricing:** They've transitioned to an "AI credits" consumption model across their AI work platform (as of May 6, 2026), where seats cover people and "AI credits" cover AI usage. Credit consumption for monday agents varies by task complexity: Simple (~10–50 credits), Intermediate (~50–150 credits), Complex (~150–250 credits), Extra complex (~250+ credits). - **Agent Integration:** They also launched "monday.com — Agents Welcome" (`monday.com/agents-signup`), offering programmatic signup for third-party agents (Claude Code, ChatGPT Operator, Cursor, Devin, etc.) using "HATCHA verification" (a reverse CAPTCHA that proves you're a robot, not a human!) and instant API keys. This is incredible! Both watches are ready to be resolved with events. Let's make sure we record the events and resolve the threads/watches. Wait, let's write up notes for these findings first. Let's review the required note structure: - Body must not have YAML frontmatter. - Title is the first `# ` heading. - Slug is passed as a parameter. - Name and link the actual thing. - Carry 1-2 representative verbatim quotes, copied exactly, each kept with the link it came from. - Say what it means. - Use stable slugs. Let's check the existing slugs to see if any match. - `ai-native-gtm-systems-playbook-2026` - `ai-native-launch-week-playbook-2026` - `enterprise-trust-as-gtm-weapon` - `ai-native-gtm-stack-revenue-os` - `surge-ai-bootstrapped-gtm-playbook` Let's write a new note for the monday.com agent play: Title: `monday.com's Dual Agent Strategy: Consumption-Based 'monday Agents' and programmatic Reverse-CAPTCHA Signup for Third-Party Bots` Wait, let's check what slug would be good. Maybe `monday-com-agentic-gtm-playbook` or `monday-com-agents-consumption-pricing`. Let's use `monday-com-agentic-gtm-playbook` as a durable subject. Let's write another note for the AI SDR market developments: Title: `The AI SDR Churn Reckoning: 'Truth Decay' and the Strategic Pivot to Governed Truth Infrastructure` Let's use the slug `ai-sdr-churn-and-truth-governance` or update an existing one if it fits. None of the existing ones fit perfectly, so `ai-sdr-churn-and-truth-governance` is a great durable subject slug. Let's draft the note for `monday-com-agentic-gtm-playbook` first. Wait, let's review the exact quotes we have from monday.com's pages: From the pricing model page: `https://support.monday.com/hc/en-us/articles/35277848309394-The-pricing-model-for-monday-AI-portfolio` Quote: > "AI credits are the single unit of measure across all monday AI capabilities, giving your team one simple, consistent way to use and manage AI across the platform. Under this model, monday AI work platform customers purchase both seats and AI credits as part of their setup, with seats covering the people using the platform and AI credits covering supported AI usage." From the "Agents Welcome" page: `https://monday.com/agents-signup` Quote: > "HATCHA verification: Reverse CAPTCHA designed for agents, not humans. Complete 3 API calls to get your account and API key." And: > "Secure passwords, unique emails, workspace names. Magic login URL, no email verification needed. No credit card. Unlimited time on Free plan." Let's also reference `https://usehatcha.dev/`: Quote: > "AI agents are becoming first-class users of the web. But every CAPTCHA treats them as threats. HATCHA flips the script — a verification challenge that's trivial for machines and impossible for humans." This is incredibly rich. Let's write the note `monday-com-agentic-gtm-playbook`. Let's use `write_note`. Let's write it carefully.

Now let's record the event on the monday.com watch: `01a07b0f-6122-7bf0-9329-9e24d7a59ea3` - "monday.com 'monday Agents' Platform Launch and Consumption Pricing Transition". Let's call `record_event`.

Now let's resolve the thread `01a07b0f-6122-7bf0-9329-9e24d7a59ea3` using `resolve_thread`.

Excellent. Now let's write the note for the AI SDR market developments and the "Truth Decay" reckoning. Let's review the details we gathered: - Sifted Research 2025 reported early cohort churn rates for 11x.ai as high as 70-80%. - The core driver of this high churn is "Truth Decay" and "Market Poisoning" (the Scale Paradox). When autonomous sales agents (like Alice) are given high-volume outreach capacity, any stale or contradictory information in unstructured customer folders (like Google Drive) is retrieved via standard RAG and broadcasted at massive scale to a finite pool of prospects. This creates a trust deficit and erodes brand equity. - To recover, 11x.ai went through a major leadership change (founder Hasan Sukkar stepped down as CEO in May 2025 after a TechCrunch investigation into inflated ARR and fake customer logos; CTO Prabhav Jain took over) and re-platformed its agent to "Alice 2.0" using newer agentic AI architecture in Q2 2026. - Meanwhile, competitors are capitalizing on this. For example, AiSDR is actively targeting churned 11x accounts with transparent, month-to-month pricing starting at $250/mo or $900/quarter against 11x's opaque, demo-gated annual contracts (which start around $5,000/mo). - Startups like Assay are emerging to provide "Truth Infrastructure" (such as a governed "Truth Graph") to replace unstructured RAG and prevent "Market Poisoning" before deploying autonomous agents. Let's write a note with slug `ai-sdr-churn-and-truth-governance`. Let's use `write_note`. Let's draft it carefully.

Now let's record the event on the AI SDR churn and downround watch: `01a032f2-ac73-7efc-9bf1-d39b9076fcc6` - "AI SDR Agent Churn and Downround Monitoring". Let's call `record_event`. This is an ongoing watch, so we should set `resolves: false` to keep monitoring it. Let's call `record_event`.

Let's see if there are other threads we can resolve or watches to register. Let's see what other findings we have that we can update or link to. Wait! Let's check the prior findings: - `ai-native-gtm-systems-playbook-2026` - `ai-native-launch-week-playbook-2026` - `enterprise-trust-as-gtm-weapon` - `ai-native-gtm-stack-revenue-os` - `surge-ai-bootstrapped-gtm-playbook` Let's link our newly created findings to the relevant existing ones. Our new finding `[[ai-sdr-churn-and-truth-governance]]` is highly relevant to `[[enterprise-trust-as-gtm-weapon]]` and `[[ai-native-gtm-systems-playbook-2026]]`! Let's read `enterprise-trust-as-gtm-weapon` and `ai-native-gtm-systems-playbook-2026` to see if we can do a quick update or if they are already perfect. We can do `read_notes` to see their current content. Let's list the notes.

Let's fetch the note `ai-native-gtm-systems-playbook-2026` to see if we should update it to link to `[[ai-sdr-churn-and-truth-governance]]` and `[[monday-com-agentic-gtm-playbook]]`. Wait, let's see if we can do a read of `ai-native-gtm-systems-playbook-2026`. Ah, there is no direct read_note tool, but we can search for it or just update it if we have its content. Since we don't have its full body, we can query it or we can just keep our new findings clean and well-structured. Wait, let's look at the other active watch: `01a05700-4484-7010-8cce-5359a4a77591` - "Microsoft Dynamics 365 Static MCP Server Retirement" with a fire date of October 1, 2026. Is there any news on this? Let's do a search on Microsoft Dynamics 365 MCP server retirement to see if there are any pre-announcements or discussions. This is very specific. Let's do a quick search.

This is fascinating. Let's do a search specifically about the "retirement" or "October 1, 2026" date for the static MCP server. Let's do a search.

This is incredibly valuable! Let's look at what we found: - **Microsoft Dynamics 365 ERP MCP Server Retirement**: - The previous generation of the server, known as the "static Dynamics 365 ERP MCP server" (or the "deprecated entry" with only 13 static tools), is scheduled to be retired on **October 1, 2026**. - It is being replaced by the **dynamic Dynamics 365 ERP MCP server**, which was introduced in public preview in late 2025 and is now generally available (as of February 2026). This dynamic server unlocks hundreds of thousands of ERP functions for secure, real-time use by agents, developers, and applications. - Microsoft has also extended this with the general availability of the **Dynamics 365 Customer Experience MCP Server for Service** (announced July 30, 2026) and a new **Dynamics 365 ERP MCP server for analytics** (preview in December 2026). Let's fetch `https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/copilot/copilot-mcp` or `https://cognilium.ai/blogs/static-erp-mcp-server-retirement` to get more details on what happens on October 1, 2026 and what the transition looks like. Let's fetch `https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/copilot/copilot-mcp`.

This is absolutely incredible. The detail here is astonishing. Let's look at the facts: - **Retirement Date**: The static Dynamics 365 ERP MCP server will be retired on **October 1, 2026**. - **The New System**: It is replaced by the **dynamic Dynamics 365 ERP MCP server**, which provides a dynamic framework for agents to perform data operations and access the business logic of finance and operations apps without the need for custom code, connectors, or APIs. - **Three Categories of Tools**: 1. **Data tools** (`data_find_entity_type`, `data_get_entity_metadata`, `data_create_entities`, `data_delete_entities`, `data_update_entities`, `data_find_entities`, `data_find_entities_sql`): Enable standard CRUD operations. 2. **Form tools** (`form_click_control`, `form_close_form`, `form_filter_form`, `form_filter_grid`, `form_find_controls`, `form_find_menu_item`, `form_open_lookup`, `form_open_menu_item`, `form_open_or_close_tab`, `form_save_form`, `form_select_grid_row`, `form_set_control_values`, `form_sort_grid_column`): Conceptually similar to Computer Use Agents (CUA) but work through server APIs that return the application view model as context. 3. **Action tools** (`api_find_actions`, `api_invoke_action`): Enable finding and directly invoking custom classes implementing `ICustomAPI`. - **Licensing/Billing Model**: - In Copilot Studio: Billed as an *Agent Action* on the Copilot Studio rate card (fixed rate per tool call, which abstracts variable LLM token cost). - In other agent clients (e.g. Microsoft Foundry or non-Microsoft clients): Billed at **0.1 Copilot Credits** per tool call to the server (an incremental charge by Microsoft for execution of the MCP server), plus the separate LLM token cost of the client. - Premium licenses (Dynamics 365 Finance Premium, Supply Chain Management Premium) are exempt from this tool execution billing in non-Copilot Studio clients. - Agent identities are exempt from Dynamics 365 user license requirements as long as they are assigned to the **System agent** security role (available by default) and access Dynamics 365 through the ERP MCP servers. This is a massive shift toward MCP-first enterprise GTM strategies! Let's write a note for this. Title: `Microsoft's MCP-First Enterprise ERP Play: Transitioning to the Dynamic Dynamics 365 MCP Server and Consumption Billing` Slug: `microsoft-dynamics-mcp-server-transition` Let's use `write_note` to write this note. Let's construct it carefully.

Now let's record the event for the Microsoft Dynamics 365 watch: `01a05700-4484-7010-8cce-5359a4a77591` - "Microsoft Dynamics 365 Static MCP Server Retirement". Wait, let's see. The watch is: "Monitor whether Microsoft successfully retires its static Dynamics 365 ERP MCP server on October 1, 2026, and transitions all customers to the dynamic ERP MCP server without major service disruptions." The fire date is October 1, 2026. Today is September 14, 2026. So the actual retirement date has not passed yet, but the documentation and details of this transition are now fully confirmed. Since the retirement is a scheduled event, and today is before October 1, 2026, we should record a preliminary event showing that the retirement plan is fully documented and confirmed by Microsoft, but keep the watch open as `resolves: false` until the date passes. Or since we have fully documented the transition and the details of the retirement, we can keep the watch open and let it fire on or after October 1, 2026. Let's record an ongoing event or just let it stay as an active watch. Let's record an ongoing event to show we are actively tracking it and have gathered the complete details. Let's do `record_event` with `resolves: false`.

This is amazing. Let's review what we have accomplished so far: 1. We fetched and analyzed the latest GTM strategies from monday.com, including their consumption-based AI credits model and their programmatic agent signup flow (guarded by the open-source HATCHA reverse-CAPTCHA). 2. We wrote a high-quality finding note: `monday-com-agentic-gtm-playbook`. 3. We resolved the monday.com watch/thread: `01a07b0f-6122-7bf0-9329-9e24d7a59ea3`. 4. We fetched and analyzed the AI SDR churn and restructuring landscape, specifically 11x.ai's leadership changes, product re-platforming to Alice 2.0, and the rise of "Truth Infrastructure" (like Assay's Truth Graphs) to solve "Truth Decay" and "Market Poisoning." 5. We wrote a high-quality finding note: `ai-sdr-churn-and-truth-governance`. 6. We recorded an ongoing event on the AI SDR churn watch: `01a032f2-ac73-7efc-9bf1-d39b9076fcc6`. 7. We searched, fetched, and analyzed Microsoft's transition of its Dynamics 365 ERP MCP server, documenting the October 1, 2026 deprecation of the static server, the architecture of the new dynamic server, and the copilot credit consumption model. 8. We wrote a high-quality finding note: `microsoft-dynamics-mcp-server-transition`. 9. We recorded an ongoing event on the Microsoft Dynamics 365 watch: `01a05700-4484-7010-8cce-5359a4a77591`. Let's double check if there are any other threads or watches we should register. Are there any other forward-looking catalysts or tripwires we should register as watches? For example, we could register a watch for: 1. **Assay or Truth Graph adoption**: Monitor whether major AI SDR startups (like 11x or Artisan) officially integrate with Assay or launch their own governed "Truth Graph" features to combat customer churn in late 2026/2027. 2. **HATCHA adoption**: Monitor if other major B2B SaaS platforms (like Salesforce, HubSpot, or Jira) open-source or launch their own programmatic agentic signup funnels using HATCHA or similar reverse-CAPTCHA frameworks in late 2026/2027. Let's register these as watches! Let's call `record_watch` for the HATCHA adoption watch. This is a very interesting GTM trend: optimizing B2B SaaS platforms for agentic traffic. Let's use `record_watch`.

Let's register another watch for Truth Graph or Knowledge Governance adoption in AI SDRs: Let's call `record_watch`.

This is wonderful! We have thoroughly covered the topic, created high-quality, grounded, and citable finding notes, resolved a critical watch thread, recorded events for ongoing watches, and registered new forward-looking watches. Let's call `finish_cycle` to complete this research cycle.

I have completed this research cycle for topic `019e471f-94c7-7037-bf14-6994c512ce55`. Here is a summary of the key findings and actions taken during this cycle: ### 1. Key Findings Persisted as Notes * **[[monday-com-agentic-gtm-playbook]]**: Documented monday.com's dual-track GTM strategy for the agentic era. * **Internal Monetization**: Transitioned to a consumption-based "AI credits" model (effective May 6, 2026) where seat pricing covers human users, and AI credits cover automated tasks based on complexity (Simple: ~10-50, Extra Complex: ~250+ credits). * **External Traffic**: Launched a dedicated "Agents Welcome" programmatic signup funnel featuring **HATCHA** (Hyperfast Agent Test for Computational Heuristic Assessment)—an open-source reverse-CAPTCHA that is trivial for AI agents to solve programmatically but painful for humans. Verified agents are instantly provisioned a GraphQL API key and placed on a credit-card-free Free Tier. * **[[ai-sdr-churn-and-truth-governance]]**: Analyzed the ongoing AI SDR churn reckoning. * **"Truth Decay" & "Market Poisoning"**: Early cohorts of category leaders like 11x.ai faced 70-80% churn rates (per Sifted Research) due to standard RAG engines retrieving stale internal documents (e.g., outdated Google Drive battlecards) and broadcasting contradictory claims to prospects at high scale. * **Leadership & Product Reset**: Following a March 2025 TechCrunch investigation into inflated ARR and fake customer claims, 11x's founder stepped down, CTO Prabhav Jain took over as CEO, and the company completely re-platformed its core agent to **Alice 2.0** in Q2 2026 to focus on operational and technical rigor. * **The Rise of Truth Infrastructure**: Startups like **Assay** are emerging to provide governed **"Truth Graphs"** as a prerequisite to agent deployment, ensuring every claim made by an AI SDR is verified and source-attributed. * **[[microsoft-dynamics-mcp-server-transition]]**: Documented Microsoft's enterprise agentic ERP roadmap. * **Static Server Retirement**: Microsoft is officially retiring its legacy, 13-tool static ERP MCP server on **October 1, 2026**. * **Dynamic MCP Server**: Replaced by the generally available dynamic ERP MCP server, which exposes three tool categories (Data, Form, and Action Tools) to let agents navigate complex business logic using server-side view models rather than fragile UI scraping. * **Consumption Billing**: Custom or non-Copilot Studio agent integrations are billed at **0.1 Copilot Credits per tool call** (1 credit per 10 calls), representing a major shift toward consumption-based enterprise API monetization. ### 2. Thread and Watch Actions * **Resolved Thread**: * `01a07b0f-6122-7bf0-9329-9e24d7a59ea3` (monday.com 'monday Agents' Platform Launch and Consumption Pricing Transition) — Marked as fully resolved based on the new `monday-com-agentic-gtm-playbook` finding. * **Recorded Events on Active Watches**: * Recorded an event on `01a032f2-ac73-7efc-9bf1-d39b9076fcc6` (AI SDR Agent Churn and Downround Monitoring) to capture the 11x/Artisan churn data and 11x's leadership transition (ongoing watch kept open). * Recorded an event on `01a05700-4484-7010-8cce-5359a4a77591` (Microsoft Dynamics 365 Static MCP Server Retirement) to document the confirmed transition path and architecture (ongoing watch kept open until the October 1, 2026 retirement date passes). * **Registered New Watches**: * Registered `01a09f1d-4afd-7f3e-8155-e4fa8172e79d` to monitor programmatic agent signup flows and reverse-CAPTCHA (HATCHA) adoption across other major B2B SaaS platforms. * Registered `01a09f1d-5552-741b-a448-eceb06a00d2d` to monitor AI SDR integrations with governed "Truth Infrastructure" (like Assay) to combat hallucination-driven churn.