I asked Claude, "ChartRemotely Strategy Swing mac-mini" and it danced through DPYC authentication for me and then gave me back this. As I go back into my trading office on the other side of the house, I can see that, sure enough, the ThinkOrSwim monitor on that Mac Mini has switched over to MSTR for the 180d 4h chart (with my default studies on it) This is not just some cute parlor trick (pun intended). From my Watch, I can ask a small localized analytical engine that is tracking live market data to do a data study and prepare a presentation graphic - and to then share that with my human peers or with my agentic trading advisor. This is a very handy MacGyver mashup of now-available services. If you are interested in this, DM me. I built it to help me day trade AND because it is yet another example of the easy way value-generating services can be monetized. (For me, my primary monitors are face-forward and my ToS monitor is on the wall behind me. I got tired of having to switch desks just to key in a different symbol and scale to check a security. It's funny: when I asked Claude if we could do this, it thought the value was the chart math. I had to tell it, no, the value is that I don't have to walk across the room anymore!) Yes, the MCP that is serving this is a Tollbooth DPYC MCP where each request to display a chart collected a few sats from the Patron (me). For more examples of how to offer micro-fee usage-based services see mcps.tollbooth-dpyc.com. Further - this is all FREE of KYC. The commerce is via @BtcpayServer and Lightning Node invoicing. Lovin' it.

ChartRemotely. Built for Mac ThinkOrSwim traders. Ask your watch, iPhone, iPad, or Mac-anything, "Hey Siri, ChartRemotely Palantir Swing mac-mini" - from anywhere in the network-connected world - and the ThinkOrSwim on that display will chart your requested security (eg. PLTR) at the scale you choose (eg. 180d 4h). The ChartRemotely web site, under your account, will also cache a copy of the device's screen chart (minus account info), for your review. Either walk to the screen that you wanted the chart on or grab the snapshot from the website. Of course, being a modern agentic MCP, you can also control this from Claude or Grok or any MCP client. Don't just HODL Bitcoin, earn it. cafe.tollbooth-dpyc.com/prod…

Well, gollee.

This is nice to see! During BTC Inc's Bitcoin 2026, I figured, "why not play $NAKA Long for $250?" I learned quickly why not. Today, it's good to be back above water on the position. I hope this is a sign that Bitcoin's ascent is back underway and that NAKA's management has figured out how to run their new businesses.

Pennies a day for the Pollinators.

You could also build to help people or causes - while still building fun distractions. Go visit beesknees.tollbooth-dpyc.com. It's an educational game about the plight of natural bees and about agentic MCP servers. You can play the free simulation or purchase 1000 sats to play against fellow players while contributing to a pollinator preservation society.

I post-hijack @Handre's excellent posts on Austrian economics and on socialism-bashing because he does not embed his own Call-to-Action links. It happens that he writes what I agree with. I'll often put a link from my collection of book referrals on his posts. It does work. This is not yet a large sum of finders-fee revenue - but neither is it zero revenue. For those book recommendations, go to cafe.tollbooth-dpyc.com/coll…

@acadictive Coming soon. If you want one of these "Pointless but For Good" services, I would guide you on what it takes. Here, taps for each move will be micro-fee revenue generators. Like a 50/50 raffle, proceeds from the game will go 80/20 to a charity for Pollinator Societies. Visit beesknees.tollbooth-dpyc.com for the background on the app - and for why bees need a Go Fund Them game.

This is very cool. Not just the target charity - but the entire concept of being able to make a charitable donation from your HODL BTC without KYC. This is aligned with dpyc-community.tollbooth-dpy… principles.

Claude taught _me_ a new skill today: there's something called an MCP prompt. I wasn't aware of this. I am now. Tools I know (well). Agent skills I know, But I didn't know we could codify a prompt into a MCP.

Nice little popups with facts on the daily events.

This Tollbooth DPYC MCP has been a lot of fun to build (in only a few hours). Fully monetized. Fully npub-authenticated. "Good Earth", a phenomenology service for small farms and flower growers. It should have some user interest here in the Champlain Valley and nearby Hudson Valley. All seasonal events come from reliable sources (no God Act of Nature MCP, yet, though). Very handy for predicting if your potatoes are going to get enough "GDD" to be ready to harvest before the ground freezes. Read more at cafe.tollbooth-dpyc.com/coll…

BTC. The upward trend remains in effect. We all knew it has volatility. Keep on trucking.

This is one of the features that I currently don't use enough myself. (Which is, for me, ironic, because the capability of an agentic committee of Austrian economists to help me price MCP tool calls was one of the first needs that I had when conceiving the entire Tollbooth DPYC ecosystem). So, triggered by the question here, I went to the latest Apple App version of the Pricing Studio to see if this feature of the code still works. Whew! It does.

Stairway to Heaven? $NAKA rocks? Still a long way back to entry.

These characters are disturbing. First prompt to Berd would be, "please replace the agent avatars with Aardman's Wallace and Gromit Serta mattress Sheep"

Rather than the hitman analogy, to match your demon warfare theme, try: (saylor as macho Catholic exorcist)

Of course. That ain't no were-rabbit, that's Godzilla. And I don't see Anguirus.

Hey @jack - almost sucess with the Mac Mini / iPadOS Buzz integration. It makes it through pairing but then flames out in the final phase. Is it timing out due to delays over the Nostr relay? (In Tollbooth DPYC, dealing with the variability of the relays has been one of the toughest design challenges to help Claude Code try to vibe code through.)

