Beyond the Chatbot: What You Can Build With the CrafterQ API

When we launched CrafterQ, the idea was simple: make it easy for any business to add an AI chatbot to its website.

Train Q on your website, documents, and business knowledge. Customize it for your brand. Add it to your site. Within minutes, visitors can ask questions, find information, get support, discover products, and engage with your business conversationally.

That remains one of the easiest and most powerful ways to use CrafterQ.

But with the release of the CrafterQ Public API, the chatbot is no longer the only way to use the intelligence behind Q. Developers can now build their own experiences on top of the CrafterQ platform.

Put another way: you don't have to use the CrafterQ chatbot. You can use the CrafterQ intelligence.

That opens up an entirely new set of possibilities.

From AI Chatbot to Conversational AI Platform

There are now three broad ways to use CrafterQ.

The first is the familiar one: an AI chatbot for your website. Businesses can train an agent, customize it, and deploy CrafterQ directly on their website without writing code.

The second is as a conversational AI platform for developers. Developers can use the CrafterQ API to build completely custom AI experiences for websites, applications, mobile apps, customer portals, and other digital experiences.

The third is as embedded AI agent infrastructure. Software companies, digital agencies, and developers can use CrafterQ as the AI backend behind products and experiences they design, build, and brand themselves.

In that sense, the standard CrafterQ chatbot is now effectively one client of a much larger platform.

So what else can you build?

Quite a lot.

1. Build a Completely Custom Website AI Chatbot

The most obvious use case is replacing the standard CrafterQ user interface with your own.

An organization may want the intelligence and knowledge capabilities of CrafterQ while having very specific requirements for its website experience, design system, or brand. With the API, developers control that experience. They can determine where conversations appear, how messages are rendered, how users initiate conversations, how responses interact with other interface elements, and how AI fits into the overall website experience.

CrafterQ remains responsible for the conversational intelligence behind that experience.

This can be especially valuable for enterprises with established digital design systems and agencies building highly customized websites for their clients. Instead of adapting the website to the AI interface, they can adapt the AI interface to the website.

2. Embed Conversational AI Directly Into the Website Experience

A conversational experience doesn't have to look like a chatbot at all.

Consider an ecommerce product page that simply asks a shopper, "Need help choosing?" The resulting conversation could happen directly within the product page rather than inside a separate chat window.

A healthcare website might offer an interactive experience that helps a visitor understand what type of authorization they need. A university might help a prospective student find the right program. A financial services website could help someone understand which account best fits their needs. A SaaS website could start by asking a prospect what they're trying to accomplish and then guide them toward the most relevant capabilities.

The interface can be designed specifically around the task.

This represents a larger shift in how we think about conversational AI. Instead of adding a chatbot on top of an existing digital experience, conversation can become part of the experience itself.

3. Create Conversational Site Search

Traditional website search expects visitors to translate what they want into keywords. Conversational search reverses that relationship.

Instead of constructing a search such as "international shipping return policy," a visitor can simply ask, "Can I return something I ordered internationally, and who pays for shipping?"

More importantly, the visitor can continue the conversation. They might follow up by asking whether the policy changes if the product has already been opened, and then ask how to start the return. The context carries forward naturally from one question to the next.

Developers can use CrafterQ to create AI-powered search experiences that let visitors explore a website's information conversationally instead of repeatedly guessing which keywords will produce the right result.

For content-rich websites, documentation sites, support portals, and large corporate sites, that can fundamentally change how users discover information.

4. Build AI Product Advisors

Ecommerce creates an especially interesting opportunity.

Imagine visiting an outdoor retailer and saying, "I need a shell for skiing in Utah. I run warm, don't want insulation, and would like to spend less than $500."

A traditional ecommerce experience requires the shopper to translate those requirements into categories, filters, specifications, and product comparisons. A conversational product advisor can understand the requirements as expressed naturally and help narrow the choices.

The ecommerce application could then present actual product cards, specifications, pricing, availability, images, and purchasing options using the retailer's existing user interface.

That's an important distinction. CrafterQ doesn't need to render the entire experience. It can provide the conversational intelligence while the ecommerce application controls the visual and transactional experience.

Combined with commerce integrations and CrafterQ Actions, this creates the foundation for AI shopping assistants that can do much more than answer FAQs. They can help shoppers move from a vaguely expressed need toward an actual purchasing decision.

5. Put Q Inside a SaaS Application

For software companies, some of the most useful product documentation often sits outside the application where customers actually need it.

The CrafterQ API makes it possible to put the assistant directly inside the product.

A user working in a SaaS dashboard might ask how to configure SSO, why another user can't access a project, where a particular setting is located, or what the difference is between two configuration options. Instead of leaving the application, opening the documentation, searching for an answer, and then returning to the task, the user can get assistance in context.

The software vendor controls the application experience while CrafterQ provides the conversational intelligence behind it.

In this scenario, Q isn't really a website chatbot anymore. It becomes an in-product AI assistant.

6. Add AI to Customer and Partner Portals

The same model applies to authenticated customer, employee, and partner experiences.

Organizations often have enormous amounts of documentation, policies, procedures, product information, and support content scattered across portals and knowledge bases. Finding the right information can be difficult even when the answer technically exists somewhere.

A conversational assistant can provide a much simpler front end to that information.

Customers could ask questions about products and support procedures. Partners could navigate program documentation and technical materials. Employees could find policies and internal resources without knowing which section of a portal contains the answer.

Rather than building the underlying conversational AI infrastructure from scratch, development teams can use CrafterQ as the intelligence layer while integrating the experience into the portals they already operate.

7. Bring the Same Agent Into a Mobile App

Your AI experience doesn't have to stop at the website.

