At https://connectstrata.com/ we're using OpenAPI specs a bit differently than most. Rather than using them to build client libraries, we're feeding them to agents that generate automations and data pipelines across SaaS APIs. As you would imagine, SOTA models are great at generating these transformations, so the challenge becomes maintaining accurate and up-to-date schemas. When API providers don't make a schema available, scraping one from documentation works but it's unreliable and requires a lot of validation.
We're experimenting with generating OpenAPI specs by parsing Typescript SDK abstract syntax trees and converting the types to JSON Schema definitions. This is tricky because the JSON Schema specification isn't a data definition language, it's primarily intended for validation use cases. Things like class hierarchies and generics are difficult to translate.
The process worked well for Slack, so we wanted to make the spec available for anyone to use. We've been propelled along by plenty of community-maintained specs on github.
If you've done any work generating OpenAPI or JSON Schema specs from non-source code sources I'd love to hear about it!
jmclai•1h ago
At https://connectstrata.com/ we're using OpenAPI specs a bit differently than most. Rather than using them to build client libraries, we're feeding them to agents that generate automations and data pipelines across SaaS APIs. As you would imagine, SOTA models are great at generating these transformations, so the challenge becomes maintaining accurate and up-to-date schemas. When API providers don't make a schema available, scraping one from documentation works but it's unreliable and requires a lot of validation.
We're experimenting with generating OpenAPI specs by parsing Typescript SDK abstract syntax trees and converting the types to JSON Schema definitions. This is tricky because the JSON Schema specification isn't a data definition language, it's primarily intended for validation use cases. Things like class hierarchies and generics are difficult to translate.
The process worked well for Slack, so we wanted to make the spec available for anyone to use. We've been propelled along by plenty of community-maintained specs on github.
If you've done any work generating OpenAPI or JSON Schema specs from non-source code sources I'd love to hear about it!