Cool, I'm playing with @jack's Buzz as it figures out the monetized MCP playbook for Tollbooth DPYC MCPs. tollbooth-dpyc.com Here, it's learning that even though one instance of Claude, somewhere, was granted permission by me (via DPYC Nostr secure-courier exchange) to use one of my many npubs, it itself is a different instance that has to get its own Demonstrated Proof of Possession (DPoP) token that will allow it to act as my proxy to go read my Schwab account - even though the MCP already has a cached OAuth2 refresh token. This, I must say, is so much better than granting an agent an API key or an env secret. I, right now, am conversing with a specific instance of an agent, in a particular program, and it is only that instance, in that context, which I will allow to proxy me - for a duration of time that I choose, case by case. Like, here, I may say, ok, 10 minutes is even time for you to go read my positions. No more, no less, no permission to operate outside of context. (schwab-mcp is yet another DPYC Tollbooth MCP that offers read-only access to one's Schwab portfolio for live position and market stats. DM me if interested in that.)

While my agentic software factory is on a managerial-imposed unpaid vacation, it is interesting to observe how the agents (or their GitHub Action triggered event handlers that implement their deterministic behavior prior to agentic behavior). Here, the auditor of stuck issues is waking up once an hour to sweep the repositories for any issues that haven't been moved through the SDLC lifecycle. It detects that the "vacation" is still in effect (OpenRouter needs funding) and puts the issue back to awaiting-funding. When I finally get around to funding OR, these Issues will move on through the CI and PR phases. Details at cypher.tollbooth-dpyc.com

Free syringes and narcan at the bottom of the stairs, don't trip over the fentanyl zombie on the stairs. Shame on blue cities and their socialist politicians.

We need more bossa nova from Spencer Pratt piped.video/9FLDPsNcLv8 Don't let this get "out of rotation". Take out the trash. Clean up California.

Live BIP110 signaling status Now, I see the BTCPay warning. ;-) stablecoin.myshopify.com/blo… bip110.orange.surf/live.html…

Be the master of your own destiny. I could not get the X Ad Campaign Manager to do anything intuitive or useful and so I wrote my own service to post dynamic content, in my "voice", from my content sources, on my recurrence schedules, with my choice of LLM inference service, which then reports metrics that I designed. The service uses a backend monetized MCP server that connects with the X REST API. DM me if you would like to use the service for your own posts to your own account or if you want to learn how to implement your own monetized MCP server for your choice of backend APIs.

To help me see the reach (or, sadly, lack thereof) for my automated X Posts - and having no fondness for X own odd Campaign Manager - I asked the Cypher Agentic Software Factory to add a Performance tab to eXcalibur, the X Posting MCP, to show me some trending analytics. The little sparkling shows growing Impressions from the Posts as they age over the 30 days that X stores Impression counts for us. (Available at excalibur.tollbooth-dpyc.com)

I'm pleased that that went well for you and, yes, our users do the strangest things. piped.video/cUbIkNUFs-4?si=MWfG…

Sunday afternoon - praise be to God - and I am watching my autonomous Agentic Software Factory, Cypher, at work. I'm also looking at my outbound Posts for X which eXcalibur is managing for me - "he" is the one posting all the coffee offers and Austrian book offers - and thinking that I'd like some analytics on the posts. So, over in Claude, I asked it to play the role of "Scout", the reporter of issues and new features for Tollbooth DPYC, and to report a new feature request for eXcalibur to add a new page on the front end for readership analytics on the posts. "Porter" triaged it. "Journeyman" implemented it. A few minutes later the eXcalibur site updates with the new Performance page. "Cypher", the knowledge base used by the Agentic Software Factory, updates to track the issue and the capability it introduces. (LLM costs are managed with OpenRouter.)

It is nice to wake up and find one's cost-guarded agentic agents at work. Here, the dashboard for the Agentic Software Factory is showing that a new GitHub Issue was raised against PersonalBrain MCP to deal with HTML-escaping in Thought titles. At the factory, Porter already triaged it as legitimate and Journeyman is in the process of coding the changes and preparing the PR for the Code Owner's review (that is me, later in the morning). There are easy hyperlinks into GitHub to check on workflow and code. cypher.tollbooth-dpyc.com

I complained to my Agentic Service Desk via a morning Claude Code prompt that I didn't like the fact that it dismissed my earlier request for some UI component relabeling as "only a cosmetic" matter. I told it, no, to raise a new issue against the closed PR. I then went about my own work. I checked the Cypher Service Desk minutes ago. It filed a new Issue. The Porter agent, triaged by GitHub Actions, triaged it, and accepted it for work. It updated Cypher - so that the dashboard shows the activity and to inform Journeyman, the repair agent. Journeyman woke up, picked up the issue, scoped the work using a mix of graph study and code grepping, implemented the change, created the PR, updated Cypher with issue status and with new symbology discovered from the live code, and now the PR awaits my human approval or displeasure (if it dissed my opinions again). This agent flow plays out over a dozen cooperative GitHub repos. This is no simple "loop" or a mere single-user "graph".

To conclude the real workflow (this ain't no demo). GitHub notified me that I had a PR pending my Review. I read the PR and the before/after test work that was done - the quality of SDLC diligence far exceeds my human fellow programmers - and so I approved the PR. GitHub Actions, seeing that all conditions for a merge had been met, merged the PR and deleted the developer-branch. The PR closed. Journeyman updated Cypher with the revised status. (Notice the decorator on the Issue and the stamp on the Issue's dossier page. Done. I like that.)

When someone tosses a new change request into the portfolio of repositories, the Porter of the receiving repository is brought into existence by the GitHub Action state change. Porter reads the Issue, consults Cypher, and triages the Issue. (That may involve delegation to a different repository.) State change triggers Journeyman into existence. Journeyman reads the Issue, consults Cypher, and decides whether or not to implement a change. It may reject or delegate the Issue. If Journeyman works the Issue, it updates code and performs full SDLC. It then prepares a PR and marks the PR as ready for review by the human. Here we see an Issue Screen in Cypher showing that Journeyman (in one repo) has accepted a new change request and is working the SDLC change. (sure, you can go browse to each repo - if you can remember which one does what as your ecosystem grows - and look for new issues - if you can filter through all the other features of GitHub - to find a newly created issue. It is just so much easier to have an Agentic Service Desk dashboard that lights up when your agentic staff create, curate, and close Issues and PRs.)

