Four Dead Projects and the Line of ‘Code’ That Would’ve Saved Them

I have four Claude API projects on this site. A legacy code explainer. A contract analyzer. A changelog generator. A job scrub pipeline. All of them work. All of them are demo-only — read about it, don’t touch it — because I never actually solved the problem that mattered, and the problem was never the code.

The problem was math. What happens the day this gets noticed, and two hundred people show up and start running completions on my card? I didn’t have an answer. So the safest move was: don’t let anyone in. Which is its own kind of failure — a working product nobody’s allowed to use.

Then I hit Sampling, and it’s the answer I didn’t know I was hunting for.

Normally, an MCP server that needs to think mid-task — summarize, classify, decide something — needs its own API key. Its own bill. Fine for a toy. A liability the second it’s public.

Sampling flips it. The server doesn’t hold the key. It turns to whoever it’s connected to and asks: can you run this one? Their model does the thinking. Their key eats the cost. Say it plainer — it’s your server asking to run something on your card. Except “your” here means whoever’s actually using it, not you.

And you don’t lose control just because you’re footing the bill. Every prompt gets shown to you before it reaches the model. Every answer, before it goes back. You’re not just the wallet. You’re the bouncer deciding what actually gets in.

Roughly:

Server:  "I need a completion to summarize this file."
             ↓  sampling/createMessage
Client:  shows you the prompt → you approve → sends it to your model
             ↓
Your model does its thing
             ↓
Client:  shows you the answer → you approve → hands it back to the Server

The server gets the output. It never sees the receipt.

Here’s what that actually unlocks for my four dead projects: guests get a small ration, enough to see if the thing’s worth their time. Bring your own key, and it’s unlimited — because now you’re paying for yourself, not me.

Four demos. Four things I built and then quietly hid from the internet because I never ran the numbers on day one going viral. Turns out the fix wasn’t more code. It was one architectural decision I didn’t know existed three weeks ago.

Every course before this one gave me feature ideas. This is the first one that gave me a business idea. Different muscle. Better one.