u/Existing-Wallaby-444

REPOST: Deleted first post because it didn't include my text with a video. So I switched to an image.

--

You know the drill. You're vibing, shipping features, and then you need to hit some API. Your AI writes code that looks right but the endpoint doesn't exist, the parameter got renamed, or the auth flow is two versions out of date. Suddenly you're not vibe coding anymore. You're manually reading API docs and trying to figure out why the thing that looks correct just fails silently.

Built openapi.city to fix that. Your AI queries it for the exact endpoint and schema instead of guessing from training data. Right now there are a bit over 100 APIs indexed. I want to get that to a few thousand when I find the time, but the current set already covers the stuff I personally run into daily. Specs refresh weekly so they don't rot.

Heads up: this is pretty early stage. Things might not always work perfectly, and there are definitely rough edges. That said, I've been dogfooding it for a while now and it's already saved me a ton of API debugging time. Your mileage may vary.

Built the whole thing with Rails 8. OpenCode with GLM 5/5.1 and Kimi K2.5/2.6 wrote a solid chunk of it. I vibe coded a tool to make vibe coding less annoying, which feels very on brand for this sub.

Free tier if you want to mess around with it. No credit card, no sneaky stuff.

Just genuinely curious if this is a pain you've run into too, or if I'm uniquely cursed with bad API luck.

Check it out: openapi.city

I have been working on side projects for a while and lately I have been using AI agents to speed things up. The workflow is amazing most of the time. But there is one thing that keeps killing my momentum.

Every time I ask my agent to integrate with some API, it writes code that looks correct but uses endpoints that do not exist, parameters that got renamed months ago, or auth flows that are two versions out of date. I end up spending twenty minutes manually reading API docs to debug what should have just worked. It is the same frustration every single time.

I got annoyed enough that I decided to just build the thing I wished existed. It is called openapi.city.

The idea is simple. Instead of your AI guessing how an API works from its training data, it queries openapi.city for the exact endpoint, parameters, and schema it needs. Lean response, no fluff, actually current. Right now there are a bit over 100 APIs indexed. I want to grow that to a few thousand when I find the time, but the current set already covers the APIs I personally hit daily. Specs refresh automatically every week.

Fair warning: this is still pretty early stage. There are rough edges and not everything works perfectly yet. But I have been dogfooding it for a while now and it has already saved me a ton of debugging time.

Tech stack is Rails 8. A good chunk of the codebase was written by OpenCode with GLM and Kimi models, which felt very meta. I basically used vibe coding to build a tool that makes vibe coding less painful.

Free tier available if you want to try it. No credit card required.

I am not trying to turn this into a massive launch or anything. Just wanted to share the project with fellow builders and hear your honest thoughts. Is API hallucination something you run into too, or is this a very specific pain I happen to have?