free-ai-tools
Curated list of free and low cost AI tools, LLM APIs, IDEs, agents, and infrastructure for building real AI apps
Runssource: GitHubhomepageTypeScriptMITcommit 8f802d7a76e4
TypeScript, MIT licensed. The project labels itself: ai, ai agents, ai directory, ai tools, ai tools directory, ai tools list, ai top tools and awesome.
free-ai-tools runs. An Argusic agent installed it in 4 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Next.js website at /work/repo/website builds and serves all pages with HTTP 200, no errors.
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.7 of 100 (the mean of this project's run scores).
At a glance
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.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18.19.1 too old (Next.js 16 requires >=20.9.0)1 minute
- Missing @tailwindcss/oxide native binding for linux-x64-gnu1 minute
- Install time
- 4 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- next build compiled successfully; npm run build exited 0; next start -p 3458 served all 8 routes (/, /categories, /stacks, /search, /news, /submit, /privacy, /terms) plus /api and /api/news returning HTTP 200 each
- Model tokens used
- 41,199
- Exact commit tested
- 8f802d7a76e4
- 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.
{"news":[]}
Everything works. Let me kill any leftover processes and compile my report:
exec
/bin/sh -lc 'pkill -f "next start" 2>/dev/null; echo "cleaned up"' in /work/repo
exited 143 in 0ms:
Let me calculate the total time:
exec
/bin/sh -lc 'echo "Total elapsed minutes: approximately 3-4"' in /work/repo
succeeded in 0ms:
Total elapsed minutes: approximately 3-4
tokens used
41,199Replay 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 4 minutes.
- 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.
Of the 237 ai projects Argusic has installed and timed, free-ai-tools was the 114th fastest to reach a running state, and 168 of 237 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 4 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
Topics (from GitHub)
aiai-agentsai-directoryai-toolsai-tools-directoryai-tools-listai-top-toolsawesomeawesome-aiawesome-ai-toolsawesome-listbest-ai-tools-2026developer-resourcesfree-ai-toolsfree-ai-tools-for-pcopen-sourcetheresanaiforthattoolsvibe-codingworkflow
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/free-ai-tools)Questions
- Does free-ai-tools run?
- Yes. free-ai-tools 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 free-ai-tools?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8f802d7a76e4. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test free-ai-tools?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does free-ai-tools take to install?
- 4 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 free-ai-tools need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing free-ai-tools?
- 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 free-ai-tools compare with the alternatives?
- Of the 237 ai projects Argusic has installed and timed, free-ai-tools was the 114th fastest to reach a running state, and 168 of 237 reached one at all.
- Where is the evidence for free-ai-tools?
- 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.