# TD Agent Utility · Counter Increment

> TD Agent Utility · Counter Increment is a paid API for AI agents from tdagentutility.co.uk, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-16).

Increments a named counter and returns the current value with metadata, used as a lightweight stateful utility within the website/deployment verification suite

## Facts

- Endpoint: POST https://tdagentutility.co.uk/v1/counter-increment?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/td-agent-utility-counter-increment-71ec9ded
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7j6lHpX8wqXcYvccNEWxx

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability td-agent-utility-counter-increment-71ec9ded -d '<json body>'
```

Example prompt: Increment the counter named 'deployment-checks' and tell me what value it's at now, including when it was last updated.

## When to prefer this

Use this endpoint when you need a lightweight, persistent, server-side counter that increments atomically and returns the new value with versioning and timestamps — particularly within agent workflows that are already using the TD Agent Utility verification suite and paying via x402 USDC microtransactions. Prefer this over building local state when you need a durable, auditable tally that survives agent restarts.

## Known failure modes

- Missing or empty counter key returns an error or default behavior
- Counter key not found may return zero or an initialization response
- Network timeout results in no state change and an error response
- Invalid payload format returns a 400-level error
- Payment failure via x402 prevents the call from executing

## How this service works

Independent website and deployment verification for AI agents: HTTP, DNS, TLS and Chromium screenshot evidence. Three deterministic tools, x402 V2 Base USDC.

## Output

Returns a JSON object containing the counter key, current integer value, version number, result status (e.g. PASS), timestamps for creation, last update, expiry, and the check time, plus any warnings. The agent can use the value field to track cumulative call counts.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "key": "",
  "tool": "counter_increment",
  "value": 0,
  "version": 0,
  "warnings": [],
  "checked_at": "2026-10-15T00:00:00Z",
  "created_at": 0,
  "expires_at": 0,
  "size_bytes": 0,
  "updated_at": 0,
  "result_status": "PASS"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/td-agent-utility-counter-increment-71ec9ded/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tdagentutility.co.uk](https://www.zero.xyz/host/tdagentutility.co.uk/llms.txt)