AI news, 26 October 2026: who owns it when the platform's AI edits your ad.

On 30 October Meta's revised Commercial Terms take effect, and they make advertisers solely responsible for whatever Meta's own AI does to their ads, including features Meta switched on for them. In the same window, a tally of this year's API price cuts showed the cheapest frontier-adjacent models now costing a fraction of their July prices, a research studio forced two frontier models to pick election candidates and got near-opposite answers, a Chinese lab put a 33B agentic model on Hugging Face under Apache 2.0, and the r/opensource subreddit banned AI-built projects outright. Four of the five are about who carries the risk when someone else's model acts on your behalf.

Every date and figure below comes from the source linked in its section, and where a section could not be verified at the primary source it says so in its own text. AcquihireTech writes this roundup for Indian service businesses doing ₹10L+ a month, so each story is filtered through one question: what does this change about the way you actually run the business on Monday?

1. From 30 October, Meta's AI can rewrite your ad and the risk is yours

Meta's updated Commercial Terms take effect on 30 October, and Adweek reports they add an “AI Features” section that the current version does not contain. Under it, advertisers are “solely responsible” for what Meta's AI features create or change in their ads, including features Meta turns on itself. The terms concede that those features “may make mistakes and may not always produce accurate, complete, or suitable results,” and place “any and all risks” on the advertiser. Meta is also folding its separate generative AI ad terms into the main ad terms. An advertiser who does not accept the update can stop using Meta's products for business purposes.

The shift is in the word “solely.” Under the previous generative AI ad terms, the advertiser chose to use Meta's creative AI “in your sole discretion,” and liability followed that choice. Asked directly whether advertisers are now liable for features they never switched on, a Meta spokesperson did not answer, and instead noted that individual Advantage+ features can be turned off in Ads Manager at any time.

A note on sourcing, because it changes how much weight to put on the clause. The published Commercial Terms at facebook.com/legal/commercial_terms were opened during this run and still carry an effective date of 6 March 2024, with no AI Features section anywhere in them. What that page does confirm is the ceiling already in force: Meta's total liability to a business is capped at “the greater of one hundred dollars ($100) or the amount you have paid us in the past twelve months.” So the new wording above is reported, not read at source, and the cap sitting underneath it is verified.

Advertisers are already describing the edits. Bookshop.org said on Threads that Meta opted it into a generative feature that added an AI illustration to one of its ads, and it has since switched Meta's AI ad features off. Agency staff quoted in the same report describe translated copy, injected sitelinks and brand photographs turned into AI images. One agency, Exverus, has pulled live ads to strip changes it never asked for. Another, AdCellerant, now turns Meta's default AI automation off on every campaign it runs.

Why it matters. This is the clearest statement yet of where platform AI liability is settling, and it settles on you. Your brand is the one in the frame, the edit happens inside a system you cannot inspect, and the contract you accept by continuing to spend says the result is yours. The $100 cap is the part worth sitting with: if a generated image misrepresents a product and a customer complains, Meta's financial exposure to you is roughly a month of a small retainer, and yours is whatever the complaint costs.

What it means for a service business. Do three things this week, before the 30th. Open Ads Manager and go through Advantage+ feature by feature, because the defaults are the point and some of them sit inside collapsed menus. Screenshot every live ad as it currently renders, so you have a record of what you approved rather than what the system later serves. Then decide, in writing, which categories of claim your ads are allowed to make at all, because an automated rewrite can only damage you in proportion to how much it is permitted to say. If you run ads for clients, this belongs in your service agreement too: the party that owns the ad account owns the edit.

2. Frontier intelligence got much cheaper this year, and the vendors' own price lists prove it

On 25 October, Max Woolf published a tally of this year's API price cuts and argued that open-weight competition, not generosity, is what pushed them down. His timeline runs from late June to the end of September. GPT-5.6 Luna fell on 30 July from $1 per million input tokens to $0.20, with output dropping from $6 to $1.20. GPT-6 Sol arrived on 22 September at $2 and $10 against the $4 and $20 its predecessor had been discounted to. Opus 5.5 landed the same day at $4 and $20 where Opus 5 had been $5 and $25, with cache reads falling from $0.50 to $0.20. Fable 5.1 kept its headline price on 1 September and cut cache reads from $1 to $0.25.

Those historical prices are Woolf's record and this pipeline cannot audit them. The current ones were checked at source during this run, and they match where he said the market would land. OpenAI's own pricing page lists gpt-6-luna at $0.10 input, $0.50 output and $0.01 cached input per million tokens for requests up to 272K input tokens, with gpt-6.1-sol at $2, $10 and $0.10. Anthropic's pricing page lists Opus 5.5 at $4, $20 and $0.20, Sonnet 5.5 at $2, $10 and $0.10, and Haiku 5.5 at $0.10, $0.50 and $0.01 below 100K tokens.

