# TD Agent Utility · Lock Acquire

> TD Agent Utility · Lock Acquire 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).

Acquires a distributed lock token as a coordination primitive before initiating website/deployment verification checks

## Facts

- Endpoint: POST https://tdagentutility.co.uk/v1/lock-acquire?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-lock-acquire-1c2d85f0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_39Ck0FClNil4TDg3nKC7I

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-lock-acquire-1c2d85f0 -d '<json body>'
```

Example prompt: Before we run the HTTP, DNS, and TLS checks on example.com, try to acquire a verification lock so we don't clash with any other agent running checks at the same time.

## When to prefer this

Choose this endpoint when you need to coordinate multiple agents or prevent concurrent runs of website verification checks on the same target. It acts as a distributed mutex before invoking the HTTP, DNS, TLS, or Chromium screenshot verification tools on the same service. Prefer it in CI/CD pipelines, multi-agent fleets, or any workflow where duplicate verification runs would waste resources or produce conflicting results.

## Known failure modes

- Lock already held by another agent — acquired returns false and lock_token is null
- Service unavailable or timeout — HTTP 5xx response
- Invalid or malformed request body — HTTP 4xx with error detail
- Payment failure via x402 — payment not accepted, request rejected
- Lock expired between check and acquire — race condition returning acquired: false

## 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 indicating whether the lock was successfully acquired (acquired: true/false), the lock token if acquired, the expiry timestamp, a result_status (e.g. PASS), the checked_at timestamp, and any warnings encountered during the attempt.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tool": "lock_acquire",
  "acquired": false,
  "warnings": [],
  "checked_at": "2026-10-15T00:00:00Z",
  "expires_at": null,
  "lock_token": null,
  "result_status": "PASS"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/td-agent-utility-lock-acquire-1c2d85f0/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)