Typesense through Squiid

What Typesense is

Typesense is an open-source alternative to hosted search engines, designed to be simple to run and fast by default. It does typo-tolerant instant search, faceting, filtering, geosearch, curation and synonyms, and it also stores vectors so semantic and hybrid search work from the same collection. Typesense Cloud runs it as a managed cluster priced per hour by node size rather than per search request, which makes a high-traffic search box cost the same as a quiet one. Schemas are explicit, with field types and which attributes are searchable, sortable or facetable declared up front.

That pricing shape is the practical reason it shows up in AI-coded projects. A search feature whose cost scales with every keystroke is uncomfortable to ship when you do not know how many users you will have, and a fixed hourly cluster removes that worry. Having vector search in the same engine also avoids running a second database just to add semantic matching to an existing catalog. Clusters can be scaled by changing node size, and high availability is a configuration option rather than a redesign.

Why connect it through Squiid

Typesense is on the Squiid roadmap. When it is connected, Squiid will provision the cluster, hold the admin and search-only API keys, and route requests through https://api.squiid.io/v1/typesense/... with Authorization: Bearer $SQUIID_API_KEY, with the official clients working by base URL swap (gateway convention). Cluster cost will pass through at Typesense's listed price on your single Squiid invoice, so search sits on the same bill as the database it indexes and the hosting it serves from.

• One account, one key, one bill, one dashboard. Typesense sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Typesense credentials. Your code carries SQUIID_API_KEY, so TYPESENSE_HOST, TYPESENSE_API_KEY, TYPESENSE_SEARCH_ONLY_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 Typesense 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 Typesense cluster
• Instant search with typo tolerance and faceting
• Vector and hybrid search in the same collection
• Predictable per-hour cluster pricing
• Typesense list pricing, no markup

How to connect Typesense

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 TYPESENSE_HOST, TYPESENSE_API_KEY, TYPESENSE_SEARCH_ONLY_KEY
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Typesense Cloud charges per hour for the cluster configuration you select rather than per search, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Typesense usage, with no markup and no per-request margin.

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

Typesense 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 Typesense 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.