fusionauth-openapi VS m3o

I talked to a startup ( https://stainlessapi.com/ ) about a service they provide where they take an OpenAPI spec and build good SDKs on top of it. This included making sure they are idiomatic, included examples, handled exceptions if needed, and some other goodness. I passed for now because they don't have the language support we need and I am not sure if we need their level of sophistication, but others may benefit from talking to them. (I think the founder helped build Stripe's API docs, IIRC.)

As we head down our OpenAPI path (https://github.com/fusionauth/fusionauth-openapi has only been built for the last 9 months), I'm very interested in stories like yours. We're very interested in quality SDKs that are easy to update. But since we control the OpenAPI spec for the product, we might have an easier time than you in some ways.

Thanks for sharing!

As someone who just released an OpenAPI spec for our API and struggled with building client libraries to test that the spec was correctly generated, I'd pay for this, especially if it integrated with the rubygems/packagists/nugets of the world.

Let me know if you want an alpha or beta tester. Our OpenAPI spec is here: https://github.com/fusionauth/fusionauth-openapi and my contact info is in my profile.

Sorry what I meant is I've been working on the open source Micro project for 8 years which underpins this. The chat app itself was not really something I meant as being open source but yes it's in a separate repo with the API hosting product I built called M3O.com.

https://github.com/m3o/m3o

Email: [email protected]

Spent the last 10 years mostly working with microservices and Go based startups, although I would not recommend microservices to most companies. I can save you a few million dollars if you wonder why.

I'm most passionate about improving DevEx in companies. Things like writing custom ORMs for lesser known/supported databases (see eg. https://github.com/gocassa/gocassa). Mostly worked with startups from $2M-$500M funding range, with the occasional enterprise gig.

Used to run a chicken shop as a hobby project which made me careful of accepting management positions, haha, people are hard. I would love to be a product owner, I mostly designed the https://m3o.com/ product with the CEO recently and implemented the MVP of it. It's open source stuff, check it out https://github.com/m3o

Currently working for a US startup but my contract is ending soon.

Cheers!

It's like API indexing, I like it. I started M3O (https://m3o.com) with this idea of API aggregation for absolutely everything but not specifically indexing, more so providing a uniform access layer to all things with one API token. The programmability of Nango will definitely a be a selling point. For the founders, focus on that, double down on that. The ability to program the APIs and the data retrieved is really key.

What if any is the relationship between https://m3o.com/ and https://micro.dev/ ?

Nocode poses a really interesting movement towards rapid prototyping end user facing apps but I think when it comes to functionality, there's always some need to drop into the escape hatch to make that API call or manipulate some javascript. I've been noticing more people using https://m3o.com for that especially with things like Adalo. There's 70+ APIs that can be used with one API token. Super useful. Also on the lookout for other API providers who make it easier to embed those apis.

We can potentially do this on https://m3o.com. It doesn't exist yet but would make sense as the next service we offer. Further details would be useful e.g endpoints required.