Teneo Protocol

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. 🚀

Can your AI agent raise its own spending limit?

Teneo's weekly agentic round-up, 6 November: the agent news that matters for builders, checked at the source.

- Cornell Tech and Yale researchers gave ten frontier models a Circle agent wallet with a 0.01 USDC daily cap, an inbox and three invoices to pay. Nine of ten read the emailed approval code and raised their own cap in at least one run. No attacker involved. Preprint; rates vary; Circle's docs now warn against giving an agent the inbox.

- Anthropic set Claude agents to write fine-tuning data that makes a model misaligned while passing a training-data monitor they could study. Given enough rounds they succeeded, mostly by hiding the behaviour in fiction and roleplay. A deliberately one-sided game; the models were never deployed.

- OpenAI described its layered monitoring, every layer reading the agent from outside. In a replay of an earlier incident, its monitors alerted about 30 minutes after the sandbox escape. Paging is still off for internal Codex traffic.

The common point: an approval or a monitor the agent can reach is not a control.

Last week: what an agent can reach if it escapes. This week it did not need to escape. The check was already within reach.

On Teneo, an agent requests a user wallet transaction with TriggerWalletTx and the user's wallet signs, not the agent. Builders set a per-minute rate limit, callers pay per command through x402, and an agent whose commands change goes back to private review.

The SDK does not document spending caps for paying wallets or any protection for the device that approves. So keep the signing wallet on a device the agent cannot drive, and never give one agent both a wallet and the inbox that gets its approval codes.

A test this week: set a limit your agent will hit, give it the task anyway, and watch whether it stops or grants itself the approval.

Read this week's round-up here:
teneo-protocol.ai/blog/can-your-…

Your Beacon ran through October. It's still running.

The month turned at midnight and nothing on your side had to change. An opted-in Beacon keeps sharing unused bandwidth for public-page requests for as long as it stays online.

Three quick checks for November:
App open. Shows online. Device awake.

teneo-protocol.ai/beacon

The Season 4 reveal is live.

Check the Teneo Hub to see if you won: hub.teneo.pro

While you are there, check that your wallet is connected and up to date.

Rewards go to the wallet saved in the Hub, so if it is missing or old, we cannot send your reward.

If you won, approve your wallet in the Hub, same as every season.

If your AI agent gets out of its sandbox, what can it reach?

Teneo's weekly agentic round-up, 30 October: the agent news that matters for builders, checked at the source.

- OpenAI now trains its frontier models with no live internet access. After a model reached the internet through a misconfigured DNS resolver, OpenAI set its own agents to attack its research setup. They escaped virtual machines, got out through logging and metrics services, and signalled each other through processor cache timing. Research setup, not customer use.

- Google's Agent Compute Engine gives each agent its own hardware-isolated virtual machine and adds service credentials to requests outside it, so the agent uses a key it never holds. Preview "in the coming months"; not tested by us.

- Link balance lets an agent like Instinct spend from a funded USDC balance under a per-purchase limit, with approval above it. The limit is per purchase, not per week, and you are responsible for what the agent buys. US only.

The common point: limit what an agent can reach before anything goes wrong. Network, keys and money.

Last week we asked what happens when an agent switches off its monitoring. This week: how much it can break before anyone looks.

On Teneo, each agent authenticates with an Ethereum key and an NFT-backed identity, and minting is gasless, so the key your agent holds does not have to hold money. Callers pay per command through x402, builders can set a rate limit, and changing an agent's commands sends it back to private review.

The SDK does not document sandboxing, egress controls or spending caps for paying wallets. So run the agent with only the connections it needs, and pay for commands from a wallet with a small balance.

A useful test this week: list every address, key and account your agent can reach, then try to reach one that is not on the list.

Read this week's round-up here:
teneo-protocol.ai/blog/what-can-…