Requires libFUSE (MacOS/Linux) and Python. It was made because I am a CLI kind of guy, and I live in a terminal so being able to fallback on muscle-memory shell instincts (for loops, piping commands and I/O, etc) without having to do a bunch of curling, or browsering, postman, etc.
It occurs to me that with all the hype lately about AI agent tool use, that it could be useful for this purpose as well, since the Agent would not need any special skill for it; the data just becomes navigable and readable as with any file in a directory tree.
I'd be interesting in hearing if you find this useful, dumb, broken, lacking an obvious feature, or anything else you might have to say about it.
ycombiredd•2h ago
I have been solely using an old X86 Darwin MacBook Air for this, so that's the extent of the platform(s) tested. (Writing this has caused me to realize I might want to document the process of installing the FUSE driver on a mac, but I do link to the MacFUSE webpage, which is probably more broadly useful than my experience on this dated laptop.)
Anyway, I actually went searching before posting because it hadn't occurred to me that this might have already been done somewhere else (yeah, one might think searching for an existing solution would be a first thing...) and was happy to see that it doesn't seem to have been exactly put out there before, while also being a bit surprised to see that so many spiritually-related FUSE implementatations have been created since last I had occasion to do anything with FUSE. It might be the case that if I have done this correctly, very-specific niche FUSE implementations will be unneeded, as my hope is that apifusefs is capable of handling any swagger-type, OpenAPI-spec API.
(Eventually, anyway. For example, there exists a massive openapi.json for the GitHub API, but due to the way the root endpoint refers to other endpoints, and each has its own context and auth-requirements, this initial release of apifusefs isn't magic for api.github.com/ even with the spec file, and I had to mount specific endpoints by their URL given in the response to "GET /", to varying degrees of success or failure, which is what caused me to add the --json-file mode,so I could just redirect the output of a curl request to a file and test with that.)
That said, it does now support a variety of ways to pass authentication tokens, so my hope is that if anyone here has an API to try it out against, that it will work for you without hassle.