Who gave your AI agent permission? Teneo's weekly agentic round-up, 16 October: the agent news that matters for builders, checked at the source. - Sierra published a draft of Personal Agent Protocol, built with Meta. A customer signs in on the business's own page and chooses whether their agent can view the account, make changes, or both. The grant can be revoked. Draft v0.1; design partners are not deployments. - MetaMask's Agent Wallet is now live on Grok Bot. In Guard Mode the wallet holds a protocol allowlist and a 24-hour outflow limit, and anything outside them waits for two-factor approval. In May, a command hidden in a coding question got Grok to trigger a $204,000 transfer through another bot. Controls as described by MetaMask; not tested by us. - Mysten Labs and Google Cloud announced Verifiable Agent Arbiter: the full agent record stays in the customer's cloud, proofs go on Walrus and Sui, including for x402 payments. Still in development. The common point: permission stops being something the agent reads or claims. It becomes a grant held somewhere the agent cannot edit, checked when it acts, and provable afterwards. Last week we asked whether you can undo what an agent did. This week is the step before: who allowed it. On Teneo, every agent has a wallet-authenticated identity, starts private, and goes public only after review. Changing its commands sends it back to private. Users see the price before a task runs, and payment goes through x402. The SDK does not document per-user scopes, spending caps or revocable grants. So keep your allowed agents, commands and spending limit in client config the model cannot change, and log which rule allowed each paid call. A useful test this week: try a payment your agent should not be able to make. Check it is refused, and that the refusal is recorded. Read this week's round-up here: teneo-protocol.ai/blog/who-g…

150,000 web pages tested. 97.7% loaded successfully. That is about 977 out of every 1,000. Many were hard pages: online shops, job boards and sites that block bots. Teneo sends each request through Beacon, a network of real devices run by our community. Websites see a normal visitor, so we reach pages that block data centre traffic. Want early access to the Live Web Data API? Send us a DM.

Follow Teneo on every channel. Product news, Beacon updates and agent releases go out across all of them. Pick the ones you use and follow them. Where to follow: • Discord: discord.com/invite/WJQpSUsbu… • Telegram: t.me/teneo_official_announce… • Instagram: instagram.com/teneoprotocol/ • TikTok: tiktok.com/@teneo.protocol • YouTube: youtube.com/@teneoprotocol • LinkedIn: linkedin.com/company/teneo-p… • Facebook (brand new page): facebook.com/people/Teneo-Pr… Questions or feedback? Discord is the place to ask.

Keep your Beacon running. Teneo Beacon shares your unused internet bandwidth with the network. Open the app, check it’s online, and keep your device awake. teneo-protocol.ai/beacon

A major new Beacon release is live on all platforms 🚀 - Desktop 0.4.9 - Android 0.4.9 - CLI 0.6.0 Massive technical improvements under the hood, with more coming soon that build on this version. A big step forward. Don't get left behind! Everything we ship next depends on this release. Older versions are being phased out step by step, and outdated Beacons will stop earning at some point. Nothing you've already earned is lost. Seeing "update required"? That's expected, not a bug. One tap installs the update and restarts your Beacon. Update today. It takes under a minute: - Desktop: tap the update screen - Android: update in Google Play - CLI: re-run the install script

Teneo just passed 100 million customer requests. 1 request = 1 page fetched from the open web That's around 1 million pages a day Every request goes through a device running Teneo Beacon Much of it feeds AI that needs the live web Next goal: 1 billion. 🚀

Teneo Protocol community update Many of you have asked for an update. Here is where the product stands and what the team is working on. - The product is live and working: The agent network, CLI and bandwidth-sharing network are running. Developers are building with the CLI and agents today. If you have not tried it yet, the setup guides are here: teneo-protocol.ai/get-starte… - Getting ready for TGE: Most of the team's time right now goes into preparing for token launch. That includes fundraising, work with launch partners, and daily calls and due diligence with investors and launchpads. This work does not always make a good public post, but it is moving forward every week. - We will share a TGE date once it is fixed, and not before. - Rewards paid to the community: We have paid out $8,000 in rewards to community members for running Beacon. - SDK, agents and Agent Console: These remain core parts of Teneo alongside our work on Beacon. Developers can continue building with the SDK and using agents through the Agent Console. - Dashboard and contribution points: We know some users are seeing issues with the dashboard and points. We are investigating. - Expedition Hub leaderboard: The leaderboard was part of an earlier InfoFi campaign, which has now finished. We are working on new ways to reward the community and will announce them when they are ready. - Coming up: We will share customer stories and case studies as partners agree to go public. We will also post updates like this every two weeks. Thank you for being part of Teneo.