Algolia through Squiid

Hosted search with typo tolerance, ranking rules and instant UI kits. Algolia is on the Squiid roadmap.

Roadmap Provisioned Provisioned. Squiid creates the project or account for you and keeps the provider keys.

What Algolia is

Algolia is a hosted search engine aimed at end-user search rather than machine retrieval. Records are indexed with searchable attributes and custom ranking, and queries return in a few milliseconds with typo tolerance, prefix matching, faceting, synonyms and merchandising rules applied. InstantSearch provides ready-made components for React, Vue and vanilla JavaScript so a full search interface with filters and pagination is mostly configuration, and search analytics show what people typed and what returned nothing. Distributed search clusters put the index near your users, and A/B testing lets you compare two ranking configurations on real traffic.

In a vibe-coded product this is the search box customers actually use: a product catalog, a documentation site, a directory, a help center. It is worth separating from vector search, because a shopper typing a misspelled brand name wants keyword behaviour with business rules, not semantic similarity. Algolia also supports AI-driven ranking and neural search features for teams that want both behaviours in one index. Analytics on zero-result queries are the fastest way to find out what your catalog is missing, which is information a vector index will not give you.

Why connect it through Squiid

Algolia is on the Squiid roadmap. When it lands, Squiid will provision the application, hold the admin and search keys, and route requests through https://api.squiid.io/v1/algolia/... with Authorization: Bearer $SQUIID_API_KEY, with the official clients working by base URL swap (gateway convention). Search requests and indexed records will meter against prepaid credits at Algolia's listed price on one invoice. Key handling matters here: Algolia issues an admin key that can delete an index and a search-only key for the browser, and getting those two mixed up is a common and expensive mistake that provisioning removes.

  • One account, one key, one bill, one dashboard. Algolia sits beside every other service your project uses, on the same invoice and the same credit balance.
  • Key custody. Squiid holds the Algolia credentials. Your code carries SQUIID_API_KEY, so ALGOLIA_APP_ID, ALGOLIA_ADMIN_API_KEY, ALGOLIA_SEARCH_API_KEY, ALGOLIA_INDEX_NAME never land in a repository, a preview deployment or an agent’s context.
  • Metering you can see. Every call is counted per service and per day, so you know what Algolia costs before the month ends.
  • Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
  • One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

  • A provisioned Algolia application
  • Typo tolerance, faceting, synonyms and ranking rules
  • InstantSearch UI components for the front end
  • Admin and search keys held by Squiid
  • Algolia list pricing, no markup

How to connect Algolia

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces ALGOLIA_APP_ID, ALGOLIA_ADMIN_API_KEY, ALGOLIA_SEARCH_API_KEY, ALGOLIA_INDEX_NAME
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/algolia/...
# header:       Authorization: Bearer $SQUIID_API_KEY
01

Add it in your dashboard

Open the Squiid catalog, add Algolia and fund credits. Squiid provisions the project and keeps the provider keys.

02

Put the one key in your env

Add SQUIID_API_KEY to .env and delete ALGOLIA_APP_ID, ALGOLIA_ADMIN_API_KEY, ALGOLIA_SEARCH_API_KEY, ALGOLIA_INDEX_NAME. Nothing else from Algolia needs to exist in your project.

03

Point your agent at it

Claude Code, Cursor and Codex read the same variable and call https://api.squiid.io/v1/algolia/. Agents index records from your database into Algolia on write, then render InstantSearch components against a search-only key.

Pricing through Squiid

Algolia charges per search request and per indexed record above the free allowance, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Algolia usage, with no markup and no per-request margin.

Algolia is used on the pay as you go basis, so there is no fixed monthly plan cost to pass through. You pay for what you use at the provider’s listed price.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Algolia usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: records, vectors and index settings are exported and re-imported into an index in your own Algolia account. Squiid never owns your code, your schema or your domain, and the gateway speaks Algolia's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Algolia through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

Vibe coding a feature on Algolia usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.

Related services

Questions people ask

Is Algolia available on Squiid yet?

Not yet. It is on the roadmap as a provisioned service with the keys held by Squiid.

Do I still need a search-only key for the browser?

Front-end search needs a restricted key. Squiid provisions and scopes it so the admin key never leaves the gateway.

Algolia or a vector database?

Algolia is for people typing into a search box, with typos and business rules. A vector database is for semantic retrieval feeding a model. Many apps use both.

How will Squiid bill Algolia?

Search requests and indexed records at Algolia's listed price, drawn from prepaid credits with no markup.

Can an agent keep the index in sync?

Yes. The usual pattern is to push changes on database writes, which an agent can wire as part of the same mutation.

Connect Algolia with one key.

Algolia powers search-as-you-type with typo tolerance, custom ranking, faceting, synonyms and analytics, plus front-end libraries that render the UI. Planned for Squiid as a provisioned service.