# Ollama Account Usage Checker — Full Usage Detail (`subimpact/ollama-usage-checker`) Actor

Full account usage report for your Ollama Cloud API key: weekly & session limits with per-model request counts, 4-week cost breakdown, pace forecast, session reset countdown, fair-share analytics, and account info. Official API — no scraping. Invalid keys are never charged.

- **URL**: https://apify.com/subimpact/ollama-usage-checker.md
- **Developed by:** [subimpact](https://apify.com/subimpact) (community)
- **Categories:** Developer tools, AI
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 usage checks

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Ollama Account Usage Checker

Paste your **Ollama Cloud API key** and get full usage detail for your account — official API, no scraping.

### What you get

- **Weekly limits** — usage %, total requests, per-model request counts
- **Session limits** — usage %, per-model, plus **reset countdown** (verified 5h epoch cadence)
- **4-week activity** — total cost, per-model cost + request share, cost per 1k requests
- **Analytics** — pace forecast (projected end-of-session %), amber/red ETA, fair-share vs 14.3%/day baseline, projected monthly cost, daily burn
- **Account** — plan, email, username, account age

### Input

| Field | Type | Description |
|---|---|---|
| `apiKey` | secret string | Your Ollama API key (`sk-...`). **Secret input** — encrypted at rest, never logged, never written to the dataset. |
| `mode` | select | `detailed` (default) or `quick` (weekly/session pct + cost only) |

### Output

One dataset item with the full report (see output schema). The API key appears **only masked** (`sk-4••••9Gxz`).

### Pricing

**$0.02 per run** (pay per event). Schedule it (e.g. daily) to track your usage over time.

### Notes

- Uses the official `ollama.com/api/usage` + `/api/me` endpoints with your key — same data as the Ollama settings page, enriched.
- Invalid keys return `{"ok": false, "error": "invalid_key"}` — you are not charged for failed runs.
- Weekly reset cadence (fixed vs rolling) is still being pinned; the report labels it honestly.

# Actor input Schema

## `apiKey` (type: `string`):

Your Ollama Cloud API key (sk-...). Stored as a SECRET input — encrypted at rest, never logged, never written to the dataset. Only the masked form appears in output.

## `mode` (type: `string`):

detailed (default): full account + usage + analytics. quick: just weekly/session pct + 4-week cost.

## Actor input object example

```json
{
  "mode": "detailed"
}
```

# Actor output Schema

## `ok` (type: `string`):

true when the key was accepted and usage fetched

## `error` (type: `string`):

invalid\_key | ollama\_<status> | bad\_response | network\_error

## `key_masked` (type: `string`):

First 4 + last 4 chars of the API key

## `plan` (type: `string`):

Ollama plan (e.g. pro)

## `email` (type: `string`):

Email on the Ollama account

## `account` (type: `string`):

Account metadata

## `weekly` (type: `string`):

Weekly usage, pct, total requests, per-model

## `session` (type: `string`):

Session usage, pct, total requests, per-model

## `activity` (type: `string`):

Cost, period, total requests, per-model breakdown

## `analytics` (type: `string`):

Reset countdown, pace forecast, fair-share, projections

## `checked_at` (type: `string`):

ISO timestamp of the check

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "detailed"
};

// Run the Actor and wait for it to finish
const run = await client.actor("subimpact/ollama-usage-checker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "mode": "detailed" }

# Run the Actor and wait for it to finish
run = client.actor("subimpact/ollama-usage-checker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "detailed"
}' |
apify call subimpact/ollama-usage-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,subimpact/ollama-usage-checker"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/UAa3vfryaZYZP2PXS/builds/wEDZtDAUaG4AuCGlh/openapi.json