Meilisearch through Squiid

What Meilisearch is

Meilisearch is a search engine that aims to be usable without a search specialist. Indexing a JSON array gives you typo-tolerant instant search immediately, and ranking rules, filters, facets, synonyms and stop words are adjusted through a simple settings object rather than a query language. Recent versions add AI-powered hybrid search that combines keyword matching with embeddings, with the embedder configured per index, and tenant tokens restrict what a given user can see. Indexing is asynchronous with a task queue you can poll, so a bulk import does not block reads on the existing index.

For agent-built projects the low configuration cost is the point. An agent can index a collection, wire a search route and produce a working results page in one pass, and the defaults are good enough that nobody has to tune relevance before launch. Tenant tokens matter for multi-user apps, because they let the front end search directly while the engine enforces which documents that user is allowed to match. Because the engine is open source, the same version runs in a local container during development, which keeps generated tests meaningful.

Why connect it through Squiid

Meilisearch Cloud is on the Squiid roadmap. When it lands, Squiid will provision the instance, hold the master and admin keys, and route requests through https://api.squiid.io/v1/meilisearch/... with Authorization: Bearer $SQUIID_API_KEY, with official clients working by base URL swap (gateway convention). Instance cost will pass through at Meilisearch's listed price on your single Squiid invoice with no markup, and the master key, which can do anything to any index, stays out of your repository entirely.

• One account, one key, one bill, one dashboard. Meilisearch sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Meilisearch credentials. Your code carries SQUIID_API_KEY, so MEILISEARCH_HOST, MEILI_MASTER_KEY, MEILISEARCH_API_KEY 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 Meilisearch 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 Meilisearch Cloud instance
• Typo tolerance and faceting with minimal configuration
• Hybrid AI search with a configurable embedder
• Tenant tokens for per-user result scoping
• Meilisearch list pricing, no markup

How to connect Meilisearch

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 MEILISEARCH_HOST, MEILI_MASTER_KEY, MEILISEARCH_API_KEY
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Meilisearch Cloud charges per month by instance size and included document volume, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Meilisearch usage, with no markup and no per-request margin.

Meilisearch has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

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 Meilisearch 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 Meilisearch account. Squiid never owns your code, your schema or your domain, and the gateway speaks Meilisearch'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

Meilisearch 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:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Meilisearch 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.