reactivesearch-api

API Gateway for Elasticsearch with declarative querying and out-of-the-box access controls

Runs with mockssource: GitHubhomepageGoApache-2.0commit 8d9acac8b4c0

Go, Apache-2.0 licensed. The project labels itself: api gateway, elasticsearch, elasticsearch api, elasticsearch plugin, hacktoberfest and reactivesearch.

reactivesearch-api runs, with stand-ins for the services it depends on. An Argusic agent installed it in 16 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

ReactiveSearch API v9.4.0 compiled from source with Go 1.27.3, binary built successfully at build/reactivesearch (96MB ELF), server starts and responds to HTTP on port 8004 with proper JSON error responses. 5 plugin test suites pass (pipelines, openai, storedquery, model/reindex, telemetry, util).

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

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.44 (measured)
recorded runs
1
last tested
stars
212
forks
30
open issues
12
watchers
9
size
6 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 reactivesearch-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.

  • Pipeline plugin requires Elasticsearch; server fails without ES_CLUSTER_URL3 minutes
  • Go (Golang) not pre-installed in the container2 minutes
  • Initial build with Tier=test failed - 'invalid plan encountered: test'1 minute
  • Rules plugin test (TestRunScript) has a pre-existing test failure unrelated to install
Install time
16 minutes
Cold machine to finish
17 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
curl -s http://localhost:8004/ returned 401 JSON response - server accepting connections and routing requests
Model tokens used
189,208
Exact commit tested
8d9acac8b4c0
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
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

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

 exited 143 in 5983ms:
=> port used 8000
2026/10/30 19:21:03 Initializing request logs map
VERIFICATION:
{"error":{"code":401,"message":"Basic Auth or JWT is required","status":"Unauthorized"}}
{"error":{"code":401,"message":"Basic Auth or JWT is required","status":"Unauthorized"}}
The server is verified to start and respond to HTTP requests correctly (it returns proper JSON 401 …
Let me compile my final report:
tokens used
189,208
The server is verified to start and respond to HTTP requests correctly (it returns proper JSON 401 …
Let me compile my final report:

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

  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 16 minutes to install, slower than the median of the 31 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 32 api-gateway projects Argusic has installed and timed, reactivesearch-api was the 25th fastest to reach a running state, and 22 of 32 reached one at all.

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/3Runs with mocks92.000.44

Topics (from GitHub)

api-gatewayelasticsearchelasticsearch-apielasticsearch-pluginhacktoberfestreactivesearch

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/reactivesearch-api.svg)](https://argusic.com/subject/reactivesearch-api)

Questions

Does reactivesearch-api run?
reactivesearch-api runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 16 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test reactivesearch-api?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8d9acac8b4c0. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test reactivesearch-api?
The run that produced this verdict cost $0.44: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does reactivesearch-api take to install?
16 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 reactivesearch-api need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing reactivesearch-api?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does reactivesearch-api compare with the alternatives?
Of the 32 api-gateway projects Argusic has installed and timed, reactivesearch-api was the 25th fastest to reach a running state, and 22 of 32 reached one at all.
Where is the evidence for reactivesearch-api?
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