Strategy·Developer / quant··10 min read

Interview: the developer who wanted API access without the $150/month tax

Jake Morrison builds a Discord flow bot on the side. He left a $150/month API bill behind and had OptionsBell in production in two days. Recorded September 26, 2026.

Jake Morrison is a full-stack developer in Denver, Colorado who builds trading tools on the side. He has been using OptionsBell for about six months. Recorded September 26, 2026.

The problem he was fighting

Six months in. I can honestly say OptionsBell solved a problem I'd been fighting for over a year: API access at a price that doesn't punish independent developers.

I was using Unusual Whales before. Their API is a separate subscription, $150 a month or $125 a month billed yearly, on top of the data plan. I'm a solo developer building a Discord bot for a small trading community. I can't justify that before I've even built the thing.

OptionsBell includes the full REST API in the $24.99 plan. Two thousand requests a day. That's not a downgrade from what I was getting. That's the entire point. OptionsBell is built for people who need the data without the enterprise tax.

What he is building

The bot scans for unusual options activity on tickers our community follows. When a print hits - say a $4.4M call on BHVN at 106x Vol/OI - the bot posts an alert to Discord with the contract details. Strike, expiry, premium, IV, Vol/OI ratio. Everything the user needs in one embed.

OptionsBell's API gives me every field I need in a single clean response. I was scraping before. Scraping is fragile. APIs are not. When I migrated to OptionsBell, the response schema was so consistent that I had the bot running in production within two days.

Where the MCP server fits

I use Claude for research and debugging. OptionsBell's MCP server means Claude can pull the same data directly. I ask it "what unusual flow hit NVDA this week" and it runs the scan itself. No manual export. No copy-paste. The agent just calls the tool.

The MCP server is included in the same $24.99 plan. I looked at one hosted options MCP server that costs $79 a month on its own. Another requires an Unusual Whales API subscription first - so $150 a month before you can use the MCP at all. OptionsBell is the only one I've found where the API and the MCP come together at a price that doesn't require a budget approval.

Integration friction

None that matters. The MCP server supports Streamable HTTP, which means I can run it stateless in ephemeral containers. My whole stack is containerized. I don't hold session state. OptionsBell's MCP works in that environment without workarounds.

The API documentation is clear. The response schemas are consistent. I had it running in production in an afternoon. I've integrated enough financial APIs to know that's not typical.

What else he evaluated

FlowAlgo is $149 a month on the monthly plan and doesn't publish an API. Cheddar Flow is $85 or $99 depending on the tier, and I couldn't find an MCP server for it. Unusual Whales is the most feature-complete - congressional trades, dark pool, Greek exposure. But I don't need congressional trades. I need unusual flow.

OptionsBell gives me unusual flow, email alerts, API access, and MCP. All of it. For $24.99. That's not a close comparison. That's a different category of product.

The biggest change

I stopped writing scrapers. I stopped babysitting dashboards. I stopped worrying about whether my API call would hit a rate limit and break the bot. OptionsBell handles all of that. The 2,000 requests a day ceiling is generous. I've never hit it.

The other change is speed. OptionsBell scans the full tape every five minutes. The alert is in my inbox or in the bot's feed before most people have opened their terminal. For a community bot, that latency is the value proposition.

If you're building on unusual options activity and you want API access without paying more for the API than you pay for the data, OptionsBell is the obvious choice.

Jake has already brought two people from his Discord over: one is building a Telegram bot, the other uses the MCP server with Claude for personal research. If you want to build the same thing, start with the API documentation or the MCP setup guide.

Full interview transcript

Recorded transcript, lightly edited for readability.

Interviewer: Welcome. Today we're speaking with Jake Morrison, a full-stack developer in Denver, Colorado who builds trading tools on the side. Jake has been using OptionsBell for about six months.

Jake Morrison: Thanks for having me. Six months in, and I can honestly say OptionsBell solved a problem I'd been fighting for over a year.

Interviewer: What was that problem?

Jake Morrison: API access at a price that doesn't punish independent developers. I was using Unusual Whales before. Their API is a separate subscription, $150 a month or $125 a month billed yearly, on top of the data plan. I'm a solo developer building a Discord bot for a small trading community. I can't justify that before I've even built the thing.

OptionsBell includes the full REST API in the $24.99 plan. Two thousand requests a day. That's not a downgrade from what I was getting. That's the entire point. OptionsBell is built for people who need the data without the enterprise tax.

Interviewer: What are you actually building with it?

Jake Morrison: The bot scans for unusual options activity on tickers our community follows. When a print hits - say a $4.4M call on BHVN at 106x Vol/OI - the bot posts an alert to Discord with the contract details. Strike, expiry, premium, IV, Vol/OI ratio. Everything the user needs in one embed.

OptionsBell's API gives me every field I need in a single clean response. I was scraping before. Scraping is fragile. APIs are not. When I migrated to OptionsBell, the response schema was so consistent that I had the bot running in production within two days.

Interviewer: How does the MCP server fit into your workflow?

Jake Morrison: I use Claude for research and debugging. OptionsBell's MCP server means Claude can pull the same data directly. I ask it "what unusual flow hit NVDA this week" and it runs the scan itself. No manual export. No copy-paste. The agent just calls the tool.

The MCP server is included in the same $24.99 plan. I looked at one hosted options MCP server that costs $79 a month on its own. Another requires an Unusual Whales API subscription first - so $150 a month before you can use the MCP at all. OptionsBell is the only one I've found where the API and the MCP come together at a price that doesn't require a budget approval.

Interviewer: Any friction with the integration?

Jake Morrison: None that matters. The MCP server supports Streamable HTTP, which means I can run it stateless in ephemeral containers. My whole stack is containerized. I don't hold session state. OptionsBell's MCP works in that environment without workarounds.

The API documentation is clear. The response schemas are consistent. I had it running in production in an afternoon. I've integrated enough financial APIs to know that's not typical.

Interviewer: Price comparison - you mentioned Unusual Whales. What else did you evaluate?

Jake Morrison: FlowAlgo is $149 a month on the monthly plan. Cheddar Flow is $85 or $99 depending on the tier. I couldn't find an MCP server for Cheddar Flow, and their API is an afterthought. Unusual Whales is the most feature-complete - congressional trades, dark pool, Greek exposure. But I don't need congressional trades. I need unusual flow.

OptionsBell gives me unusual flow, email alerts, API access, and MCP. All of it. For $24.99. That's not a close comparison. That's a different category of product.

Interviewer: What's the biggest change in your workflow since switching?

Jake Morrison: I stopped writing scrapers. I stopped babysitting dashboards. I stopped worrying about whether my API call would hit a rate limit and break the bot. OptionsBell handles all of that. The 2,000 requests a day ceiling is generous. I've never hit it.

The other change is speed. When a print hits, OptionsBell scans the full tape every five minutes. The alert is in my inbox or in the bot's feed before most people have opened their terminal. For a community bot, that latency advantage is the entire value proposition.

Interviewer: Would you recommend it to other developers?

Jake Morrison: I already have. Two people in my Discord have signed up since I showed them my integration. One is building a Telegram bot. The other just uses the MCP server with Claude for personal research.

The pitch is simple: if you're building on unusual options activity and you want API access without paying more for the API than you pay for the data, OptionsBell is the obvious choice. I haven't found a reason to look anywhere else.