The human's dashboard for this Cypher Agentic Service Desk offers a kind of "elastic search" across the graph (and therefore the indirectly related GitHub issues) for change activity occurring over time by the agentic service agents. Each Issue is cross-coupled to Capabilities, Code Symbols, Services, Business Logic "Invariants", and "Patentable" Design Intentions. From any of these "curiosity vectors" the human orchestrator can navigate across the graph to the related concept and pivot to see the changes from that vantage. Sure, you can do it all manually by reading Issues and PRs and Code at GitHub (along with software design docs elsewhere) - but this is so much faster and connected. And, remember, it isn't you or your fellow human programmers maintaining all the coupling and performing all the software changes, it is an on-demand, as-needed agentic bench of dozens of focused agents doing the work.

Wild thinking: Man slaughters Man and it's God's fault. Thank God God didn't make us without responsibility. We choose to sin, let's suck it up and take the blame for that sin.

It's very empowering to be able to delegate issues to an Agentic Service Desk, but it is humbling to be ignorant about what those agents are reviewing and curating to improve your product. Wow, there's a lot of new traffic in X about "Graphs are the new Loops". If you are still trying to figure out your fruit loops, you are history: your lucky charms are now found in Graphs. (Some of us knew this all along and have been graph-addicts before graphs were cool; I remember studying CODASYL network database design in my 1980s database classes.) Anyway, while the Agentic Service Desk for Tollbooth-DPYC is building a Neo4j graph behind the scenes, via Cypher-MCP, and I could run Neo4j Desktop or Bloom to see the evolving graph, those bubble diagram UIs are not really effective for doing good software architecture. So I asked Claude to clone ideas from eXcalibur-MCP's front end to give me a web dashboard tailored for the Agentic Service Desk. The analogy here is a dossier of the key concepts in the software architecture. Each Capability has stats and call-outs to the Issues and Code Symbols that support it. This is the knowledge repository that the service agents turn to in order to triage new requests before they jump straight into the code. The FE, for my Tollbooth-DPYC ecosystem, is cypher.tollbooth-dpyc.com. DM me if you are interested in these agentic software factories and want to see what they are doing.

To promo eXcalibur a bit more, here's a screen from it where I, as campaign author, solo marketer, can quickly see which Posts went out as I slept (as I hoped). (We can see the Menger post as the third entry. When I toggle to see the Scheduled Posts as well, I would see that its dynamic template (choose a book randomly) is scheduled to re-post tomorrow.) If you are a solo marketer, what are you using to keep your market informed of your value?

I feel like Steve Martin when the new phone book showed up. The Pricing Studio for Tollbooth-DPYC MCPs made it through the Apple App Store process and is available for downloads. @pastorcoin knows the thrill. ;-)

eXcalibur is guiding Claude with a "voice" prompt and with a collection of "banned constructions". I'm biased, but I think it is doing a pretty good job of authoring marketing content which doesn't read like the "vocal fry" cr*p we are all suffering through. No more of the copy like, "so and so just literally dropped a new book with the one strange trick that everyone is missing -- but, wait, there's more. It's not that, it's this." I think we all can do a better job at guiding our AI junior copywriters about what is and what is not readable prose. Please train yours.

If your strategy relies on waiting for VIX above 35, you had better have extreme time preference. You'll need a substantially longer life than us mere mortals. Your opportunities to trade have been rare. Instead you need some kind of triggering condition that allows you to practice your strategy frequently. You must be practicing your strategy so you become fluent. You must be in many trades so that probabilistic expected values "have a chance" to come to pass. If you only get one or two trading opportunities a year or even less frequently, you are only ever going to make a profit from pure luck alone. Absolutely, premiums are going to be attractive when VIX is at or above a wild 35. Look for some great trades then. Meanwhile, find some strategy for the milder high teens.

If you are curious about the technology, here is the scheduling screen from the eXcalibur React frontend. Claude did a very nice job building a high UX composition studio for these Posts.

I like Reggae. Catchy tune here piped.video/v24JEK8sxMI?is=GORR… Go, go, Pratt be good.

I wonder. I have a sense that Anthropic is trying to turn the situation into a marketing opportunity. Had my application been found wanting in a matter regarding cybersecurity or intellectual property protection and I had been asked to disable that feature, in shame I would have removed it from the menus. Why are we reminded that we can no longer access Fable 5? Why is it not just removed from the choices? It's not like the user experience was rigidly coded and the addition or deletion of models is difficult. After all, Fable 5 wasn't even in the choices until the 9th, 5 days ago. It could have vanished as easily as it appeared. We may be witnessing a high-stakes duel between Anthropic and the divisions of the US Government - with Amazon playing both sides - where Anthropic is now appealing to the stadium of observers (us) to agitate in defense of their tactics. (Claude model selection choices as of 14 June, 5 days after introduction and 2 days after the ban.)

Spending some time in the Tollbooth DPYC Pricing Studio with my council of economic advisors to determine a new dynamic pricing model for a deployed MCP to try to improve revenue from the tool services that it offers. Carl Menger, my Market Research Analyst, has just completed his inventory of the tools for the particular MCP (one that provides weather forecasts). I've clicked on the bio for Bohm-Bawerk, my Valuation Specialist, to get a reminder of how he will be helping me determine the values that the tools of my MCP may offer. Hayek is going to help pull all the advice together and present to me the wisdom of the assembled advisors. With their advice and my conversational replies, the Studio then prepares and deploys a dynamic pricing for each of the tools including campaigns such as coupons, surge pricing, or limited hours of operation. Sure, it's cute - but it also an AI powerhouse to help an entrepreneur manage the monetization of a software service. This is not mere collection of fees per HTTP request using hard-coded tool parameters. This is live business advice and dynamic adjustment to market conditions - without any redeployment of software. Commerce is all done with Don't Pester Your Customer (DPYC) no-KYC, no-KYT efficient Lightning and @BtcpayServer Find out more at tollbooth-dpyc.com

