LanceDB vs Pinecone API + MCP

LanceDB

Embedded, no server, and tables can live directly in S3, GCS or Azure storage. No self-serve hosted API. Enterprise is sold through a contact form.

Pinecone API + MCP

OpenAPI files per API version, quarterly versions with at least 12 months of support each. Nine regional incidents between 9 July and 28 September 2026, four lasting more than an hour.

LanceDB

1. Use it through the Python or TypeScript library. There's no public endpoint an agent can call without an Enterprise deployment
2. Build an FTS index before calling query_type="hybrid", or hybrid search has no keyword side
3. Call optimize() after many small writes, since each write adds a new file version
4. Use select() to drop the vector column from results unless the task needs it
5. On object storage, set a read consistency interval if several processes write the same table

Pinecone API + MCP

1. Send X-Pinecone-Api-Version: 2026-07 on every call. Without it you get the oldest supported version
2. Queries go to the index host from describe_index, not to api.pinecone.io
3. Wait a few seconds and retry when fresh upserts don't show up in search
4. Back off exponentially on 429. There's no Retry-After header
5. Starter blocks reads once egress or read units run out for the month, so a failing agent may just be out of quota