darkbloom app can serve models on your own Mac, to you alone, through an OpenAI-compatible API. When your Mac can’t take a request, it can pass the request to your other Macs for free, and then to the Darkbloom network, billed to your balance.
This is the same app that providers install. You do not need to earn anything to use it: Only me never contacts Darkbloom and needs no account.
Requirements
- An Apple silicon Mac. The installer checks for
arm64and refuses an Intel Mac. - macOS 27 or later for a new install. The binary targets macOS 14, and a Mac that already has the CLI or a provider config can reinstall or repair on an older system with an upgrade notice.
- Enough unified memory for the model you choose. Serving starts at 8 GB, but every real model needs more: the catalog’s smallest build (
gpt-oss-20b) needs about 24 GB, the 8-bit Gemma 4 26B builds need 48 GB,nvidia-nemotron-3.5-superis registered for 128 GB, andglm-5.3-flashfor 256 GB. - Disk for each model’s weights. The catalog lists a size for every model, and
darkbloom models listshows what is already on the Mac.
https://api.darkbloom.dev.
Install
Follow Install and set up the provider for what the installer checks and writes. The install is one command:darkbloom on your PATH and at least one model.
Serve only you
darkbloom local is the shortest path. Where nothing is serving, it starts Only me in the background, exactly as darkbloom start --local does, then prints the local API’s base URL and key. Where Darkbloom is already serving, it prints the address and key if a local API is up, and only in a terminal asks before switching this Mac to Only me; pressing Enter keeps Darkbloom serving.
darkbloom start --local is the explicit form. It serves Only me in the background and saves the choice, so it starts at login, restarts after a crash and updates itself. darkbloom start --local --here serves it in the current Terminal until Ctrl-C and saves nothing.
Only me means:
- This Mac’s models on this Mac’s local API.
- No coordinator connection and no earnings.
- Requests this Mac answers never leave the Mac and are never billed.
Choose models
darkbloom start --local --model <id>, repeatable, to skip the picker.
Call the local API
darkbloom local prints the address to use as the base URL, the key, the file that holds the key, and a curl example. The key is this Mac’s own local key and is also in ~/.darkbloom/local_token; it is not your account API key, which starts with sk-db-.
On a Mac whose first free port was 8001, the address looks like http://127.0.0.1:8001/v1. Copy what the command prints rather than assuming the port.
GET /v1/models on the same base URL lists the models this Mac advertises.
Where requests go when your Mac is busy
The local API answers on this Mac first. When it doesn’t serve the model, or has no room for the request, the saved route decides what happens next.
Without a saved account key the default is
this-mac; once a key is saved the default is my-macs. A route change applies to a running local API from its next request that needs it, with no restart and no model reload.
To save the key:
sk-db-. darkbloom route key checks it once and keeps it in your Mac’s Keychain. It is never printed, logged or written to provider.toml.
Requests from other machines never use the paid network. The API listens on loopback by default. If you bind it beyond loopback (--bind), a request that arrives over your LAN or tailnet can use this Mac and your other Macs, but is treated as my-macs even when the saved route is my-macs-first, so it never reaches the network. Anyone on that network with the key can use the API.
Serve Darkbloom and yourself
On a Mac with no saved choice,darkbloom start serves Both: Darkbloom’s requests, which earn, and a local API for you. It saves that choice.
Add --me-first to pause Darkbloom while you use the Mac; --local-endpoint is the older flag for the same thing. From the moment one of your requests holds a model, Darkbloom sends no new requests here. Requests it already started finish, and it comes back once none of your requests has run for 2 minutes. --me-first-idle <min> changes that window (1 to 120), and --no-me-first keeps Darkbloom serving while you use the local API.
darkbloom status says how this Mac serves. What serving the network earns, and how it is paid, is in Provider overview and Earnings.
Two Macs
Two Macs joined by a Thunderbolt 5 cable, with RDMA over Thunderbolt enabled on each and the same Darkbloom version installed, can serve one model together.darkbloom cluster local serves that pair for you alone: each Mac holds part of the model, no Mac contacts a coordinator, nothing registers or takes public traffic, and nothing is billed. It needs a terminal, pairs the Macs first if they are not paired yet, and ends with the pair’s local API, for example ✓ Serving <model> on both Macs, on your local API at http://localhost:8001. darkbloom local on either Mac then prints that Mac’s address and key. The pair’s API listens on every network of the leading Mac by default; add --bind 127.0.0.1 to keep it on that Mac. darkbloom cluster instead pairs the two to serve through Darkbloom with a local API beside it.
Privacy
A request this Mac answers stays on this Mac: it is not sent to Darkbloom and is not billed. A request the router passes on leaves the Mac as an API request. It goes through the Darkbloom coordinator, which decrypts it in memory to route and bill it, and the Mac that runs the model sees the prompt and completion in plaintext. That is the same path as a request to the public API, and it is not end-to-end encryption between you and the provider. See Security and trust for the full model. The local API has no TLS and no rate limiting. Keep the default loopback bind, or put a reverse proxy in front before exposing it.--no-auth removes the bearer-token check; the local router then keeps every request on this Mac and never uses your account key.
Inference is an experimental research prototype. Expect rough edges and breaking changes.

