What authentication does the Swagger2OpenAPI Converter use?

The hosted service does not declare a security scheme; the documented endpoints are publicly callable. Through Jentic, calls are still routed through the gateway so tenants get logging and request shaping even when the upstream is unauthenticated.

Can I send the Swagger spec directly in the body instead of by URL?

Yes. POST /convert accepts the Swagger 2.0 definition in the request body and POST /validate accepts an OpenAPI 3.0.x definition the same way, which is useful when the spec is not yet published at a public URL.

What are the rate limits for the Swagger2OpenAPI Converter?

The OpenAPI spec does not declare rate limits. The hosted service is community-run on a single host, so high-volume callers should self-throttle and prefer the npm package swagger2openapi for batch jobs rather than calling the API in a tight loop.

How do I convert a Swagger 2.0 spec through Jentic?

Install the SDK with pip install jentic, search for 'convert Swagger 2.0 to OpenAPI 3.0', load the POST /convert operation, and execute it with the Swagger JSON in the body. Jentic returns the converted OpenAPI 3.0.x payload.

Does the converter return validation errors when the input is broken?

Yes. POST /validate returns a structured error response listing the schema violations found, so callers can use it to gate CI pipelines or fail a publish step when the underlying spec is invalid.

Can I limit what my agent is allowed to do with the Swagger2OpenAPI Converter API?

Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call, so you can allow only the conversion and validation endpoints it actually needs. For a spec-cleaning agent you might permit POST /convert and POST /validate while leaving out the GET /status and GET /badge endpoints entirely. Since the converter takes the spec in the request body rather than as a keyed resource, this operation-level scoping is how you keep the agent inside its intended job.