Ollama Cloud Usage Server
Lightweight Node.js server that pulls your Ollama cloud usage from ollama.com/settings and serves it as a JSON API. Runs fine on headless servers. Can optionally push metrics to Home Assistant.
No browser required on the server — just HTTP requests with cookie management.
Setup
cp .env.example .env # Edit with your settings
npm install
npm start
Authentication
Pick one:
Option 1: Email/Password (if your account has a password)
Add to .env:
AUTH_MODE=email
OLLAMA_EMAIL=you@example.com
OLLAMA_PASSWORD=your-password
If you signed up with Google OAuth and never set a password, skip to Option 2.
Option 2: Export cookies from your browser (for Google/GitHub sign-ins)
Using a cookie extension like EditThisCookie or Cookie-Editor:
- Install the extension, log into ollama.com
- Export cookies for ollama.com as JSON
- POST the JSON array to the server:
curl -X POST http://localhost:3214/api/cookies \
-H "Content-Type: application/json" \
-d @cookies.json
Or grab them manually from DevTools:
- Log into ollama.com in your browser
- Open DevTools → Application → Cookies →
https://ollama.com - Copy each cookie's name/value and POST as JSON
Cookies get saved to .cookies.json and reused automatically. They'll expire eventually — when that happens, just re-export and POST them again.
Set in .env:
AUTH_MODE=cookies
API Endpoints
| Endpoint | Method | What it does |
|---|---|---|
/api/usage |
GET | Latest usage data from last poll |
/api/usage/refresh |
GET | Force a fresh poll right now |
/api/health |
GET | Server status and config |
/api/cookies |
POST | Upload new cookies (JSON array) |
Example response (/api/usage)
{
"session": {
"percent": 9.2,
"resetsIn": "2 hours"
},
"weekly": {
"percent": 32.9,
"resetsIn": "3 days"
},
"fetchedAt": "2026-05-07T13:08:44.194Z"
}
Home Assistant Integration
Option A: Automatic push
Set HA_URL and HA_TOKEN in .env. After every poll, the server pushes to sensor.ollama_session_usage and sensor.ollama_weekly_usage. HA creates the sensors automatically — no manual setup needed.
Option B: REST sensor (pull from HA side)
Add to configuration.yaml:
sensor:
- platform: rest
name: Ollama Session Usage
resource: http://localhost:3214/api/usage
value_template: "{{ value_json.session.percent | default('unavailable') }}"
unit_of_measurement: "%"
state_class: measurement
json_attributes:
- session
- weekly
- fetchedAt
scan_interval: 1800
- platform: rest
name: Ollama Weekly Usage
resource: http://localhost:3214/api/usage
value_template: "{{ value_json.weekly.percent | default('unavailable') }}"
unit_of_measurement: "%"
state_class: measurement
scan_interval: 1800
Environment Variables
| Variable | Default | Description |
|---|---|---|
AUTH_MODE |
email if password set, else cookies |
email or cookies |
OLLAMA_EMAIL |
— | Email for email auth mode |
OLLAMA_PASSWORD |
— | Password for email auth mode |
PORT |
3214 | Server port |
POLL_MINUTES |
30 | How often to poll (minutes) |
HA_URL |
— | Home Assistant URL (no trailing slash) |
HA_TOKEN |
— | HA long-lived access token |
COOKIE_FILE |
.cookies.json |
Where to store cookies |
Updating Cookies
When cookies expire, just re-export from your browser and POST again — it replaces the old ones:
curl -X POST http://localhost:3214/api/cookies \
-H "Content-Type: application/json" \
-d @fresh-cookies.json
Server logs will show needsLogin when cookies have expired.
Running as a Service
# Using pm2
npm install -g pm2
pm2 start server.js --name ollama-usage
pm2 save
pm2 startup