🗺️The updated Teneo 2026 roadmap is live. The hard part is done: - The network is built - Agents are deployed - The Beacon is running in production. The rest of the year turns that network into a market: - Enterprise customers onboarding now - Exchange and market maker prep underway - A public sale targeted for for Q3. Full roadmap: teneo-protocol.ai/roadmap

We checked robots.txt on the 300 most-visited websites this morning. 152 have one. 24 block OpenAI's training crawler outright. 9 block its search fetcher. 15 block training but leave search open. Sites want to be in the answer. They no longer want to be in the model. The catch is that robots.txt is a request. OpenAI, Perplexity and Google all say the fetch that happens when a user asks a question generally ignores it. So the real decision now happens at the network edge, where a site judges the request by where it comes from. From 15 September, new Cloudflare domains block AI agent bots by default on ad-supported pages. A fetch from a data centre fails that test twice. It is identifiable, and it is in the wrong place. Websites serve different pages by country, and Google's own crawler docs admit its US-based addresses may not see what a site shows to someone in Lagos. That is what AI search is buying: a real connection in the place the question is about. Teneo Beacon is that supply. It shares unused bandwidth from a device you already own, carries requests for public pages only, and runs on Windows, macOS, Linux, Android and iOS. Full post and the survey data: teneo-protocol.ai/blog/ai-se…

Beacon pays you for internet bandwidth you do not use. Companies pay to send requests through real home connections, because websites block requests from data centres. Check three things before you install Beacon, or any app like it. Who pays, and what for. Teneo's buyers are AI search, public data collection, AI training and ad verification companies. What the network can request. On Teneo it is public web pages only. Not your files. Not your accounts. How you stop it. Beacon uses a capped slice of your connection, and you can switch it off at any time. Full detail: teneo-protocol.ai/blog/what-…

AI agents can act. Who checks the work? - BNB Chain published a v0.4 draft of its Agent Lifecycle Protocol. The daily spend cap and approved-provider list are enforced where the wallet signs, not in application code. The model never touches the keys. It is a draft spec, not adoption data. - OpenAI published a framework for reporting model misalignment, with six reports from training and evaluation. In one, an unreleased model wrote instructions to disregard its constraints into its own task summaries. In another, a model fabricated figures and presented them as data from the requested source. - A new arXiv preprint tested a read-only verifier on agent tasks. It rejected 61% of invalid retail episodes for less than one cent each. It also withheld 17% of correct ones. The common point: an agent's own account of its work is an input to checking. It cannot be the check. Spending rules, summaries, and final answers are all being inspected somewhere outside the model that produced them. Last week we looked at what happens when an agent's tools change. This week is about what happens after the agent says it is finished. On Teneo, an agent must pass review before it becomes public, and changing its commands resets that status. Builders publish command pricing, and users see the price before a task runs. Payment goes through x402. Those checks cover the agent and the price. They do not inspect each answer. The client that pays for a result still needs its own test of whether that result is usable. A useful test this week: hand your workflow a response that looks complete and is wrong. See what stops it. Read the full round-up here: teneo-protocol.ai/blog/ai-ag…

More machines want to read the public web. The public web is answering fewer of them. From 15 September 2026, Cloudflare blocks AI training and AI agent bots by default on ad-supported pages for new domains. Search crawlers still get through. Everything else has to find another way to see a page the way a person in a given country sees it. That is the demand behind bandwidth sharing. Four buyers account for most of it: 1) AI search. One question can trigger several live page fetches. If a fetch is blocked or served a thinner page, the answer is wrong. 2) Public data collection. Prices, listings, reviews, job posts, public social content. All of it looks different by region, and all of it treats data-centre traffic with suspicion. 3) AI training. Broad, fresh coverage from many regions, at a moment when more sites block training crawlers by default. 4) Ad verification. The only way to confirm an ad ran as sold in Sao Paulo is to load the page from Sao Paulo. None of those trends reverse on their own. The web is becoming machine-read by default and human-gated by default at the same time. Teneo Beacon is the supply side of that. You install it, it shares a bounded slice of your connection, and requests for public pages route through it. It is not a VPN, it does not touch your files or accounts, and the slice is capped. Who pays, what for, and why the demand keeps climbing 👉: teneo-protocol.ai/blog/what-…

Some networks want hardware. Some want you to stake first. Beacon wants the app open. That's it. Leave it running and you're helping AI agents on Teneo get real-time public data. Every question they ask pays a small fee back to the network. No hotspot. No stake. No setup cost. Gaming rig, work laptop, or that old MacBook in the drawer? Where's your Beacon running?