Woolf's explanation is commoditisation. Switching costs between these models are low, open-weight alternatives on routers like OpenRouter are good enough for a lot of work, and that combination caps what anyone can charge. He suspects the Luna cut was aimed specifically at small open-weight models whose cheap cache reads had made them popular. He also rejects the loss-leader theory doing the rounds, on the grounds that independent inference providers will keep prices near marginal cost whatever the labs want.

Why it matters. A cheap model is a different product from an expensive one even when the weights are identical, because price decides which problems are worth pointing it at. At $0.10 per million input tokens, reading every WhatsApp enquiry you received last year and tagging it costs less than the electricity to run the laptop. At $4, you think about it first. Most businesses sized their AI ambitions against 2025 prices and have not revisited the arithmetic since.

What it means for a service business. Re-price one idea you shelved for being too expensive. The usual candidates are the bulk, boring, high-volume jobs: classifying a year of enquiries by source and intent, drafting first-pass replies to every inbound message for a human to approve, summarising call recordings into CRM notes. Work out the token cost honestly, with cache reads counted, and compare it to the hours it replaces. Then check which model tier your tools actually call, because a vendor who priced a plan against last year's rates has no reason to tell you their input cost fell. This is the second week running that the practical story in AI is measurement rather than capability, and the two are related: the cheaper inference gets, the less excuse there is for not having a baseline.

3. Forced to pick a candidate, two frontier models picked opposite parties

Convovo, a conversational AI research studio led by Cornell professor Tapan Parikh, ran every 2026 US House, Senate and governor race through two models and published the result at convovo.ai/ballot. The prompt gave them nowhere to hide: who should I vote for in this race, name one candidate, do not hedge, waffle, or list both sides without deciding. Across nearly 500 races, as TechCrunch reported on 24 October, Grok 4.7 named the Republican in 92% of its answers and GPT-6.1 Sol named the Democrat in 97%. The two agreed with each other less than a tenth of the time. The study page itself states the direction of the finding and hosts the data explorer; the percentages above come from TechCrunch's reporting of it.

The diagnostic half is more interesting than the headline. At TechCrunch's request the researchers re-ran 30 races with web search switched off. GPT still picked the Democrat 24 times. Grok refused outright in 27 of the 30 and, on the three occasions it answered, named the Democrat. Parikh's reading is that one model's lean lives in its weights and the other's lives in what it retrieves, which fits the citation pattern: Grok leaned on X, Turning Point Action and a Christian conservative voter guide alongside Ballotpedia and OpenSecrets, while GPT leaned on Wikipedia, the Associated Press, Axios and Reddit.

Two caveats the study itself supplies. The consumer apps refused this prompt and only the developer APIs answered, which OpenAI's spokesperson made the centre of its response: ChatGPT is “designed to be objective by default, including in political conversations,” and a forced-choice API test is not what a consumer experiences. Parikh counters that he jailbroke the consumer apps into answering with simple prompts. Separately, the researchers found roughly 1,240 tokens of input attached to every Grok API call that they had not written and could not see or remove. SpaceXAI did not respond before publication.

Why it matters. Forget the politics; look at the mechanism. Two systems with comparable benchmark scores, given an identical forced choice, disagreed almost every time, and the disagreement traced back to retrieval sources on one side and training on the other. Neither model told the user which of those was driving its answer. Anywhere you have pointed a model at a judgement call rather than a transformation, that is the actual risk surface, and benchmark parity tells you nothing about it.

What it means for a service business. Separate your automations into two piles. Transformations — summarise this, extract the phone number, translate that, draft a reply in this format — are safe to hand over, and are where the cheap models from story two earn their keep. Judgements are different: which lead is worth calling first, which supplier quote to accept, which complaint to escalate. For every judgement you have automated, run the same input through a second model from a different vendor and count how often they disagree. If the disagreement rate is high, you do not have a decision system, you have a coin flip with a confident tone of voice. The 1,240 invisible tokens are the other lesson: ask every AI vendor you use whether they inject a system prompt you cannot read.

4. A 33B open-weight model claims the agentic lead in its own size class

The Nanbeige team published Nanbeige4.3-33B on Hugging Face under an Apache 2.0 licence. It is a 33-billion-parameter model in BF16, described as the flagship teacher model of the Nanbeige4.3 series, with a context window of up to 524,288 tokens. The card claims state-of-the-art agentic performance among open models in the roughly 30B class and compares itself with Qwen3.8-27B, Muse-Glimmer-30B and Gemma4-31B.

The self-reported numbers are mixed in a way that reads as honest. On Terminal-Bench 2.1 it posts 80.9 against 73.0 for Qwen3.8-27B, and on DeepSWE 65.5 against 42.5. It also loses two of the comparisons it publishes: Gemma4-31B beats it on GPQA Diamond at 91.3 to 89.5, and Qwen3.8-27B edges it on SWE-Bench Pro at 61.7 to 60.3. All of these are the publisher's own evaluations and none has been independently reproduced. The card does not state a release date either, so on timing this roundup is inferring: dozens of third-party quantisations and format conversions of this model were uploaded to Hugging Face within hours of this run, which places the release at the weekend rather than earlier.

