Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A Collection of Free Public APIs That Is Tested Daily

freepublicapis.com

Post reply on HN
Print view View original

121–130 of 130 posts

Re: A Collection of Free Public APIs That Is Tested Daily

#121

Post by bliteral »

fragmede wrote: post #120
bliteral wrote: post #73

Earlier quoted context omitted.

https://api.isfizzbuzz.xyz/ Cheers!

The error response telling me to upgrade to a paid plan isn't in json. Also, I broke something, maybe in the caching logic. I tried 99999999 then 999999 then 99999 and down, and now I'm currently getting. ~$ curl https://api.isfizzbuzz.xyz/api/9 Invalid number. Please upgrade to a paid plan to use imaginary, non-real, or non-numeric numbers. also fails on 8.

Whoops, fixed and fixed! And regression tests added.

I had made a silly, silly mistake when I went to restrict numbers longer than 7 digits from the "free plan", I had at the same time disallowed digits larger than 7 as being "valid digits", so anything with an 8 or a 9 had been "invalid".

Re: A Collection of Free Public APIs That Is Tested Daily

#123

Post by therealdrag0 »

rozenmd wrote: post #3

(This doesn't apply to every API in the list, but) having made the mistake of using a public API (that later went offline) for examples in a book of mine, never again. These days I keep an API deployed on a subdomain I control.

I’ve seen books reference internet archive.

Re: A Collection of Free Public APIs That Is Tested Daily

#124

Post by ehnto »

ozim wrote: post #72
ehnto wrote: post #70

I tried to build something years ago on a similar foundation, and I found maintaining the API list to be impossible as a solo dev. In a pool of say 30 APIs, at least one would break their "contract" as a public resource daily. Shifting endpoints, revoked public tokens, changing outputs. I was quite disappointed because I loved the product, a dashboard for arbitrary live data sourced from APIs, but the cost of maintai…

I would say that would be my use case for LLMs. These should be easily fixed by automation that can reason about documentation and could spit out code fixes. Of course I assume there is documentation that is updated before new changes go live which might be too much to ask :)

It's interesting engineering problem, I wouldn't imagine LLMs as they currently are could work directly on the whole codebase without breaking it just as often as the APIs. But perhaps you could have it maintain connectors/interfaces for each individual API, such that it can get one very wrong and not ruin the whole program.

You could even have its success depend on a test suite, so that it iterates until the tests pass.

Re: A Collection of Free Public APIs That Is Tested Daily

#125

Post by ozim »

ehnto wrote: post #124
ozim wrote: post #72

Earlier quoted context omitted.

I would say that would be my use case for LLMs. These should be easily fixed by automation that can reason about documentation and could spit out code fixes. Of course I assume there is documentation that is updated before new changes go live which might be too much to ask :)

It's interesting engineering problem, I wouldn't imagine LLMs as they currently are could work directly on the whole codebase without breaking it just as often as the APIs. But perhaps you could have it maintain connectors/interfaces for each individual API, such that it can get one very wrong and not ruin the whole program. You could even have its success depend on a test suite, so that it iterates until the tests p…

For “API list” that only has tests to be fixed, something like shifting endpoint should be fixable with tests + LLM.

So that’s the idea I proposed that single dev with automation and LLM should be able to maintain “API list” but maintaining any code that depends on the API I expect is above LLMs.

Re: A Collection of Free Public APIs That Is Tested Daily

#126

Post by schwartzworld »

RicoElectrico wrote: post #6

Paraphrasing a known saying, "there's no API, it's just someone else's computer". I wish programmers would internalize this. They often seem to take APIs uncritically, not questioning whose resources they're using and where does the data come from as well as its quality beyond obvious cases. APIs are leaky abstractions as all abstractions are.

That’s “there’s no cloud”. Of course there are APIs.

Re: A Collection of Free Public APIs That Is Tested Daily

#127

Post by luckman212 »

lobsterthief wrote: post #91
arjvik wrote: post #18

Earlier quoted context omitted.

> You can't sell ads on it. Maybe you could! Perhaps a sample data API that creates users like "John Chocolate Oreos," address "100 Pack Street", age 19.99, email "visit oreo.com"

I don’t think Oreo would want to commit ad spend to that—it would perform worse than the display network, and worse than the Outbrain/Taboolas of the world.

I get the feeling arjvik's comment was meant to be sarcasm.
Post reply on HN