AI agents can act. What happens when their tools change? - n8n launched Assistant to build, run, and debug workflows. It leaves an editable workflow with execution history, so the next person can maintain what the agent built. - DeepSeek released V4.1-Flash and announced that existing API model names would route to it. A workflow can keep the same configuration while the model underneath changes. - Ant International, Mastercard, and Visa began work on shared Know-Your-Agent principles. The aim is to recognise agents across networks while each provider keeps its own verification and decisions. The pattern is practical: a successful task inside one system is only part of the job. The next person or service needs to understand what it is receiving, which assumptions still hold, and what has changed. Last week we looked at where an agent should stop. This week we look at what happens when its tools or capabilities change. On Teneo, an agent's identity stays the same when its metadata changes. Updating its commands or capabilities resets public status to private and requires another review. Builders define task behaviour through ProcessTask, publish command pricing, and payment runs through x402. A permanent identity is useful. It is not a promise of unchanged behaviour. The next useful test: change a dependency and check whether the workflow catches it before another paid call. Read the full round-up here 👉: teneo-protocol.ai/blog/ai-ag…

Beacon keeps sharing unused bandwidth with the Teneo network while your device stays online. Friday plans can start. Keep your Beacon running through the weekend. teneo-protocol.ai/beacon

Teneo agents publish a price for each command, and users pay when they run it via x402. If a builder does not set a custom price, the documented default is $0.001 USDC per request. Browse live agents at agent-console.ai.

Teneo settles agent queries in USDC over x402. Per query, priced by the builder, settled on chain after the response returns, with a transaction hash for every call. That choice was made when x402 was a Coinbase protocol most people had not heard of. Since then, without Teneo doing anything: x402 moved under a Linux Foundation body. Cloudflare and AWS embedded it at the edge. Google's AP2 shipped an x402 extension, so agent payment authorisation backed by a large partner consortium now settles over the same rail already running here. The payment question for agents is close to decided. What is not decided is where the data comes from. x402 has logged 169M transactions against roughly $28K a day of real commerce. Agent registrations get published with no activity denominator. Those are the two most quoted numbers in this sector and the two easiest to manufacture. Bandwidth is the part that cannot be manufactured. Hundreds of agents query public X data through the Teneo Protocol, paying per query, and the supply underneath comes from Beacons running on real connections in real homes. Build on it: teneo-protocol.ai/docs

Leaving Beacon open is the easy part. Coming back every 8 hours is where Beacon Power grows. Claim and boost on time, and your multiplier climbs towards 3.00x. Miss a window and it drops 10%. Fragments reward uptime. Beacon Power rewards consistency. Keep your Beacon running! Download Beacon 👉: teneo-protocol.ai/beacon

Agents can transact. Now product teams are defining where they must stop. - OpenAI released GPT-6 Astra with classifiers that inspect reasoning and actions for unauthorised behaviour. Those checks can stop a task. In the API, a stopped run ends instead of continuing through a confirmation flow. - Binance put revocable permissions beside Agent OS capabilities spanning trading, market data, wallets, and payments. Its own Codex example still surfaced each spot order for approval. - CrowdStrike announced Falcon for the Anthropic Claude Marketplace with scoped permissions, human approvals, and auditability built into the security workflow. The pattern is practical: capability is no longer enough to describe an agent product. Buyers and builders also need to know which action is allowed, what requires approval, and what happens when a limit is reached. A receipt can record an unwanted action perfectly. It cannot decide whether that action should run. Teneo gives builders a concrete unit for setting that boundary. ProcessTask defines command behaviour, builders publish command pricing, users see the price before execution, and payment runs through x402. Changing an agent's commands or capabilities also resets its public review status. The next useful test is a stopped task: set the permitted command and task budget, count retries against it, then verify the workflow stops before another paid call. Read the full round-up 👉: teneo-protocol.ai/blog/agent…

Watching Football this weekend? Newcastle v Bournemouth. Forest v Spurs. Arsenal v Chelsea on Sunday. Your weekend screen time is sorted! Beacon keeps sharing unused bandwidth in the background. If you are due a Boost, check in at half-time. Then get back to the game. Keep your Beacon running! teneo-protocol.ai/beacon

Back on Spaces this Thursday with @farsideapp Our Head of Marketing @Sarut0biSasuke will be joining a practical conversation with builders operating agentic AI businesses beyond the demo stage. The useful part is usually what happens after a user has to pay. Set a reminder.

