OpenAPI Specification

“OpenAPI can't do that, and OpenAPI also needs a codegen step”

“just adding some semi-standard attributes to OpenAPI specs to make them more LLM consumable”

“validates everything against an OAS so the agent can't make invalid requests”

“It addresses all the key description and security details.”

“another one on the OpenAPI schema”

“OpenAPI 3.0 has auth. You can turn OpenAPI specs into tool calls just as well”

“Pair it with OpenAPI and the whole thing is self-documenting.”

“I really like OpenAPI in conjunction with openapi-fetch to create a typed interface”

“Today, there's tooling around OpenAPI/Swagger, but I don't think it's nearly as nice as using WCF”

“developing against a spec, like OpenAPI, and using/building an auto-generated SDK is still very useful for coding agents”

“using something like OpenAPI to share the schema is a subpar solution”

“A good OpenAPI spec was working perfectly fine for me all the way back when OpenAI introduced GPTs.”

“Swagger / OpenAPI just aren't detailed enough to use without other documentation.”

“OpenAPI is really outdated and the tooling is always a mess.”

“with OpenAPI for shared types”

“Why not just extend the OpenAPI specification to skills?”

“Swagger and OpenAPI were attempts to solve problems that only exist because we didn't stick with REST”

“OpenAPI, JsonSchema, GraphQL all describe *Data*.”

“OpenAPI is great, there are a lot of tools to go from OpenAPI to UI, but you don't have a lot of control over the presentation.”

“But you know what also gives you auto-generated code that works perfectly without a hitch, with full schema validation?”

“Except everyone who ever used standards like OpenAPI and JSON Schema.”

“OpenAPI specs really don't have that much overhead (especially if you make use of YAML anchors)”

“That is very viable these days, just isn't a "default" in the ecosystem.”

“OpenAPI, Thrift and protobuf/gRPC are all far better schema languages.”

“Specs drift from reality, documentation lies, and you're trusting convention”

“I write all of my openapi specs by hand. It's not hard.”

“the issue we face is that REST API specs for many products are either missing, incomplete or simply outdated”

“Post-honeymoon, I returned to REST+Open API”

“The whole spec would consume a huge fraction of context tokens.”

“Yes, and it's called OpenAPI.”

“Most existing OpenAPI specs out there don't clear that bar”

“open-api 3.1 is still not viable, and isn't looking like it will be anytime soon.”

“Many users are stuck at 3.0 or even Swagger 2.0 because the libraries they use refuse to support recent versions”

“OpenAPI 3.1 replaced the not-a-superset-or-subset of JSON Schema with the actual JSON Schema”

“having a document describing how your API works, including types, that is important”

“OpenAPI is another good choice”

“OpenAPI is also a good choice nowadays.”

“OpenAPI v3 would be a much better fit”

“OpenAPI supports a lot of languages, not just 2.”

“OpenAPI (which I've used and it's a mediocre solution)”