Evidence tier Source Confirmed · 4 captures on record
What the publisher says
As described on AWS Marketplace.
Why Oasify?
Manually crafting OpenAPI 3 specs from existing API descriptions is error-prone and time-consuming. Oasify automates that translation so you can:
Show the rest of the publisher’s description (21 more lines)
Accelerate API onboarding and documentation.
Migrate legacy SOAP (WSDL) or GraphQL services into REST-friendly OpenAPI.
Ensure your AWS Marketplace offering is accompanied by a standard-compliant API specification.
Integrate seamlessly into CI/CD pipelines with programmatic access.
Core Benefits
Quick conversion: Get OAS3 output in seconds. No manual rewriting.
Format support: Postman, GraphQL (SDL/introspection/URL), WSDL > OpenAPI 3.
How It Works
- Select Source
Choose your input format: Postman JSON, GraphQL schema/introspection/URL, or WSDL XML.
- Upload or Provide
Send the file or endpoint to the /transpile endpoint with your desired output mode.
- Receive OAS3
Get back a fully formed OpenAPI 3 specification as a downloadable file or base64 payload, ready for use.
On-Premises Deployment
Need the solution inside your network? Ask about our on-premises deployment options.
Need Help or Found a Bug?
Help us help you! If the API isn't working as expected, tell us what happened and we'll jump on it ASAP.
Swagger UI: https://api.oasifyteam.uk/docs
ReDoc: https://api.oasifyteam.uk/redoc
Raw OpenAPI schema: https://api.oasifyteam.uk/openapi.json
Highlights
Highlighted by the publisher on AWS Marketplace.
Postman Collections Upload your exported Postman collection (JSON). Oasify infers endpoints, parameters, and schemas and emits a compliant OpenAPI 3 definition ready for documentation or automation.
GraphQL Schemas Provide SDL, introspection JSON, or even a GraphQL endpoint URL. Oasify introspects or parses the schema and produces a REST-style OpenAPI 3 spec to help bridge GraphQL to traditional tooling.
WSDL Files Modernize legacy SOAP services: upload WSDL definitions and receive OpenAPI 3 representations, making integration with RESTful ecosystems straightforward.
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Plans and pricing as listed
1 listed- Requests
Refund terms
As stated by the publisher on AWS Marketplace.
WE REFUND: Billing errors. Failed conversions attributable to us. Material service incidents. NOT COVERED: Successful requests that produced outputs based on unsupported or malformed inputs. Charges from abuse or violation of our Terms. AWS infrastructure fees. Email oasify.team@gmail.com within 30 days with: Your AWS Account ID. The billing period and estimated number of affected requests. Any request IDs / timestamps / logs that help us validate.
Sources
Linked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.