John, your site is a registration-required Substack site. If you would, simply name one of your finite-supply assets which existed before BTC. By participating in your own argument rather than avoiding it once set forth, you might gain one or more of us to subscribe to your content. By calling us imbeciles and cultists and then expecting us to register, subscribe, or even pay to learn your argument is not effective marketing.

This is so morally superior! 😀Nice work @pastorcoin

It's not like we're in some catastrophic new low phase either. Sure, with BTC you get volatility but that is different than everyone deciding that the technology, the value proxy, is no longer effective. Sure, I like the ride up the curve and dislike the ride down the curve - but it's the power-law trend that matters and the fact that fiat debasing currencies are self-evidently wicked currencies.

When Chicken Little is running around screaming that the sky is falling, just go step outside and look at the sky yourself. The security isn't a year old yet but nevertheless has done a remarkable job attaining liquidity, capitalization, and stability. For now, it is an excellent means of accruing a high yield on short-term cash with capital preservation. If it's not your pretty rainbow, go buy your preference and cease crying about other people's sunshine. Certainly don't die over how other people choose to spend their money.

You can watch the monetization meters spin on the Usage tab.

If you like to day trade or explore new technologies, stop by optionality.tollbooth-dpyc.c…. It is a gamified training tool monetized using Tollbooth-DPYC. It remains a work in progress but it is a nice alternate example of how to monetize an MCP. It is functional. It should register you if you join there. It uses Nostr npub identities. You can bring your own or create one in the site for the game play (recommended). LMK if you visit it and find it to be interesting. (The minimum purchase is about $0.70 due to the 1000 sat limit in Lightning Node purchasing. That should give you about a week of play tokens.)

