Jina through Squiid

What Jina is

Jina AI publishes a small set of retrieval building blocks. Reader takes a URL and returns clean text suitable for a prompt, with a variant that reads search results. Jina Embeddings covers multilingual and long-document embedding, including a late-chunking approach that keeps context across chunk boundaries, and the reranker scores retrieved passages against a query. A segmenter for chunking and classifiers round it out. Most endpoints are callable with a plain HTTP request, which makes them easy to drop into an existing pipeline without an SDK.

For an AI-coded app the appeal is that one vendor covers the whole retrieval chain: fetch the page, split it, embed it, retrieve, rerank. That reduces the number of providers a RAG feature depends on, which matters when an agent is assembling the pipeline and every extra service is another key, another SDK and another way for the build to fail. Late chunking in particular helps with long documents, where a naive split loses the context that made a passage meaningful.

Why connect it through Squiid

Jina is on the Squiid roadmap. When it lands, requests will go to https://api.squiid.io/v1/jina/... with Authorization: Bearer $SQUIID_API_KEY, with clients working by base URL swap (gateway convention), and tokens across reader, embedding and reranker calls will meter against prepaid credits at Jina's listed price on one invoice. Squiid will hold the key, so a retrieval pipeline spread across several workers and functions shares one rotatable credential. Keeping the whole chain with one vendor also makes cost attribution simpler, because every stage appears under one service.

• One account, one key, one bill, one dashboard. Jina sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Jina credentials. Your code carries SQUIID_API_KEY, so JINA_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 Jina 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

• Reader that converts URLs to clean text
• Multilingual and long-document embeddings
• Reranking for retrieval quality
• Segmenter and classifier endpoints
• Jina list pricing, no markup

How to connect Jina

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 JINA_API_KEY
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Jina charges tokens from a prepaid balance across reader, embedding and reranker endpoints, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Jina usage, with no markup and no per-request margin.

Jina 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 Jina 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

Nothing to move: Jina is usage-metered, so leaving means creating your own Jina key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks Jina'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

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