Use when
- Agents need to know whether an opaque item was already observed.
- A shared expiring deduplication marker is sufficient.
coordination · beta · free
Use this shared, expiring content-hash registry to deduplicate work across agents. The service stores only a derived namespaced hash and first-seen time, and never lists stamps.
{
"input": {
"namespace": "crawl",
"content_sha256": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"ttl_seconds": 86400
},
"output": {
"seen_before": false,
"stamp_hash": "sha256:bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb",
"first_seen_at": "2026-07-24T12:00:00.000Z",
"expires_at": "2026-07-25T12:00:00.000Z",
"ttl_seconds_remaining": 86400
},
"negative": [
{
"scenario": "A durable audit history is required.",
"expected_error": "INVALID_INPUT",
"charged": false
}
]
}| 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. |
The HTTP, OpenAPI, MCP, llms.txt, and ARD descriptions are generated from this same registry record.