Friday on Geeknewz is not another shopping cart. It is a stack of meters, and the useful question is who still gets a copy of the bill. Overnight and this morning we covered Ethereum zkAPI, which tries to unlink prepaid AI credits from a billing identity, next to Microsoft MAI-Transcribe-2-Streaming at an intro $0.54 per audio hour that still lands on a named Foundry or Azure account. Add the AWS Well-Architected Agent, the SEC crypto custody proposal, and ServiceNow Flow in Slack and Teams, and Friday's pattern is clear. Some rails want your name on the receipt. One new rail is built to keep the name off it.
The nameless credit and the named meters
Start with the unlinkable path. The Ethereum Foundation and the Open Anonymity Project put zkAPI on mainnet on October 1, implementing the February 11 "ZK API Usage Credits" design from Davide Crapis and Vitalik Buterin. That is 232 days from research post to a live vault, client, and OA Chat demo. You deposit once, spend with zero-knowledge proofs, and the payment layer is not supposed to learn who you are or what you asked. The model provider still sees prompts. Network metadata still can correlate sessions. So this is prepaid credits without a customer dossier, not Tor for ChatGPT. Primary write-up lives on the Ethereum Foundation blog.
Microsoft's meter goes the other way. MAI-Transcribe-2-Streaming is public preview for live speech-to-text in 60 languages, with first partials just over 100 ms of audio and an intro price of $0.54 per audio hour through year-end. The older batch MAI-Transcribe-2 sits at $0.10 per hour, so the streaming premium is 5.4× ($0.54 ÷ $0.10). You pay that for continuous partials over a WebSocket-style stream, and the usage still ties to whatever Microsoft account runs Foundry, Azure Speech, or the Realtime-compatible path. Microsoft's own launch post is the primary card; our morning piece walks the latency and voice-loop math.
Accounts that already know you
AWS Well-Architected Agent, also preview as of October 1, ranks cloud fixes by goals you declare across cost, security, performance, and resilience. It needs an AWS Support plan, agent profiles in us-east-1, us-east-2, or us-west-2, and IAM roles that can read your configs and metrics. First recommendations can take up to about 24 hours. There is no separate consumption sticker in the launch posts, so the "receipt" is your Support tier plus a service that has already seen your topology. That is the opposite privacy posture from zkAPI, and it is the right posture if you want ranked remediations with SSM runbooks and IaC diffs.
ServiceNow Flow is the chat-desk version of the same idea. It launched October 1 as a standalone AI help desk inside Slack, Teams, email, and a Flow web app, with a claim of going live in a day and no CMDB migration. Employees describe resets and access requests where they already talk. Flow can open ServiceNow incidents with conversation context. Controlled availability is open now; North America GA for current customers is aimed around October 6. Whoever owns the Slack or Teams workspace owns the daily relationship, and every assist still sits inside that workspace identity.
| Oct 2 item | Meter or custody shape | Who sees the receipt? | Geeknewz next move |
|---|---|---|---|
| Ethereum zkAPI | Prepaid private notes + ZK proofs | Provider sees prompts; payment layer should not see who paid | Small Sepolia or mainnet deposit test if billing identity is your leak |
| MAI-Transcribe-2-Streaming | $0.54/audio hr intro (5.4× batch) | Named Microsoft / Foundry / Azure account | Pilot only if mid-utterance partials unlock real actions before year-end pricing ends |
| AWS Well-Architected Agent | Support-plan AI architect (preview) | Your AWS account + Support delivery path | One non-critical account pilot if you already pay for Support |
| ServiceNow Flow | Consumption AI desk in Slack/Teams | Workspace identity + Flow / NOW audit trail | Two-week trial on repeat tickets; measure escalation quality |
| SEC crypto custody proposal | Adviser self-custody when no custodian exists | Adviser/fund with disclosures, reviews, controls | File comments in the 60-day window if you custody client crypto |
The SEC piece closes the Friday ledger. Release IA-7023 / IC-36353 (October 1) would let advisers and regulated funds "self-custody" client crypto only when no permitted custodian is available, with quarterly rechecks, cybersecurity controls, annual reviews, and client disclosures. Chair Paul Atkins and Commissioners Uyeda and Peirce posted statements the same day. This is institutional custody paperwork, not a green light for retail hardware wallets, and the comment clock runs 60 days from the announcement framing we tracked.
If you build agents or research tools where the billing identity is the privacy leak, zkAPI is the Friday experiment worth a small deposit. If you need live captions or voice agents inside Microsoft's stack, the $0.54 streaming meter is a named, measurable pilot, not a privacy play. AWS and ServiceNow both deepen account-bound ops help, so treat them as productivity bets you make under existing Support or chat tenancy. And if you run an RIA or crypto fund, the SEC draft is the receipt that still requires your letterhead. Friday's Geeknewz weather report is simple: most of today's stack still prints a name on the stub. One new Ethereum rail is trying not to.