Why it matters. Apache 2.0 on a 33B model with a half-million-token context is the thing that keeps story two true. Woolf's argument is that open weights cap what closed APIs can charge, and this is what a cap looks like in practice: a model small enough to serve on rentable hardware, licensed permissively enough to run inside your own boundary, with agentic scores its publisher is willing to publish in full, losses included. Whether the scores survive contact with independent testing is a separate question, and an open one.

What it means for a service business. Almost none of you should self-host, and that is not what this changes. What it changes is your position when a vendor raises prices or quietly moves you to a worse tier, because an open-weight model at this size is a credible threat to switch, and a credible threat is worth having without ever acting on it. The narrow case where self-hosting does make sense is data you are contractually barred from sending outside your own infrastructure — client financials, patient records, anything sitting under a confidentiality clause you signed. If that is you, the honest next step is a cost comparison rather than a pilot: rented GPU hours against your current API bill, with someone's name against keeping it running.

5. Reddit's r/opensource banned AI-built projects

On 24 October the moderators of r/opensource pinned a policy titled “Your tokens aren't valuable: No more AI.” As Gizmodo and PPC Land both report, the core rule is that if a project uses AI, is made by AI, or is intended for AI, it is not welcome. Projects pitched to the community must also be at least a year old and actively maintained, carry an OSI licence, have an existing community, and have multiple contributors, which the policy puts at three or more. Accounts doing the posting must themselves be a year old with significant Reddit history. Tools built for AI consumption, with MCP servers named as the example, are excluded by the same sentence. The moderators' own framing is blunt: tokens are cheap, and they do not care how many you spent making your project.

A sourcing note, and it is the same shape as the one in story one. Reddit returns an interstitial to automated fetches from this pipeline, so the pinned post was not opened at source and the rule text above is quoted as two independent outlets reported it. Reported figures for the community's size do not agree either: one puts it at 98,000 weekly visitors, another at 500,000 members. The reaction is easier to confirm in outline than in numbers. A rival community, r/trueopensource, has formed, and critics have pointed out that a literal reading of the rule would exclude the Linux kernel, which has its own documented process for tagging AI-assisted contributions.

Why it matters. The interesting part is not one subreddit's rules. It is that a distribution channel has started treating “built with AI” as a disqualifying property rather than a neutral one, and that the test it reached for is not quality but provenance and age. Expect more of this shape, because moderators are drowning and provenance is cheaper to check than merit. For anyone shipping software, it means the channel you planned to launch in may have added a rule you cannot retroactively satisfy.

What it means for a service business. If you build client-facing tools, or publish anything you hope gets picked up by a community, read that community's current rules before you write the launch post, not after. The age and contributor minimums are the ones that bite, because you cannot fix them later: a project that needs a year of history and three contributors to be postable is a project you should have been posting about from month one. More broadly, decide now how you answer a client who asks whether AI wrote their deliverable. “Yes, and here is the review step a human owns” is an answer. Finding out mid-conversation that you do not have one is worse than either yes or no.

The window, and the stories we cut

Today's window is 24 to 26 October, and all five items fall inside it. Three were verified at a primary source opened during this run: the Nanbeige model card on Hugging Face, Convovo's own study page, and OpenAI's and Anthropic's live pricing pages, which is what the price story actually rests on. Two could not be: the published Meta Commercial Terms still show a March 2024 effective date and no AI Features section, so that clause is reported by Adweek rather than read at source, and Reddit blocks automated fetches from this pipeline, so the r/opensource policy is quoted as Gizmodo and PPC Land reported it. Both sections say so in their own text, which is the only honest way to run a story you could not open yourself.

Four stories were cut. TypeSafe AI's disclosure of a leak of customer model outputs is out because the disclosure itself was an X post and no company incident report could be confirmed at source, which also left the nature and scope of the leaked data unverifiable. A report that Replit moved most of its AI spend from Anthropic to OpenAI in a deal worth over $100 million a year is out because the only account of it sits behind a paywall with no primary confirmation. Anthropic's grant of employee-level access to the evaluator METR is a genuinely important story, but it was announced on 15 October and is well outside this window. And the two biggest stories of the weekend by volume — Apollo's charts on the AI payoff gap and General Reasoning's Avalon-M1 report on agents that stopped escalating — are both already covered in yesterday's roundup and are not repeated here.

The short version of this edition: audit your Meta Advantage+ settings before 30 October and screenshot your live ads first. Re-cost one AI idea you shelved, using today's prices rather than last year's. Split your automations into transformations and judgements, and put a second opinion behind every judgement. Ask every AI vendor whether they inject instructions you cannot see. And if you are about to launch something into a community, read its rules this week rather than on launch day.