When multi-agent systems go live, what usually blows up first isn’t the strategy—it’s the billing. 1. Three submodules calling each other—who pays, how much, and how do you verify delivery? Even humans get confused keeping track; scale it up, and it collapses faster. Addresses can be faked, APIs can wear fake labels—how do you verify when something’s “done”? 2. That’s why I now prioritize approaches like @GoKiteAI, which bake accounting into the system from the start: How is identity proven? How are limits fixed? How is payment recorded? What looks like API traffic on testnets isn’t like traditional blockchains with a few transactions per day. Passport sessions expiring, failed payments—was it deducted or not? It feels like reading a bank card manual designed for machines. 3. I treat Avalanche mainnet and PayPal pilot runs as background noise. What made me pause was this: for an agent to move from toy to business, it must pass the billing test. Fail that, and no matter how flashy the orchestration, it’s just a demo. Thread → https://t.co/SK2OLlQZ6V #KiteBBW $KITE