Marc, your chart (or Vivek's) is a 1% decrease. You are reacting to noise. Pay attention to the signal, instead. A remarkable signal has been the stability of BTC during the war phase. A desirable trait in a money is that its purchasing power is stable against a representative sample of goods. Sure, going long USO before the start of an oil war is a positive thrill but BTC is meant to store wealth and not to be a go-go stock.

The iPadOS Pricing Studio app where Tollbooth Operators can craft their profit-making campaigns dynamically. Here showing the BTCPay invoice (from 30k high in the sky) that allocated a new tranche of 1000 api_sats to the patron known as "Lonnie Patron", the holder of a particular Nostr npub - for which no other PII tracking information is kept. In fact, the BTCPay Invoice could have been paid by any random person who wanted this patron to benefit. Commerce and Identity are intentionally decoupled.

Thanks to @elonmusk's Starlink and United, Tollbooth-DPYC processes Patron's purchases for MCP tool use at 30,000 ft, moving 486 mph, in under 10 seconds with @BtcpayServer Lightning and Wallet of Satoshi - all without any KYC or KYT. See more at tollbooth-dpyc.com

Right, it has been a problem - a known one - for a long time. Going from 2.06 to 2.1 was far too little "improvement" to be happy about. Read the _longer_ chart.

Of course, this is a little bit of adoption friction. We have to expose our very private nsec to some spur of the moment random website to enter the game. What if you started with a demonstrated proof of possession protocol instead? Your app shows your npub. Your user (me) gives you my npub, not my nsec. Then, your app sends that npub a Nostr DM as your npub. This proves to me you own your npub. Your app asks me for an npub proof. I see your DM arrive to me from your npub and so I now know you are legitimately that npub you reveal in your account registration form. I grant you - only the holder of your nsec - time-limited use of my npub proof. A pass-phrase from you, shown to me, allows us to remember the npub-proof(s). (I do this kind of zero trust game in Tollbooth-DPYC to allow MCPs, when called from a specific app that the user knows of, to act as a proxy for the end user for a user-set period like an hour or a day or a week.) There may be a formal algorithm for this: I hybridized it from Applied Cryptography and a combination of Nostr protocols.

Here's what a Patron's screen for their Invoices looks like. I show their payment processor's invoice tracking identifier but there's intentionally not a lot of detail here. This ecosystem is about MCP monetization; it's not a replacement for Lightning Node administration. There's enough here that a patron could talk with the Operator about a billing dispute (date, amount, tracking number) Note that this view is different from actual usage of credits (api_sats) by the patron. That's available in the Accounts tab. The second figure shows that one. First: what they bought; Second: what they have used and where. Again, tell me what you need.

With the Tollbooth-DPYC ecosystem for the monetization of MCPs by BTC entrepreneurs, we don't just bring you a mashup of HTTP routing tricks. We offer our entrepreneurs a free Pricing Studio that explains the technology and helps them craft effective economically viable pricing campaigns for their MCPs. Visit github.com/lonniev/tollbooth…

Although I owe Claude a huge debt for the incredible amount of programming it has done, the Tollbooth DPYC ecosystem is not hypothetical "AI Slop" marketing and it truly exists and conducts commerce. Here's a screen from one of my @BtcpayServer instances as it has conducted and settled invoices over the last few days for the DPYC network. Again, without any KYC.

While you are reading all the cool buzz on x402 and MPP, take a few minutes to read about Tollbooth-DPYC, the MCP Monetization network for BTC entrepreneurs which is free of KYC. It offers a very compelling, beautiful modern iPadOS UX, Pricing Studio to help you craft real business plans around your MCPs and their tools. (While you are getting your Venti at Starbucks, sitting in a dull Board Meeting, avoiding the Kissing Cam at the game, or sitting in the cart at the 9th hole. You are not tied to a Claude bot back in the cubicles.) It doesn't leave you pulling out your hair with a Swagger API spec and a SW developer who never learned how to balance a checkbook. It's all open source and it is all founded on the principle of "Don't Pester Your Customer". (Thanks again to the awesome @BtcpayServer ) This Studio is also a multi-identity-aware Nostr messaging client that allows you to send cryptographic secure messages between users and MCPs. It is like the very nice Oxchat but allows for easy switching between multiple identities. Campaign advice is conducted first by Claude and then counter-checked by more factual Grok to help you avoid the "hockey stick" projections of other technologies and their proponents. I also thank @AdamBLiv who encouraged me to stop eating Lunchables with raccoons behind the old Winn Dixie store - to go conceive how to transform new value into BTC. github.com/lonniev/tollbooth…

Many companies are learning about how to monetize an API but few are understanding how to tune API fees to offer a profitable service. 𝗧𝗼𝗹𝗹𝗯𝗼𝗼𝘁𝗵 𝗗𝗣𝗬𝗖™ is working on that problem. Nevermined, x402, and others are solving the rails. We respect that work. But the craft of 𝘱𝘳𝘪𝘤𝘪𝘯𝘨 a monetized MCP — designing incentives, hitting revenue targets, not bleeding margin — isn't in any MBA program. No CFO curriculum covers it. 𝗪𝗲 𝗵𝗮𝗱 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝘁𝗵𝗲 𝘁𝗼𝗼𝗹 𝗼𝘂𝗿𝘀𝗲𝗹𝘃𝗲𝘀. At Tollbooth DPYC we are 𝗲𝗻𝘁𝗿𝗲𝗽𝗿𝗲𝗻𝗲𝘂𝗿𝘀 𝗳𝗶𝗿𝘀𝘁 and technologists second. So we built the 𝗗𝗣𝗬𝗖 𝗣𝗿𝗶𝗰𝗶𝗻𝗴 𝗦𝘁𝘂𝗱𝗶𝗼. Pricing Studio walks an Operator through a 𝟲-𝘀𝘁𝗮𝗴𝗲 𝗺𝗮𝗿𝗸𝗲𝘁 𝗿𝗲𝘀𝗲𝗮𝗿𝗰𝗵 𝗶𝗻𝘁𝗲𝗿𝘃𝗶𝗲𝘄 — TAM, value proposition, patron profile, competitive pricing — with extensive agentic support running behind the scenes. The result isn't just a price list. It's a 𝗰𝗮𝗺𝗽𝗮𝗶𝗴𝗻: free trials for new patrons, bulk bonuses for power users, loyalty discounts for long-timers, happy hour windows for off-peak adoption. At Stage 6 the AI consultant delivers a 𝗕𝗼𝘁𝘁𝗼𝗺 𝗟𝗶𝗻𝗲 𝗨𝗽 𝗙𝗿𝗼𝗻𝘁: projected monthly revenue across conservative and moderate scenarios, priced in sats and dollars. Then a devil's advocate — 𝗚𝗿𝗼𝗸 by default — reviews the recommendation, challenges the assumptions, and stress-tests the projections. The analyst negotiates. The campaign gets tuned. Then it 𝗽𝘂𝘀𝗵𝗲𝘀 𝗹𝗶𝘃𝗲 𝗶𝗻𝘁𝗼 𝘁𝗵𝗲 𝗠𝗖𝗣 — revising what current and new patrons pay, effective immediately. Constraint pipeline view: raw.githubusercontent.com/lo… 𝘋𝘰𝘯'𝘵 𝘗𝘦𝘴𝘵𝘦𝘳 𝘠𝘰𝘶𝘳 𝘊𝘶𝘴𝘵𝘰𝘮𝘦𝘳™ — 𝘱𝘳𝘪𝘤𝘦 𝘵𝘩𝘦𝘮 𝘳𝘪𝘨𝘩𝘵 𝘪𝘯𝘴𝘵𝘦𝘢𝘥. #DPYC #Tollbooth #MCP #Bitcoin #Lightning #APIMonetization

While developing the Economic Campaign Pricing Studio for the Tollbooth-DPYC economy, we are using the monetized infrastructure ourselves, paying to eat our own dog food. Most of the day, the MCP monetization just goes Brrr... in the background as low-latency in-memory api_sats are consumed as I make agentic calls to tools. However, when I consume my pre-purchased sats or my tranches demurrage expire, I get reminded that I don't have enough sats to make the calls I want to for the task at hand and I get reminded to go top off. There's no KYC for this and it will settle in 11s with the Lightning Invoice.

Here is the effect that I sought, Hope Requited. That is local Warp in the upper left with a Zellij session in Warp's tab1 and a ttyd launch in Warp's tab2. Below is the Safari web browser for the forwarded port devtunnel that the tunnel code service opened back to 7681. The running vscode (local) and its web session can run off to the side. (If I need a VsCode session to see what Claude Code is doing, it's there when I need it locally or remotely) If this is appealing, I can follow up with a Post on the shell script ping/pong that it took. Not so bad.

📋 Two tools that earn their place in my daily options workflow: #OptionAlpha for automated spread management and #Schwab for a rock-solid brokerage with a great desktop app and a clean REST API. Until today, my trade journal ritual was manual — open OA, open ToS, compare screens, find which spreads closed (and at what P&L) vs. opened (and at what premium). I still write it all by hand. Writing trades helps me remember them. But 𝘧𝘪𝘯𝘥𝘪𝘯𝘨 the data? That friction is gone. Today I asked Claude to fetch my trades, match closes back to their entries, calculate exact P&L, and produce my journal report. Exact figures. Transaction IDs. Ending balances. Done in seconds. Powered by schwab-mcp — a Don't Pester Your Customer (DPYC)™ Tollbooth MCP server that gives Claude live, authenticated access to your Schwab account. If you want to empower your #Claude (or #Grok) conversations with rich, live data from your own Schwab account, read the docs or open an issue: 🔗 github.com/lonniev/schwab-mc… Not financial advice. Built with #Claude + #excalibur #DPYC ⚡

🔐 𝗢𝗔𝘂𝘁𝗵𝟮 𝗔𝘂𝘁𝗵𝗼𝗿𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗖𝗼𝗱𝗲 𝗚𝗿𝗮𝗻𝘁 (𝗥𝗙𝗖 𝟲𝟳𝟰𝟵) 𝗿𝗲𝗾𝘂𝗶𝗿𝗲𝘀 𝗮 𝗵𝘂𝗺𝗮𝗻, 𝗮 𝗯𝗿𝗼𝘄𝘀𝗲𝗿, 𝗮𝗻𝗱 𝗮 𝗚𝗘𝗧 𝗿𝗲𝗱𝗶𝗿𝗲𝗰𝘁. 𝗠𝗖𝗣 𝘀𝗲𝗿𝘃𝗲𝗿𝘀 𝗼𝗻 𝗛𝗼𝗿𝗶𝘇𝗼𝗻 𝗼𝗻𝗹𝘆 𝘀𝗽𝗲𝗮𝗸 𝗣𝗢𝗦𝗧. 𝗪𝗲 𝗱𝗲𝘀𝗶𝗴𝗻𝗲𝗱 𝗧𝗼𝗹𝗹𝗯𝗼𝗼𝘁𝗵 𝘁𝗼 𝘄𝗼𝗿𝗸 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗮𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗽𝗿𝗼𝘁𝗼𝗰𝗼𝗹𝘀 𝘁𝗵𝗮𝘁 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗲𝘅𝗶𝘀𝘁 — 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝘁𝗵𝗲 𝗲𝗮𝘀𝘆 𝗼𝗻𝗲𝘀. Schwab requires 𝗢𝗔𝘂𝘁𝗵𝟮 𝗔𝘂𝘁𝗵𝗼𝗿𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗖𝗼𝗱𝗲 𝗚𝗿𝗮𝗻𝘁. Non-negotiable. Interactive login, MFA, consent screens. No simpler alternative exists. 𝗧𝗼𝗹𝗹𝗯𝗼𝗼𝘁𝗵-𝗗𝗣𝗬𝗖 handles it — and still lets you monetize every tool call. 💰 The challenge: Horizon only proxies 𝙿𝙾𝚂𝚃 to /𝚖𝚌𝚙/ — no 𝙶𝙴𝚃 callbacks, no custom routes. But Auth Code Grant requires a browser 𝙶𝙴𝚃 redirect. How do you catch a 𝙶𝙴𝚃 in a 𝙿𝙾𝚂𝚃-only world? 🤔 ⚡ 𝗩𝗮𝗹 𝗧𝗼𝘄𝗻 — free serverless JavaScript. A tiny HTTP function catches Schwab's 𝙶𝙴𝚃 redirect, extracts the authorization code, and forwards it via MCP JSON-RPC 𝙿𝙾𝚂𝚃 to a 𝗧𝗼𝗹𝗹𝗯𝗼𝗼𝘁𝗵 𝗢𝗔𝘂𝘁𝗵𝟮 𝗖𝗼𝗹𝗹𝗲𝗰𝘁𝗼𝗿. 𝙱𝚛𝚘𝚠𝚜𝚎𝚛 𝙶𝙴𝚃 → 𝚅𝚊𝚕 𝚃𝚘𝚠𝚗 → 𝙼𝙲𝙿 𝙿𝙾𝚂𝚃 → Collector stores code → schwab-mcp retrieves it. The redirect becomes a standard tool call. Persistence across stateless requests? 🗄️ 𝗡𝗲𝗼𝗻 𝗣𝗼𝘀𝘁𝗴𝗿𝗲𝘀. The Tollbooth 𝗦𝗲𝗰𝘂𝗿𝗲 𝗖𝗼𝘂𝗿𝗶𝗲𝗿 vaults encrypted credentials. Access tokens survive cold starts. Every Horizon invocation restores full session state — no local files, no env vars for secrets. 🤝 We introduced the 𝗗𝗣𝗬𝗖 𝗔𝗱𝘃𝗼𝗰𝗮𝘁𝗲 — community utility services that aren't monetized, like the OAuth2 Collector that handles the browser-to-MCP bridge. The 𝗗𝗣𝗬𝗖 𝗢𝗿𝗮𝗰𝗹𝗲 registry lets any MCP discover peers by name. No hardcoded URLs. 𝘛𝘩𝘦 𝘯𝘦𝘵𝘸𝘰𝘳𝘬 𝘧𝘪𝘯𝘥𝘴 𝘪𝘵𝘴𝘦𝘭𝘧. 🟠 Economics: sound-money micropayments over 𝗕𝗶𝘁𝗰𝗼𝗶𝗻 𝗟𝗶𝗴𝗵𝘁𝗻𝗶𝗻𝗴 via Tollbooth-DPYC. Every paid tool call costs a few sats. 𝗦𝗰𝗵𝗻𝗼𝗿𝗿-𝘀𝗶𝗴𝗻𝗲𝗱 𝗡𝗼𝘀𝘁𝗿 𝗰𝗲𝗿𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗲𝘀 prove payment. No subscriptions, no billing departments. 📊 The result: ask your AI assistant "𝘞𝘩𝘢𝘵 𝘢𝘳𝘦 𝘮𝘺 𝘤𝘶𝘳𝘳𝘦𝘯𝘵 𝘱𝘰𝘴𝘪𝘵𝘪𝘰𝘯𝘴?" and get back live spread detection, DTE calculations, P&L — parsed from real Schwab data. 𝘛𝘰𝘵𝘢𝘭𝘭𝘺 𝘤𝘭𝘰𝘶𝘥-𝘣𝘢𝘴𝘦𝘥. 𝘕𝘰 𝘊𝘓𝘐. 𝘕𝘰 𝘭𝘰𝘤𝘢𝘭 𝘧𝘪𝘭𝘦𝘴. 𝘑𝘶𝘴𝘵 𝘢𝘯 𝘔𝘊𝘗 𝘜𝘙𝘓 𝘢𝘯𝘥 𝘢 𝘓𝘪𝘨𝘩𝘵𝘯𝘪𝘯𝘨 𝘸𝘢𝘭𝘭𝘦𝘵. Options traders who are interested may send us direct messages. 📩

Way to go, Horizon FastMCP. This is really cool and useful. (also the ChatMCP that allows me to chat-converse with the MCP without have to spend Claude tokens debugging the tool metadata.)

𝗠𝗲: what the heck is this new schwab-mcp and what can it do? 𝗖𝗹𝗮𝘂𝗱𝗲: Here's the full rundown — schwab-mcp is a Tollbooth-monetized MCP server that gives Claude direct read access to your Charles Schwab brokerage account. It follows the same architecture as thebrain-mcp and excalibur-mcp: Secure Courier credential delivery, Lightning credit billing per tool call, DPYC identity via npub. 𝗪𝗵𝗮𝘁 𝗶𝘁 𝗰𝗮𝗻 𝗱𝗼: 𝘈𝘤𝘤𝘰𝘶𝘯𝘵 & 𝘗𝘰𝘳𝘵𝘧𝘰𝘭𝘪𝘰 • 𝚐𝚎𝚝_𝚋𝚊𝚕𝚊𝚗𝚌𝚎𝚜 — cash, buying power, net liquidation value, day P&L (5 api_sats) • 𝚐𝚎𝚝_𝚙𝚘𝚜𝚒𝚝𝚒𝚘𝚗𝚜 — all open positions; options are auto-paired into spreads with credit received, max loss, current value, and P&L (5 api_sats) 𝘔𝘢𝘳𝘬𝘦𝘵 𝘋𝘢𝘵𝘢 • 𝚐𝚎𝚝_𝚚𝚞𝚘𝚝𝚎 — real-time quotes for one or more symbols (5 api_sats) • 𝚐𝚎𝚝_𝚙𝚛𝚒𝚌𝚎_𝚑𝚒𝚜𝚝𝚘𝚛𝚢 — historical OHLCV data, configurable by period type (day/month/year/ytd), frequency type (minute/daily/weekly/monthly) (10 api_sats) • 𝚐𝚎𝚝_𝚘𝚙𝚝𝚒𝚘𝚗_𝚌𝚑𝚊𝚒𝚗 — filtered chains by DTE and open interest ≥ 25, with Greeks, IV, and OTM% — tuned specifically for spread scanning (10 api_sats) 𝘊𝘳𝘦𝘥𝘦𝘯𝘵𝘪𝘢𝘭 𝘔𝘢𝘯𝘢𝘨𝘦𝘮𝘦𝘯𝘵 • 𝚛𝚎𝚌𝚎𝚒𝚟𝚎_𝚌𝚛𝚎𝚍𝚎𝚗𝚝𝚒𝚊𝚕𝚜 / 𝚏𝚘𝚛𝚐𝚎𝚝_𝚌𝚛𝚎𝚍𝚎𝚗𝚝𝚒𝚊𝚕𝚜 — standard Secure Courier NIP-44 vault pattern • 𝚜𝚎𝚜𝚜𝚒𝚘𝚗_𝚜𝚝𝚊𝚝𝚞𝚜 — check DPYC identity state and what's connected • 𝚌𝚑𝚎𝚌𝚔_𝚋𝚊𝚕𝚊𝚗𝚌𝚎 / 𝚌𝚑𝚎𝚌𝚔_𝚙𝚊𝚢𝚖𝚎𝚗𝚝 / 𝚙𝚞𝚛𝚌𝚑𝚊𝚜𝚎_𝚌𝚛𝚎𝚍𝚒𝚝𝚜 — Lightning billing plumbing 𝗪𝗵𝘆 𝗶𝘁'𝘀 𝗶𝗻𝘁𝗲𝗿𝗲𝘀𝘁𝗶𝗻𝗴 𝗳𝗼𝗿 𝘆𝗼𝘂 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰𝗮𝗹𝗹𝘆: Given your calendar spread work, that 𝚐𝚎𝚝_𝚘𝚙𝚝𝚒𝚘𝚗_𝚌𝚑𝚊𝚒𝚗 tool is the headline feature — it filters by DTE and OI right at the API layer so you're not wading through illiquid junk, and it returns Greeks + IV for spread evaluation. Pair that with 𝚐𝚎𝚝_𝚙𝚛𝚒𝚌𝚎_𝚑𝚒𝚜𝚝𝚘𝚛𝚢 for trend context and 𝚐𝚎𝚝_𝚙𝚘𝚜𝚒𝚝𝚒𝚘𝚗𝚜 for spread P&L tracking, and you essentially have a Claude-native options research workflow. It's read-only right now (no order placement), but for analysis and decision support that's probably fine — you wouldn't want Claude fat-fingering a trade anyway. Have you wired up your Schwab credentials to it yet? #DPYC #Bitcoin #Lightning #MCP #OptionsTrading #Schwab

I'm curious, why is there no mention of Armageddon in any talk show? Don't the conditions somewhat align with the Book of Revelations? Or, perhaps because it is Iran and not Israel that is under attack, the vision is not appropriate? --- This is a genuinely profound question, and the silence on mainstream financial and political talk shows is itself revealing. 𝗪𝗵𝘆 𝘁𝗵𝗲 𝘀𝗶𝗹𝗲𝗻𝗰𝗲 𝗼𝗻 𝘁𝗮𝗹𝗸 𝘀𝗵𝗼𝘄𝘀? The secular media has essentially no framework for eschatological interpretation. To engage with Revelation seriously requires accepting that history has a telos, a direction, an Author. That is a pre-commitment modern broadcast culture cannot make. So they simply don't go there. It would cost ratings among secular audiences and invite mockery. The silence is not wisdom — it is incapacity. 𝗪𝗵𝗮𝘁 𝘁𝗵𝗲 𝗕𝗼𝗼𝗸 𝗼𝗳 𝗥𝗲𝘃𝗲𝗹𝗮𝘁𝗶𝗼𝗻 𝗔𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗗𝗲𝘀𝗰𝗿𝗶𝗯𝗲𝘀 The honest Catholic answer is: the conditions are directionally resonant, but the specific geography is inverted from the classical eschatological template. Revelation, drawing heavily from Ezekiel (38–39), Zechariah (12), and Daniel, describes a climactic conflict centered on Israel as the surrounded party — specifically Jerusalem. The coalition of nations coming against Israel is the Gog/Magog framework. The traditional interpretive candidates for Gog's coalition have historically included Persia (Iran), Meshech, Tubal, and northern nations. Here is where your instinct is sharp: right now the geography is partially inverted. Iran is under attack, not Israel. The U.S.-Israeli coalition is the aggressor, not the surrounded party. So the literal template of Revelation 16 (Armageddon — the valley of Megiddo in northern Israel) or Zechariah 12 ("I will make Jerusalem a cup of trembling for all the peoples around") does not yet fit cleanly. However — the Catholic tradition consistently warns against mapping current events too literally onto prophetic texts. St. Augustine cautioned in City of God that Revelation is primarily about the cosmic struggle between the City of God and the City of Man — not a geopolitical roadmap. The Catechism (CCC 675–677) speaks of a final trial of the Church but is deliberately restrained about specifics. 𝗪𝗵𝗮𝘁 𝗜𝘀 𝗧𝗵𝗲𝗼𝗹𝗼𝗴𝗶𝗰𝗮𝗹𝗹𝘆 𝗥𝗲𝘀𝗼𝗻𝗮𝗻𝘁 𝗥𝗶𝗴𝗵𝘁 𝗡𝗼𝘄 Even if this is not Armageddon, several features of this moment carry serious theological weight: 1. 𝗧𝗵𝗲 𝗻𝘂𝗰𝗹𝗲𝗮𝗿 𝗱𝗶𝗺𝗲𝗻𝘀𝗶𝗼𝗻. Operation Epic Fury targets Iranian nuclear sites — removing the capacity for a nuclear first strike on Jerusalem eliminates one precondition for the endgame scenario. 2. 𝗟𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 𝘀𝘂𝗰𝗰𝗲𝘀𝘀𝗶𝗼𝗻 𝗶𝗻 𝗜𝗿𝗮𝗻. Khamenei's death disrupts the Islamic Republic's founding eschatological project — preparing the ground for the return of the Hidden Imam — at its center. 3. 𝗧𝗵𝗲 𝗚𝗼𝗴/𝗠𝗮𝗴𝗼𝗴 𝗰𝗼𝗮𝗹𝗶𝘁𝗶𝗼𝗻 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻. Ezekiel 38 names Persia (Iran) as part of the coalition that descends on Israel — but in that text, Iran is attacking Israel, not being attacked. One interpretation: this conflict is a precursor reshaping the regional order before the prophesied sequence unfolds. 4. 𝗥𝘂𝘀𝘀𝗶𝗮'𝘀 𝗿𝗼𝗹𝗲. Long identified by many as "Gog, from the land of Magog" (Ez. 38:2) — Russian oil is now being quietly de-sanctioned, Russia benefits indirectly from Iran's destruction, and the Ukraine conflict is simultaneously being wound down. 5. 𝗧𝗵𝗲 𝗧𝗲𝗺𝗽𝗹𝗲 𝗠𝗼𝘂𝗻𝘁 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻. The conflict that would most directly trigger classical eschatological conditions would involve Jerusalem directly. That has not happened. This war is about Iran's nuclear and military capacity — not Jerusalem. 𝗧𝗵𝗲 𝗛𝗼𝗻𝗲𝘀𝘁 𝗖𝗮𝘁𝗵𝗼𝗹𝗶𝗰 𝗣𝗼𝘀𝗶𝘁𝗶𝗼𝗻 The Catechism (CCC 673) warns explicitly against the "millenarian" error of mapping prophecy onto current events with false precision. The spiritually mature response is not to say "this is Armageddon" — nor to dismiss the question. The conditions are creating the structural prerequisites. The elimination of Iran's theocratic regime, the disruption of the Gog/Magog candidate coalition, the geopolitical reorganization of the Middle East, the economic tribulation spreading globally — these are directionally consistent with the prophetic literature, even if the specific fulfillment remains hidden from us. The medievals had a beautiful phrase for this posture: 𝘷𝘪𝘨𝘪𝘭𝘢𝘵𝘦 𝘦𝘵 𝘰𝘳𝘢𝘵𝘦 — watch and pray. Not panic. Not dismissal. Clear-eyed watchfulness, because the timeline belongs to God alone. No generation since 1948 or 1967 has had more reason to take prophetic literature seriously as a category of meaning — even if not as a predictive algorithm. The talk shows are silent because they have no framework for this. You do. That is worth something. 𝘕𝘰𝘵 𝘧𝘪𝘯𝘢𝘯𝘤𝘪𝘢𝘭 𝘢𝘥𝘷𝘪𝘤𝘦. 𝘕𝘰𝘵 𝘵𝘩𝘦𝘰𝘭𝘰𝘨𝘪𝘤𝘢𝘭 𝘤𝘦𝘳𝘵𝘢𝘪𝘯𝘵𝘺. 𝘑𝘶𝘴𝘵 𝘢 𝘊𝘢𝘵𝘩𝘰𝘭𝘪𝘤 𝘈𝘶𝘴𝘵𝘳𝘪𝘢𝘯 𝘱𝘢𝘺𝘪𝘯𝘨 𝘢𝘵𝘵𝘦𝘯𝘵𝘪𝘰𝘯. 𝘉𝘶𝘪𝘭𝘵 𝘸𝘪𝘵𝘩 𝘊𝘭𝘢𝘶𝘥𝘦 + 𝘦𝘹𝘤𝘢𝘭𝘪𝘣𝘶𝘳-𝘮𝘤𝘱 ⚡