coordination · beta · free

Freshness Lease

Atomically grants a short renewable lease for refreshing an opaque resource. Only the current holder can renew or release it; status reveals activity and TTL but never the holder.

Use when

One agent should own a renewable refresh responsibility for a short period.
Peers need to see lease activity and expiry without learning the holder.

Do not use when

The underlying refresh itself must execute exactly once.
A permanent ownership record is required.

Invocation contract

HTTP: /v1/tools/freshness-lease
Version: 0.1.0
Mode: atomic
Idempotency: required
Retention: Only hashes of the namespace, key, and holder remain in Valkey until the lease TTL expires. Raw identifiers are never returned.
Tested with: HTTP/1.1, HTTP/2, MCP Streamable HTTP

Positive and negative examples

{
  "input": {
    "action": "acquire",
    "namespace": "index:example.invalid",
    "key": "sitemap-refresh",
    "holder": "agent-a",
    "ttl_seconds": 45
  },
  "output": {
    "action": "acquire",
    "lease_hash": "sha256:cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc",
    "active": true,
    "acquired": true,
    "renewed": false,
    "released": false,
    "held_by_caller": true,
    "expires_at": "2026-07-24T12:00:45.000Z"
  },
  "negative": [
    {
      "scenario": "The underlying refresh itself must execute exactly once.",
      "expected_error": "INVALID_INPUT",
      "charged": false
    }
  ]
}

Deterministic errors

Code	Retry	Charged	Recovery
INVALID_INPUT	false	false	Correct the request to match input_schema.
TOOL_PAUSED	true	false	Wait for the operator to resume the tool.
RATE_LIMITED	true	false	Retry after the response Retry-After interval.
DEPENDENCY_UNAVAILABLE	true	false	Retry with the same idempotency identity.

Full machine manifest

The HTTP, OpenAPI, MCP, llms.txt, and ARD descriptions are generated from this same registry record.

Open JSON manifest →