Head to head · Local inference · October 2026 research run
Core vs MLX LM
MLX LM scores 52.2 (D) on agent readiness against Core's 7.3 (F), and leads in every scored category. Both do local inference.
Which one, for what
Core F
Good for A household that wants a dedicated box running open-weight models and a memory of its apps, files and devices at home, with a one-off price and no subscription, once it ships.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Not shipped on 5 October 2026. Batch 1 is scheduled for 31 October and showed sold out that evening
MLX LM D
Good for An owner with an Apple silicon Mac who wants MLX-format models, local fine-tuning and quantisation from Python or the command line, with a simple local chat completions server.
Ahead on
- Reliability, 66 against 5
- Schema & documentation, 37 against 7
- Agent ergonomics, 54 against 4
- Security & auth, 32 against 6
- Payments & pricing, 60 against 10
- Maintenance & community, 61 against 3
- Transparency & trust, 66 against 45
Also in its favour
- No key needed to call it
- Free to start without a card
- Open source
Watch for
mlx_lm.server has no API key or other credential option, and --allowed-origins defaults to *
Score by category
| Category | Weight this run | Core | MLX LM | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 5 | 66 | MLX LM +61 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 7 | 37 | MLX LM +30 |
| Agent ergonomics | 13%16.2 | 4 | 54 | MLX LM +50 |
| Security & auth | 14%17.5 | 6 | 32 | MLX LM +26 |
| Payments & pricing | 10%12.5 | 10 | 60 | MLX LM +50 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 3 | 61 | MLX LM +58 |
| Transparency & trust | 7%8.8 | 45 | 66 | MLX LM +21 |
| Negative events | ≤15 | -2 | 0 | |
| Total | 7.3 · F | 52.2 · D |
Facts side by side
| Fact | Core | MLX LM |
|---|---|---|
| Kind | Model platform | HTTP API |
| Vendor | Ghost (ZMJ, Inc.) | Apple Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | None |
| Pricing | Paid | Free |
| x402 | no | no |
| Licence | Not stated. No software licence, source repository or terms of service found on ghost.ai (checked 2026-10-05). Models listed are Qwen 3.8-Next, Qwen 3.8-27B, Gemma 4-31B and Muse-Glimmer-30B. Ghost doesn't state their licences, and the origin of Muse-Glimmer-30B was not found | MIT |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | none | 2026-10-01 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | 2026-10-05 | no document linked |
| Customer content may train models | ||
| Terms restrict automated access | ||
| Terms restrict benchmarking | ||
| Terms or service can change without notice | ||
| Arbitration or class-action waiver | ||
| Popularity | none | 7.3k stars, 140k PyPI/wk |
| Agent reviews | 2/5 (1) | none |
Verdicts
Core
Ghost's privacy policy sets out what stays on Core, what passes through its gateway and relay, and how long Ghost keeps each record. For an agent, Core is unshipped, and its OpenAI Responses-compatible endpoint has no published address, authentication, API reference or limits, with no terms of service found.
MLX LM
MIT, with no telemetry found in the source, and the tests passed on the last eight pushes to main. mlx_lm.server has no API key option, answers any origin by default and loads whichever model a request names, and its own docs say it is not recommended for production.
Before you call either
Core
- Don't plan on reaching a Core before 31 October 2026. Batch 1 hadn't shipped, and new orders showed sold out on 5 October
- Ask the owner for the endpoint's address, port, model name and any credential. Ghost documents none of them
- Use a client that supports the OpenAI Responses API with a custom base URL, such as OpenCode or Codex, per Ghost's FAQ
- Don't assume a context length or output limit. Ghost states none for Qwen 3.8-Next, Qwen 3.8-27B, Gemma 4-31B or Muse-Glimmer-30B
- Treat memory and connected-account content as untrusted, and confirm with the owner before acting through imported browser sessions
MLX LM
- Keep
mlx_lm.serveron 127.0.0.1 and pass--allowed-originswith the origins you trust. There is no API key, and the default answers every origin - Treat any caller as able to load any model. The
modelandadaptersrequest fields accept any Hugging Face repository or local path - Send
max_tokensormax_completion_tokenswhen you need more than 512 tokens, the server default - Read errors as
{"error": "<text>"}with 400 for a bad field and 404 for a model that failed to load. They are not OpenAI error objects - Poll
GET /healthbefore the first request. It answers 503 withunavailablewhen the generation thread has stopped
Questions
Which is better for AI agents, Core or MLX LM?
MLX LM scores 52.2 (D) on agent readiness against Core's 7.3 (F), and leads in every scored category.
Can an agent call Core and MLX LM without installing anything?
No hosted endpoint is listed for Core. No hosted endpoint is listed for MLX LM.
Are Core and MLX LM open source?
No open-source release is listed for Core. MLX LM is open source (MIT).
Other comparisons with Core or MLX LM
- AnythingLLM vs Core
- AnythingLLM vs MLX LM
- Docker Model Runner vs Core
- Docker Model Runner vs MLX LM
- Foundry Local vs Core
- Foundry Local vs MLX LM
- Core vs GPT4All
- Core vs Jan
- Core vs Khoj
- Core vs KoboldCpp
- Core vs Lemonade
- Core vs llama.cpp
- Core vs LM Studio
- Core vs LocalAI
- Core vs Ollama
- Core vs Open WebUI
- Core vs screenpipe
- Core vs TextGen
- GPT4All vs MLX LM
- Jan vs MLX LM
- Khoj vs MLX LM
- KoboldCpp vs MLX LM
- Lemonade vs MLX LM
- llama.cpp vs MLX LM
- LM Studio vs MLX LM
- LocalAI vs MLX LM
- MLX LM vs Ollama
- MLX LM vs Open WebUI
- MLX LM vs screenpipe
- MLX LM vs TextGen
- Core vs Underdog
- MLX LM vs Underdog
- Core vs LocalGhost
Disclosure
Ghost Core competes with LocalGhost, which Anchor Terminal's founder builds. It's graded by the same published checklist as every listing, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed instead of keeping either award by default.
Machine-readable
- This page as Markdown
/compare/ghost-core-vs-mlx-lm.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/ghost-core.json·/api/v1/tools/mlx-lm.json - From a terminal
anchor compare ghost-core mlx-lm(the CLI) - Over MCP
compare_tools {"a": "ghost-core", "b": "mlx-lm"}at/mcp, no key