rag-api

ID-based RAG FastAPI: Integration with Langchain and PostgreSQL/pgvector

Runssource: GitHubhomepagePythonMITcommit c4e5cbf79fce

Python, MIT licensed. The project labels itself: api, api rest, embeddings, fastapi, langchain, pgvector, postgresql and psql.

rag-api runs. An Argusic agent installed it in 3.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Dependencies installed in venv, all 303 non-integration tests pass after adding OPENAI_API_KEY mock to conftest.py; 6 tests skip due to missing pandoc, 35 integration tests require Docker

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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
2
last tested
stars
928
forks
418
open issues
56
watchers
8
size
30 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.

Time lost to each failure while testing rag-api, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • OpenAI API key required at import time in app/config.py line 368; tests failed to collect0.5 minutes
  • pandoc not installed (6 tests skipped in test_lazy_load.py)
Install time
4 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
pytest exited 0, 303 passed, 6 skipped, 35 deselected
Model tokens used
49,309
Exact commit tested
c4e5cbf79fce
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.

 succeeded in 0ms:
os.environ["TESTING"] = "1"; os.environ["OPENAI_API_KEY"] = "test-key"
# Set DB_HOST (and DSN) to dummy values to avoid real connection attempts.
os.environ["DB_HOST"] = "localhost"  # or any dummy value
os.environ["DSN"] = "dummy://"
# -- Patch the vector store classes to bypass DB connection --
All 303 tests pass, 6 skipped (all due to `pandoc` not being installed — not a repo code issue). Th…
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 3.5, "…
tokens used
49,309
All 303 tests pass, 6 skipped (all due to `pandoc` not being installed — not a repo code issue). Th…
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 3.5, "…

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.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 3.5 minutes to install, slower than the median of the 61 comparable projects Argusic has measured.

Of the 62 api projects Argusic has installed and timed, rag-api was the 32nd fastest to reach a running state, and 39 of 62 reached one at all.

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 3.5 minutes after the clone.

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 Runner2/3Runs with mocks92.000.06
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

apiapi-restembeddingsfastapilangchainpgvectorpostgresqlpsqlpythonragvectorvector-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/rag-api.svg)](https://argusic.com/subject/rag-api)

Questions

Does rag-api run?
Yes. rag-api runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test rag-api?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit c4e5cbf79fce. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test rag-api?
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 rag-api take to install?
3.5 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 rag-api need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing rag-api?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does rag-api compare with the alternatives?
Of the 62 api projects Argusic has installed and timed, rag-api was the 32nd fastest to reach a running state, and 39 of 62 reached one at all.
Where is the evidence for rag-api?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion