A Collection of Free Public APIs That Is Tested Daily(freepublicapis.com) |
A Collection of Free Public APIs That Is Tested Daily(freepublicapis.com) |
Found public resources I always wished existed.
I was quite disappointed because I loved the product, a dashboard for arbitrary live data sourced from APIs, but the cost of maintaining it was too high.
Of course I assume there is documentation that is updated before new changes go live which might be too much to ask :)
You could even have its success depend on a test suite, so that it iterates until the tests pass.
And there's a weekly data dump of our database: https://rubygems.org/pages/data
Not to QC the link title, but ;)
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.
Maybe you could! Perhaps a sample data API that creates users like "John Chocolate Oreos," address "100 Pack Street", age 19.99, email "visit<at>oreo.com"
These days I keep an API deployed on a subdomain I control.
> having made the mistake of using a public API (that later went offline) for examples in a book of mine
Literally a tale as old as time. The Old Testament references a command from God, that is not contained in the Old Testament itself.Add a fancy feature of redirection with format changing to handle replacing dead APIs with new ones transparently.
If anybody makes one of these, they should totally make it a free public API. I'd use it, and I'm not certain if that would just be ironically.
> Running an API Forwarder that could act as a common target for all your APIs might work.
That just sounds like adding another point of failure into the chain.Best part is that 'sign up' links to https://archive.org/donate/
API Result:
GET https://api.isevenapi.xyz/api/iseven/6/
{"ad":"Buy isEvenCoin, the hottest new cryptocurrency!","iseven":true}
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.
Hence testing them daily to see if the someone else is still offering them.
Not all abstractions are leaky. Not at all.
There's not a lot of incentive to create a service if you feel like no-one will ever know about it. I have had a few thoughts for services that I might have developed if I thought anyone would ever see it.
There's probably an argument for sponsorship here as well, not as a vehicle for advertising, but just companies paying for (or supplying resources) to cover the ongoing costs of the service as a public good. I wish I could make something that worked and could put it somewhere and commit zero mindspace to billing, server maintenance etc. and just have it keep running, forever.
Where does one get a geo location for an IP address from?
There's a bunch of IP/GPS and physical address lookup sites, services, and databases out there.
Bummer.
I remember years ago doing something as simple as getting a coin onto an alt-chain was a 20 step process. Get the gas coin on the target chain, find the right contract address, bridge the assets over, do a bunch of conversions, finally to get the token on the chain I wanted.
These days its a single click. Different tools or companies have sprung up, and while they use the same exact contracts I would have manually interacted with before, they script them all together into one transaction to save time and gas fees. A simple UI to select destination chain and coin and it handles all the swaps, gas, bridging, etc needed.
You don't need permission and a lot of standards have developed to keep things running smooth.
It's not just coins and crypto either. No reason not to develop other things off the chain too.
I've been working on my own PIM (personal information management) suite and using web3 has been amazing. No need to worry about a server or a database. Just deploy my code to the chain and store all my data encrypted on chain as well. The altchains are extremely cheap and this storage is already backed up, replicated, distributed, and can be local with a self-ran node. I will never lose it and I can bootstrap my data from scratch anywhere in the world as long as I can sync the chain or reach an API. I have todo lists, notes, contact management, and more in the pipeline and I've never felt so safe about my infrastructure or data before.
- https://web.archive.org/web/20180530151717/https://forestry....
- https://web.archive.org/web/20180525154607/https://forestry....
This is really great overall. I like the interface on mobile, and search works great for me so far. Bookmarking for later.
One nitpick: why can I not open like KS to API sub-pages in a new tab? Are Hyperlinks unfashionable now?
Design flaw, sadly. Also very annoyed by this.
Australia's was enough that the unfortunately complicated math of their election system was repeatable and verifiable (Can't find the post about it, however)
IMHO sitemap.xml and/or ActivityPub are sleeper approaches to helping the sites with the adversarial relationship they have with scrapers. In my experience, there are two schools of thought: play the very expensive game of cat and mouse (expensive for BOTH sides) of trying to verify the human-ness of visitors, or make it so the inevitable bots don't eat up very expensive and valuable resources that can be spent serving actual humans
Imagine how much less nonsense would have to go on if Amazon had ActivityPub that CamelCamelCamel could subscribe to, or similar for Craigslist
I'm not saying "all information wants to be free," so if Amazon wants to focus its energies on hoarding the review content, since that's arguably its moat, fantastic - let the bot and anti-bot people war over that content, instead of arguably factual data found on the product listing pages
I think you getting confused with opinion polling.
I'm not saying these shouldn't exist, I think they're pretty funny, but everything in its place.
"They were stoned, they were sawn asunder, were tempted, were slain with the sword: they wandered about in sheepskins and goatskins; being destitute, afflicted, tormented;"
I stand by my rant :-D but obviously stand corrected on the question being asked
{"ad":"Looking for someone to do yard work. Must have a hoolahoop. 760-555-7562","iseven":true}
{"ad":"FOR SALE - collection of old people call 253-555-7212","iseven":true}
{"ad":"Auto Repair Service: Free pick-up and delivery. Try us once, you'll never go anywhere again. Email dave57@qotmail.com","iseven":true}
$ curl https://api.isevenapi.xyz/api/iseven/9999999
{"error":"Number out of range. Upgrade to isEven API Premium or Enterprise."}
$ curl https://api.isevenapi.xyz/api/iseven/2e21
{"error":"what is this I don't even"}> APIs handpicked by the University of Applied Sciences of Grisons for their IM2 JavaScript programming course...
Cheers!
https://api.isfizzbuzz.xyz/api/15000000000000000000000000000...
BTW, there are neat divisibility rules which can give you the answer in practically linear time when the number is in decimal: https://en.wikipedia.org/wiki/Divisibility_rule
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.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".