What is OpenAPI Specs?
OpenAPI Specifications (formerly Swagger) are machine-readable descriptions of REST APIs in JSON or YAML format. They describe every endpoint, request body, response schema, authentication method, and error code in a single document. Kelu parses and indexes your spec so that natural-language questions like 'how do I paginate the /orders endpoint?' return precise, cited answers drawn from your actual spec.
How Kelu works with OpenAPI Specs
Everything you can do once the integration is connected.
Spec URL
Add your OpenAPI spec as a source URL (JSON or YAML, publicly accessible, up to 16 MB). Kelu re-fetches it every hour and re-indexes what changed.
Operation-level chunking
Each API operation (path + method) is chunked individually so retrieval is precise. Asking about POST /orders returns only the orders creation operation — not unrelated endpoints.
Parameter and schema awareness
Request parameters, body schemas, response shapes, and enum values are all indexed. Users can ask 'what fields are required for the checkout body?' and get an exact answer from the spec.
Multi-spec support
Add multiple OpenAPI specs to a single knowledge base — for example your public API and an internal admin API. Kelu retrieves across all specs and cites the source spec and operation in every answer.
How to set it up
- 1
In the Kelu dashboard, create or open a knowledge base and add an OpenAPI Spec source. Enter your public spec URL (https://api.example.com/openapi.json).
- 2
Kelu parses and chunks the spec by operation. The first index completes in under a minute for most specs.
- 3
Kelu re-fetches the spec every hour; click Sync Now right after you publish a new version. Embed the chat widget or connect the MCP server for your developer audience.
Related integrations
Notion
Connect Notion pages, databases, and wikis so your team can ask questions and get AI answers with citations from your internal knowledge.
View details
Confluence
Index Confluence Cloud spaces and let your team ask questions with answers grounded in your own wiki content.
View details
Google Drive
Connect Google Drive to index Google Docs, Sheets, Slides, PDFs, Office files, and folder collections into your Kelu knowledge base.
View detailsGot questions?
OpenAPI Specs — Frequently Asked Questions
Common questions about connecting Kelu to OpenAPI Specs.
Kelu supports OpenAPI 3.0, OpenAPI 3.1, and Swagger 2.0 specs in both JSON and YAML format. The spec must be at a publicly accessible URL, up to 16 MB.
Yes. Add each spec as a separate source within the same knowledge base. Kelu retrieves across all specs and cites the source spec name and operation ID in every answer.
Kelu re-fetches the spec every hour. Click Sync Now right after you publish a new version. Only changed content is re-embedded, keeping costs low.
Not by tag or path: the source's only setting is the spec URL. To keep an endpoint out, click Remove from the index on its document in the source's Documents tab, and later syncs skip it. Or publish a spec without your internal or deprecated endpoints.
Yes. Kelu indexes example values defined in the spec's `example` and `examples` fields and includes them in retrieved chunks. Answers can show example request bodies, response payloads, and code samples when present in the spec.