Cloud Counter API

About the Cloud Counter API

A cloud counter API that keeps a named number for you between requests, with no database to run. Pick an ID, call it with up, down, set or get, and the current value comes back with timestamps for when it was created, last read and last changed. It works as a persistent counter for page views, button clicks, download tallies, queue numbers or anything else you would otherwise store a single integer for.

Because the counter lives behind a simple GET request, it fits static sites, serverless functions, no-code automations, IoT devices and quick prototypes. Each response also describes the number: spelled out in words and as an ordinal, its digit count, and whether it is even, negative, zero or prime.

Counters are scoped to your API key, and you can list or delete them at any time. The Free plan increments and decrements in steps of one and can set any value. Paid plans let up and down move the counter by any amount in one call, and higher plans allow more counters per key.

How it works

Cloud Counter stores each counter under your API key, keyed by id. An id must be 1 to 64 letters, digits, underscores or hyphens; anything else returns a 400. The first call to an unknown id, for any action other than delete, creates it at 0. Creation is refused once your key holds its maximum number of counters: five on the Free plan and the entry paid plan, 50 on higher plans.

action defaults to get. up adds value and down subtracts it, with value defaulting to 1; on the Free plan value is ignored for these two, so they always step by one. set replaces the value with a whole number from 0 to 100,000,000. down can take a counter below zero, but no action may leave it beyond 100,000,000 in either direction; a change that would is refused with a 400 and the counter is left unchanged. delete removes the counter and returns a confirmation message, or a 404 if it does not exist. list returns every counter on the key as id, value and created, with a count.

Every read stamps lastRead. Every change also updates lastUpdated and lastAction, which a plain get leaves alone. All timestamps are ISO 8601 in UTC.

The descriptive fields are recomputed on each call. words and ordinal spell out the value in English ("twenty-five", "twenty-fifth"). numberOfDigits ignores the minus sign. isEven, isNegative and isZero are as named. isPrime uses trial division and is false for anything below 2. Updates are read-then-write rather than atomic, so simultaneous calls on the same counter can overwrite each other.

What people use it for

Article View Counts

Increment a page tally each time a reader loads a blog post, returning the fresh total without querying a local database.

Feature Usage Quotas

To enforce monthly limits, SaaS backends increase a user action counter and check whether the total crosses allowed thresholds.

Live Score Tracking

Gaming servers adjust player points up or down during matches while fetching parity and formatted word representations.

Inventory Stock Adjustments

When shoppers complete checkout, decrement item tallies and inspect the remaining balance without maintaining dedicated database tables.

Without writing code

Word Counter Widget for Windows counts the words in anything you copy.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON

Default REST response

XML

Markup format

YAML

Human-readable

CSV

Tabular export

Beta

GraphQL

Query language

New

MCP

For AI agents

Request parameters — GET /v1/counter

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

1
2

curl "https://api.apiverve.com/v1/counter?id=test_counter" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Response — GET /v1/counter

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

{
  "status": "ok",
  "error": null,
  "data": {
    "created": "2024-04-26T22:09:46.000Z",
    "id": "test_counter",
    "lastAction": "get",
    "lastRead": "2025-12-16T22:21:45.000Z",
    "lastUpdated": "2024-04-26T22:09:46.000Z",
    "numberOfDigits": 1,
    "ordinal": "zeroth",
    "value": 0,
    "words": "zero",
    "isEven": true,
    "isNegative": false,
    "isZero": true,
    "isPrime": false
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

What a call costs — 1 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Zero-code embed — one snippet, no backend

Drop an interactive Cloud Counter form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — Cloud Counter API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1