Your chatbot now reads OpenAPI specs directly

Your chatbot gets smarter with structured API data, plus conversations finally persist when users navigate your site.

Here's what shipped in September:

OpenAPI integration

Add OpenAPI documents directly as a data source instead of crawling your API docs.

Why this matters:

Complete coverage: Every endpoint, parameter, and schema gets indexed automatically
Better accuracy: Schema definitions and data types are fully captured
No missing content: Unlike web crawling, nothing gets lost

Add OpenAPI documents in project settings under Sources > OpenAPI. Paste the URL and we handle the rest.

Conversations now persist across page navigation.

The problem: Someone asks a question, gets a helpful response with a link, clicks that link, and loses the entire conversation context. Frustrating.

Now conversations are cached as users navigate. Click a link from the chat? Context stays. Refresh the page? History remains intact.

Makes the chatbot feel like part of your documentation rather than a separate tool that resets constantly.

Both the search widget and chatbot widget now open in full-screen mode on mobile devices.

When someone taps the chatbot on their phone, it takes over the entire screen, giving them the space they need for a proper conversation.

Same experience, optimized for thumbs instead of cursors.

If the updates help your team, consider leaving a G2 review. It helps others evaluate the platform and guides our roadmap.

Questions about these features? Email support@biel.ai.