Developers can integrate CrafterQ into mobile applications and create native conversational experiences appropriate for iOS, Android, or other application environments.

That becomes particularly interesting for organizations operating across multiple digital channels. The same underlying Q agent can potentially power a website experience, mobile application, customer portal, and product interface.

Instead of building and maintaining separate AI systems for each channel, the organization can maintain a common knowledge and conversational layer while creating interfaces appropriate for each experience.

The channel changes. The underlying intelligence doesn't have to.

8. Build Persistent AI Assistants

Most website chatbots are treated as temporary conversations. A visitor arrives, asks a few questions, leaves, and starts over on the next visit.

But many customer experiences don't actually work that way.

A customer might first have a conversation about selecting a product. Later, they may need help installing it. Several weeks after that, they might return with a troubleshooting question or ask about the warranty.

Developers can use CrafterQ's conversation capabilities to create interfaces where users can return to previous conversations and continue them. An application might organize those conversations around topics such as product selection, installation, warranty information, and troubleshooting.

Instead of every interaction beginning from zero, conversation can become part of an ongoing customer relationship.

9. Create Conversational Landing Pages

Landing pages have followed roughly the same formula for years: headline, benefits, features, testimonials, form, and call to action.

Conversational AI creates another possibility.

A visitor could arrive on a landing page and immediately be invited to explain what they're trying to accomplish. From there, the experience can adapt to the conversation.

A visitor evaluating the product might ask detailed technical questions. Someone further along in the buying process might want to discuss pricing or implementation requirements. A prospect with a particular business problem can describe it in their own words instead of figuring out which predefined marketing path applies to them.

CrafterQ Actions can then move the experience naturally from conversation into lead capture, escalation, or another business process.

Instead of forcing every visitor through the same static funnel, developers can build a conversational funnel that responds to the visitor's actual intent.

10. Build White-Label AI Experiences for Agencies

Digital agencies and development firms represent another important use case.

An agency can build its own conversational interface and use CrafterQ underneath it. The agency owns the design, branding, implementation, and customer relationship while CrafterQ provides the underlying AI infrastructure.

An agency could even develop a reusable conversational component and deploy customized versions across multiple client websites.

Building production-grade conversational AI involves considerably more than connecting a user interface to an LLM. There is knowledge ingestion, retrieval, conversation management, model integration, streaming, configuration, feedback, actions, security, and ongoing infrastructure to consider.

Using CrafterQ as the underlying platform lets agencies focus on the differentiated customer experience rather than rebuilding that infrastructure for every project.

That makes CrafterQ useful not only as an application, but as a building block for other digital solutions.

11. Embed AI Into Another Software Product

The same idea extends beyond agencies.

Software companies can use CrafterQ to add conversational AI capabilities to their own products while keeping their own product experience front and center.

Building a production AI assistant involves much more than sending prompts to an LLM. Applications need ways to ingest and manage knowledge, retrieve relevant information, maintain conversations, stream responses, collect feedback, invoke actions, configure agent behavior, and manage the surrounding infrastructure.

CrafterQ can provide that layer.

The software company builds the experience its customers see. CrafterQ operates behind it.

In that model, CrafterQ becomes embedded AI agent infrastructure. For many software companies, that can be considerably faster than building, operating, and continuously improving an entire conversational AI stack themselves.

12. Create Interactive Kiosks and Digital Experiences

Not every digital experience lives on a traditional website.

Retail kiosks, trade-show displays, showroom systems, tablets, information terminals, and other interactive experiences can also benefit from conversational AI.

A visitor at a trade show might ask detailed questions about a company's products. A shopper at a retail kiosk could describe what they're looking for instead of navigating through a complicated category structure. A visitor using an information terminal could simply ask a question rather than work through layers of menus.

In each case, the interface can be designed specifically for the environment while CrafterQ handles the conversational intelligence behind it.

13. Add Voice Experiences

The CrafterQ API is conversational rather than voice-specific, but that means it can also serve as the intelligence layer behind a voice interface.

Developers can combine speech recognition, CrafterQ, and text-to-speech technologies to create experiences where users talk to an agent rather than type to it.

That could be useful in mobile applications, kiosks, accessibility experiences, hands-free environments, and other situations where speaking is more natural than using a keyboard.

Once again, the interface changes. The underlying intelligence doesn't have to.

One Agent, Many Experiences

That's ultimately the bigger idea behind the CrafterQ Public API.

For the first generation of website AI, the chatbot and the AI behind it were effectively treated as the same product. We're separating those concepts.

The agent contains the knowledge, instructions, conversational intelligence, and capabilities. The client determines how people experience that intelligence.

That client might be the standard CrafterQ chatbot. Or it might be a custom website interface, ecommerce product advisor, mobile application, SaaS assistant, customer portal, conversational search experience, landing page, kiosk, voice interface, or an entirely new experience we haven't thought of yet.

One CrafterQ agent can become the intelligence behind many different digital experiences.

And that distinction becomes increasingly important as AI moves beyond the chatbot window and becomes a native part of websites, applications, commerce experiences, and digital products.

The Chatbot Is Just the Beginning

Every website needs an AI chatbot.

For many businesses, it is exactly the right interface. It's familiar, easy to deploy, requires little or no development work, and gives visitors an immediate way to engage with a website conversationally.

But conversation is increasingly becoming part of the broader digital experience.

Developers shouldn't have to squeeze every AI use case into a floating chat window. They should be able to decide where AI belongs, how users interact with it, and how it fits into the products and experiences they're already building.

With the CrafterQ Public API, they can.

You don't have to use the CrafterQ chatbot. You can use the CrafterQ intelligence.

The chatbot was the starting point. We're excited to see what developers build next.

Start Building Today

Learn how to build conversational AI experiences with CrafterQ's developer API here.