Comments URL: https://news.ycombinator.com/item?id=45350381

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=41770449

Points: 4

# Comments: 1

We have the OpenBB Platform CLI, a command line interface (CLI) that allows users to access a lot of financial data but needs to bring each API key.

The reason why this works is that once you run the CLI, you are running it on your machine and leveraging your own API keys - which, when you subscribe you sign for Terms and Conditions.

And, in it, it usually states that you cannot use the data for any commercial purpose.

This is what most data vendors do. Not only because they are trying to upsell you but because giving you access to data costs them money.

So, most of the APIs that you find that are free and have the rights to distribute that data are usually from governments (e.g. FRED or Companies House https://developer.company-information.service.gov.uk/get-sta...)

We have a paid enterprise product: OpenBB Terminal Pro (https://openbb.co/products/pro).

In it, users have access to several datasets that we have redistribution rights for. This enables users to export any dataset but also to access that same financial data through our Excel Add-in.

Most retail financial products only have display rights as it's much cheaper than the redistribution license.

Most data vendors will require a free API key because that's their GTM. They want you to create an account with them to get a free API key and then expect to be able to upsell you over time.

Or you can access "free data" (e.g. yfinance) that relies on projects who actively scrape financial data from a website - these tend to need a lot of updates from main maintainer since there are no aligned incentives between maintainer of the scrapped API and company that has the data.

PS: I'm the main creator behind the OpenBB project on GitHub.

PyWry is also a ~2mb footprint for Mac and Windows - Linux will require a few more libraries which are listed below.

Comments URL: https://news.ycombinator.com/item?id=36303570

Points: 2

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=35944313

Points: 2

# Comments: 0

Some of them can be found here: https://docs.openbb.co/terminal/quickstart/api-keys

https://docs.openbb.co/terminal/quickstart/api-keys

After that your API key will allow you limited usage, e.g. AlphaVantage allows 5 requests per minute. This means that if you want more access you'll have to subscribe to one of their premium tiers.

It's not our data, it's their data. We just provide it under OpenBB terminal and API, in 1 place. So you don't need to read 10 different data sources documentations and it's all standardized by us

What we did was wrong, everyone knows it. We came out and apologized. We discussed this for days after it happened internally and with our investors/advisors. But there's nothing else we can do.

You can find the core here: https://openbb.co/products/terminal#features

In any case, you are right. We rely on API keys because unlike BBT we don't own the data, and therefore, we are essentially a platform that aggregates investment research data - and that the user is allowed to customize their own feeds.

FWIW, Databento has just announced a partnership with OpenBB (https://www.linkedin.com/posts/databento_openbb-investment-r...) and they provide real-time data

OpenBB doesn't own any data. But by providing an open source infrastructure, any data can be hooked up into a single platform.

So your argument about BBG isn't valid, because with what we are building there's no reason why OpenBB couldn't integrate with BBG data feeds (if they were open to it).

Regardless, I agree that the Bbg comparison is more for marketing. Our approach is substantially different for a different market.

We literally came out and apologize.

https://github.com/OpenBB-finance/OpenBBTerminal/issues/1625 - this provides my initial train of thought. But the "Welcome to our newsletter" was never the email intended to be sent.

In any case, it was a shitty idea regardless. We apologized for it, but there's nothing we can do now to make up for it.

But that was after I received a SPAM email saying "Welcome to our newsletter" in my personal GitHub account when I wasn't part of that audience.

You can see my interaction with someone from our team here: https://github.com/OpenBB-finance/OpenBBTerminal/issues/1625... - When we realize what had just happened.

We immediately deleted that audience (which was our plan all along anyway), but then it was too late, we were trending on HackerNews and Mailchimp pinged us after. After that it was mostly damage control, as there's nothing we could have done to make things better.