application programming interface

I would say some EHRs make our lives super easy.

They're like, here's APIs, you can pay for access, we'll get you into our developer portal.

Others I've been in fights with now for six months plus where they're just like, we don't want third parties to have access to this data.

And I think it's a combination of they're both a little bit like trepidatious of letting sort of the hen or the fox into the hen house.

There's some interesting developments in the last couple of days.

Yeah.

MCP protocols and the automated transfer of data between healthcare APIs.

Yeah.

It needs to understand the causality of the system.

So if it changes a variable in a core database schema, it has to know which APIs rely on that schema and which front end components consume those APIs.

Oh, I see.

It's mapping the blast radius of its own code.

Did you guys cover the story of a world cup where this was possible with the world cup? Somebody got into the backend video stream infrastructure just by creating an account on like a public account you could create.

They found the API end points and the API end points were not secured.

And this guy eventually finds his way on this webpage where it's like, What is the protocol? RTSP or something?

RTSP, yep.

Verified Ultra users no longer have a five-hour limit.

The Max and Ultra plans include API credits equal to total plan cost on top of the monthly limits.

Heading.

On your marks.

I don't think there should be an opt-out, which rather destroys the point of watermarking.

Live in China and want Claude and Codex accounts.

They're so valuable that it plausibly makes sense to go to America to set up a bank account and get a credit card, as you get $8,000 a month in Claude API credits for roughly $200 on each account.

The math checks out if you think you'll get to keep your accounts.

FutureSearch wasn't designed to do things more complex than a simple clearer framed forecast, so it bungled the various calculations involved in the Autogranter process.

What seems to have worked is to run the Autogranter on Claude Opus, but give it a connector that allows it to call FutureSearch via the API for all components of the grant analysis that benefit from a probabilistic forecast.

For example, in one case where the success of an organization depended on it getting a new CEO quickly, Claude gave the relevant information to FutureSearch and asked it to predict the probability that it would find a new CEO within six months.

In another case where an organization was working on verification technology, Claude asked FutureSearch to predict whether the political situation would lead to a treaty where the relevant verification was necessary.

FutureSearch has kindly given me a free subscription, but if you're paying through the API, it's about $1 to $5 per query like this.

I asked Claude to limit itself to five queries per grant analysis.

Precene and Mantic have competing AI superforecaster products with equal evidence of accuracy.

An average Autogranter run on Opus 5.5 High Effort uses about 30% of my 5-hour limit.

I probably will before I use this.

But I would suspect it's using the NPM and Composer APIs to understand the dependency chains and then just building a graph from that.

That's how it's building that fancy galaxy thing.

map that John had mentioned, but it's certainly possible to include things directly.

But Kind of the whole point of using something like Composer MPM is that it does dependency management.

And because it does that, it can report fairly accurately what is installed through itself.

So it's using those APIs, I would suspect.

Could there be bugs or gaps? Certainly.

And then they also need to be able to access the full set of platform capabilities.

So all of our APIs need to be documented.

They need to be available via MCP.

So that's been a big deal.

So a lot of founders, they find growth channels, they find team members, but they don't build it in a way that's sustainable.

You know, they might find a loophole inside of some Facebook API or some LinkedIn thing or some scraping email outbound system or whatever it is.

I've seen every variation possible, but they're not sustainable.

So you need to build the business where the comp structure for your executive team, where the marketing channels that you're using are not gray area, where the product allows it to sell itself.