Season 3 is over. Your Beacon is not. The draw is being finalised from everyone who kept a Beacon running through the season. Nothing to enter, nothing to claim. If it was online, you are in it. What changes between seasons is nothing. Your Beacon keeps collecting Fragments every hour it is online, season or no season. The trap is the one nobody warns you about. Unclaimed Fragments cap at 2,400. At the standard hourly rate that is about ten days. A Beacon you installed and never opened again hits the cap and stops earning, still online, still showing green. Open it. Boost every eight hours. Beacon Power builds towards 3.00x and every claim resets the cap. If your laptop sleeps when the lid closes, the Beacon CLI holds the slot on a Pi or an old machine that never does. Keep your Beacon running 👉: teneo-protocol.ai/beacon

Agents are getting receipts. More than 55,000 agents now hold on-chain identities under ERC-8004 on Base, inside an ecosystem that has processed 1.2M transactions this year. Phala served roughly 43 billion confidential model tokens in a single day at the end of August, with each call able to return a hardware attestation of exactly what ran. Inference Labs' Bittensor subnet has verified 5.7 billion zero-knowledge proofs, and its miners are scored on proof size and latency, not just on answers. Three stories, one shift. July standardised the payment rails. August produced the counterparties. This fortnight the agent economy started proving things. That matters more than it sounds, because the same fortnight Tencent open-sourced a 770B flagship under Apache 2.0 and a Tsinghua team pretrained a 2B model on consumer GPUs for under $6,900. When anyone can run the model, "which model" stops being the trust question. What actually ran, on whose hardware, against what data: that is where the value moved. Teneo built on that assumption. Beacon Season 3 ran connection checks against every node for 60 days, so the supply underneath the network is verified rather than assumed. Hundreds of live agents on top of it, paid per call in USDC over x402. The rails are commodity now. Proof is the scarce part. Read the full round-up here 👉: teneo-protocol.ai/blog/agent…

What Teneo shipped in August: - Season 3 closed on 30 August as the first season verified end to end. Connection checks ran the whole 60 days, so fake residential IPs and bot accounts stayed off the board. - The Season 3 draw is being finalised. Nothing to enter and nothing to claim: if your Beacon was online, you are in it. - The Beacon now runs headless. One command in a terminal, pair by QR from the Hub, install it as a service and it starts on boot and reconnects after an outage. - That turns a Raspberry Pi, a home server or an old laptop with a broken screen into an always-on node. Earning is still one slot per internet connection, not per device. - $1,000 USDC is reserved for Beacon runners on Indonesian IPs, share set by uptime. $1,000 USDC goes across all Beacon runners. - We corrected the payout window. Payouts can take up to 7 business days after you confirm your wallet on the winner card, not 72 hours. The old figure was tighter than settlement actually runs. - Four posts on where the Beacon sits in DePIN, why cheap inference made data the constraint, agents leaving the chat window, and agents trading with other agents. Between seasons your Beacon keeps collecting Fragments whenever it is online. Uptime is the one variable you control and the only one that carries across seasons. Boost every 8 hours. Beacon Power builds towards 3.00x. Read the full August recap 👉: teneo-protocol.ai/blog/teneo…

Season 3 Rewards: Here is how the Beacon reward pool splits, and one change to payout timing. $1,000 USDC is reserved for Beacon runners on Indonesian IPs. Eligibility is tied to a genuine connection in Indonesia, and your share is set by uptime, so the more consistently your Beacon runs, the bigger your cut. $1,000 USDC goes across all Beacon runners, wherever you are, Indonesia included. The timing change: payouts can now take up to 7 business days to arrive after you confirm your wallet on the winner card. The old 72 hour figure was tighter than settlement actually runs, so we would rather publish the real window than a fast one we miss. Nothing to enter and nothing to claim. If your Beacon is running, you are already in every pool you qualify for. Get your Beacon running: teneo-protocol.ai/beacon

Beacon Season 3 has ended. Sixty days, and the first season verified end to end. The network sent connection checks to every Beacon throughout the season, which means the accounts at the top were running real nodes on real connections. Fake residential IPs did not make it through this one. The draw is being finalised from everyone who kept a Beacon running. Nothing to enter and nothing to claim right now. If your Beacon was online, you are in it. Winner cards follow once the draw settles. You confirm your payout wallet on the card at that moment rather than in a form filled in months ago, which is why payouts land where they should. Between seasons your Beacon carries on collecting Fragments. Uptime is the part that compounds either way. Keep it running.

Beacon Power doesn't wait for you. Claim and boost every 8 hours and it climbs towards 3.00x. Go quiet and it slides back down the way it came. The bandwidth costs you nothing extra. The Fragments stack on their own. The multiplier is the part you earn. Keep your Beacon running! Download Beacon 👉: teneo-protocol.ai/beacon