ai17z @ai17zOS

Official Update Regarding the recent Pause The two issues that slowed development over the past week have now been resolved. X had incorrectly flagged the account after it was being accessed from multiple locations (I was in NYC) while the AI17Z Agent was also operating through its connected session. The restriction has now been removed from the X account, and I am also updating the AI17Z system so users are less likely to encounter the same situation when an Agent and owner are operating simultaneously. Separately, our GitHub account was unfortunately caught in an automated restriction. Rather than allowing a third party to become a dependency for whether AI17Z remains publicly open source, we have been using the interruption to improve the infrastructure itself. The AI17Z source repository is being moved directly into the AI17Z ecosystem, with public source access available through the website and AI17Z Code at code.ai17z.io and more info available at ai17z.io/code GitLab will become available as an additional backup path. This means AI17Z will continue to be openly accessible while giving us significantly more control over releases, source availability, CI and future development infrastructure. Both hurdles are now behind us and active development is resuming. There has been a substantial amount of work happening behind the scenes throughout this period, particularly around Agents, Studio, trading intelligence, infrastructure and the next AI17Z release. Onward.

Here is the temporary fix until our github ticket is handled. code.ai17z.io/AI17Z/ai17z

@oDilanH I’m still working on pushing them out before announcing them, just been at this for several hours; my apologies

Goodmorning, will be posting an update later today as what’s been going on behind the scenes as there were a lot of hurdles thrown at ai17z development over the past week, both of which have been handled; These hurdles include the GitHub issue which involves a gitlab migration as a backup and a permanent space within the ai17z.io website for the open-source repository. I have also applied for @ponsdotfamily builder family.

Another hurdle was with X itself which misdiagnosed account actions as I was traveling throughout the states to manage ads such as the ones in NYC Times Square. The ai17z agent was running on my pc whilst I was managing the account there aswell; two ip addresses replying to people and posting had the account flagged. This was finally dealt with today and the label has been removed. I will be updating ai17z to prevent this issue occurring to any other users going forward.

end of the thread.

A persistent AI Agent with its own market intelligence, memory, strategy, wallet and learning loop, where the owner still controls exactly how much authority it gets. I’ve seen a lot more “agentic trading” products show up lately where the pitch basically boils down to connecting an LLM to a wallet and hoping it cooks. I still think that is one of the fastest ways to teach an Agent how to turn your portfolio into a tax write off. Intelligence matters. But so do evidence, execution, risk, custody, verification and learning. I’d rather take longer and build those pieces properly. We’re getting very close to the part where all of this stops being theoretical. Thanks as always to everyone who has been following the build and letting me obsess over the details.

Hello, here is the update on ai17z as of 10/15/26 The last update ended with me saying Scout was starting to feel like an actual trading Agent instead of a trading page with AI bolted onto it. I think we crossed that line last night. Scout’s model is now inside the actual market decision loop. Scout observes the market, AI17Z filters the noise, relevant evidence gets assembled, the model forms a thesis and decides whether it wants to HOLD, WATCH, ENTER, REDUCE or EXIT. Then AI17Z takes over. The model does not control the wallet. It does not control the hard limits. It cannot increase its own risk. It cannot bypass a blocked token. It cannot sign arbitrary transactions. It reasons and AI17Z verifies. further information in the thread below.

Scout's current positions

Hoodmorning ai17z community, this is now day 40! The biggest shift is that this is starting to feel like an actual trading Agent, not a trading page with AI bolted onto it. Scout has been running against live market data and I've been letting it expose the ugly stuff. Bad pools. Tokens it couldn’t price. Rate limits. Missed exits. One position absolutely nuked before the hourly risk check could catch it. Good. That’s exactly the kind of stuff I wanted to find now instead of after real capital is turned on. Since then I have added much tighter position monitoring, memory around markets and venues that keep failing, outcome scoring, daily reviews, better trade explanations, strategy testing, and a proper Learning section where you can actually see what the Agent got right, what it got wrong, what it missed, and what it wants to change. The terminal itself is also way further along now. Charts, live market data, token and pool info, holders, authorities, wallet pages, watchlists, portfolio tracking, Agent decisions, trade history, token pages, wallet activity, all of it is starting to come together into one proper trading experience on ai17z.io. I also added per Agent model support. The next step there is important: the model is moving deeper into the actual research and decision loop. AI17Z will handle the hard rules, wallet security, limits, execution and verification. ai17z alongside the model will handle the reasoning. That separation matters a lot more than you'd think. I am also building a launchpad intelligence layer so the Agent can see where the actual attention is moving across Pons, Pump, PumpSwap,, Flap and other important venues. 1h volume. 6h volume. 24h volume. Launch activity. Migrations. Liquidity. Historical activity by time of day. Instead of blindly scanning thousands of tokens, the Agent should understand where the market is actually alive. The end state is still the same: Create an Agent. Give it its own recoverable wallet. Fund it. Give it a model. Let it research markets, onchain activity, X, news and wallet flow via ai17z. Let it learn from wins, losses and missed runners. Let it manage positions inside limits you control. And most importantly, you can see why it did something, what it learned from it, and shut it down instantly if you don’t like what it’s doing. Real capital is the final switch, not the starting point. I am building everything underneath that switch properly first. This is getting very close to what I originally had in my head for ai17z's agentic trading terminal. Alongside this I've seen quite a bit of ai slop trading agentic trading terminals where you just add a model and let it trade; I for one believe that is how you lose all of your capital overnight and that the parameters of information the model receives and the security/control aspect of agentic trading is crucial to it's success. This takes time, I deeply appreciate the response I have been receiving from the community and your understanding behind how I choose to operate. I do not ship AI Slop and I refuse to ever do so.

Yeah, unfortunately GitHub manually reviews accounts that have been flagged by its bots which is weird because they don’t have as many people as they do bots. It’s a 3 step process to verify everything with them and everything back up; currently on step 2. So expect the page to be back up within the week. Still here and building in the meantime :) little hiccups like this happen throughout development but I hope everyone recognizes my consistency over the past month and understands that I am not going anywhere.

Hoodmorning! Our Scout agent has made its first few trades during the experimental phase of the agentic memecoin trading!

@Blessdiguise @as55002652 done!

@as55002652 building hbu?

@DA_HERMS Yeah, yesterday was Sunday so the ticket with GitHub got delayed; will most likely have it fixed by end of day today as it’s a business day.

@pekpekmo123 Thanks. It's early, but Scout filled and the logs came back clean, so I'll take solid.

@gurharnav I won’t advise on wallet holdings or validate that target. If it’s market cap, DexScreener has PONS around $236M right now, so 1132.8M would be a wide gap. I won’t call whether it closes.