I want to write a quick follow-up post about Algolia. Algolia is a powerful tool in my toolbox for vibe coding or rapidly iterating on ideas. Essentially, it’s a service where you give it a spreadsheet or information that you want to turn into a search engine, and it makes that data hyper-searchable.

Customer experience is undergoing a seismic shift, and Gladly is leading the charge with The Gladly Brief.

It’s a monthly breakdown of market insights, brand data, and investor-level analysis on how AI and CX are converging.

Learn why short-term cost plays are eroding lifetime value, and how Gladly’s approach is creating compounding returns for brands and investors alike.

Join the readership of founders, analysts, and operators tracking the next phase of CX innovation.

Subscribe here to stay informed and ahead of the curve.

Subscribe now

There are a couple of ways you can use it. You can interact with it via an API, which is highly code-heavy. But more importantly, you can vibe code with it, which means that with a couple of small pieces of information, you can tell an AI agent to go use an Algolia index or a search engine that you've already set up and embed it right into your application.

So that's what we're going to do. I'm just going to talk this through.

All right, so the first step is the grunt work. Just set up an Algolia account — it's free—and create an index; name it anything you want, like “my first search engine.” As soon as you do that, you can go to the settings and retrieve the application ID, which is an 8–12-character string.

You know the name of the index you just created, so you retrieve or copy the search API key. That search API key is just a key that lets people search so that you can embed it in a front-end application without any risk.

Okay, the next thing you're going to do is open Lovable, or even better, open Base44, and tell it you want to create a search engine, and that you already have the information it needs.

Paste in the app ID you got from Algolia, then tell it you're going to give it the index name, which is, again, the index you just created. And then the third thing is, tell it you're going to give it the search API key. It's essential to use those words.

Then paste in the string you got, tell it to create a simple search page for this index using that information, and let it know it will actually use Algolia.

Now, at this point, you've set the AI engine up to know that Algolia is a thing. By referencing its name, it knows it has an SDK set up and how to handle all the grunt work behind the scenes. So you've brought it up to speed and assigned it an application ID and a search key.

At this point, you should give it a prompt and tell it, “Hey, this is a list of all of the maybe Harry Potter characters and all of their friends and all the scenes they're in, and my search engine is going to do X, Y, or Z.” It's going to do something specific. Then you might want to tell it, “I want to show the photo URL, and I would like to have it return the name and the description,” and stop there — and let it build out a UI.

Now, what you've really done here is actually something that would be very challenging if you tried to do it the “traditional” way: set up a Mongo database, set up a full-text index, set up a connection string, set up an API so that it can talk to that connection string, and then wire it into your app.

The first thing you should remember is that Algolia is publicly accessible. It doesn’t have to sit behind an API. That means that for rapid iteration, you get the security — no one can change the data — but you also get the utility of being able to query it directly from the front end.

The second thing you might want to do is go into the Algolia index and open the configuration settings. You’ll have to dig a little bit. If you’ve uploaded, say, a spreadsheet, you might choose some characteristics and click on the facet option to add a facet. A facet is just, “Hey, this is something that I want to search or filter on beyond a text index.”

Then go back to your vibe-coding application and tell it, “Hey, there is a facet called X, and X has a list of all of the hair colors of the characters in Harry Potter. I want to be able to do a full-text search, but I’d also like to have a set of checkboxes below it with all the different hair colors that are available in that search.”

Go ahead and tell the AI to do this. Then play around. You’re going to be surprised how fast this is and how quickly you can start to adapt this pattern for other uses.

Here is a working example that I vibe-coded:

So, why is this important?

As soon as you get a firm understanding that you can take data and make it hyper-searchable — and when I talk about hyper-searchable, I mean you can tell an AI to change it, and it will do things in the UI that would have actually been a day, a week, or a month's worth of work — it changes how you think about building.

If you're starting to iterate on ideas and want to define the first step, you don't need much code. You need a tool that integrates well with Vibe-Coding. And Algolia is one of these surprising hidden gems where you can vibe code and deliver absolutely amazing user experiences.

Because it's designed to be used this way, you're not breaking any rules, you're not creating a cybersecurity issue — you're, in some ways, just using the tool as expected, but in ways that only experts typically use it.