pinecone-ts-client

The official TypeScript/Node client for the Pinecone vector database

Runssource: GitHubhomepageTypeScriptApache-2.0commit fca1f72ba40a

TypeScript, Apache-2.0 licensed. The project labels itself: llm, pinecone, semantic search, similarity search and vector database.

pinecone-ts-client runs. An Argusic agent installed it in 2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

SDK installs, builds, and passes all 1460 unit tests and 48 mocked smoke tests on Node 22.14.0. The dist/ folder contains 30 files with all expected exports (Pinecone, Index, Documents, Assistants, Inference, etc.). No errors remain.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
278
forks
50
open issues
21
watchers
22
size
4 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
2 minutes
Cold machine to finish
3 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
npm test:unit passed with 1460/1460 passing in 22.5s; npm test:smoke:mocked passed with 48/48 passing in 14.3s; npm run build exited 0 producing dist/; npm run typecheck passed with both tsconfigs
Model tokens used
69,168
Exact commit tested
fca1f72ba40a
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Exported names: Pinecone, Index, Documents, Indexes, Collections, Backups, RestoreJobs, BackupSched…
exec
/bin/sh -lc 'export PATH="/home/runner/.local/node22/bin:$PATH" && cd /work/repo && npm run typeche…
 succeeded in 8803ms:
> @pinecone-database/[email protected] typecheck
> tsc --noEmit && tsc -p tsconfig.tools.json
All verified. Here's the final results:
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":2.0,"errors…
tokens used
69,168
All verified. Here's the final results:
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":2.0,"errors…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 2 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 2 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

llmpineconesemantic-searchsimilarity-searchvector-database

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/pinecone-ts-client.svg)](https://argusic.com/subject/pinecone-ts-client)

Questions

Does pinecone-ts-client run?
Yes. pinecone-ts-client runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test pinecone-ts-client?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit fca1f72ba40a. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test pinecone-ts-client?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does pinecone-ts-client take to install?
2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does pinecone-ts-client need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing pinecone-ts-client?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for pinecone-ts-client?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion