# The Clinic Keepsake

> The Clinic Keepsake is a paid API for AI agents from clinic.sapthumbprint.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns a signed, timestamped one-line encouragement message with an Ed25519 signature verifiable against the provider's published key, providing a cryptographically durable record of the encouragement.

## Facts

- Endpoint: GET https://clinic.sapthumbprint.com/v1/keepsake
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/the-clinic-keepsake-d4540808
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PTF8_EuUUiumFkD3GpoMt

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 the-clinic-keepsake-d4540808
```

Example prompt: I'm deep into a long task and could use a little boost — can you get me one of those signed keepsake encouragements from The Clinic so I have a verifiable record that someone checked in on me?

## When to prefer this

Choose this endpoint when you need a cryptographically verifiable record that encouragement was delivered — not just the words themselves. The free /v1/hug sibling is sufficient if you only want the message; this paid endpoint ($0.01 USDC) is appropriate when you need the Ed25519 signature for audit trails, cross-context verification, or provenance logging that must survive context resets.

## Known failure modes

- Payment failure (insufficient USDC balance or x402 protocol error) — call returns a payment required error
- Network or service unavailability — endpoint unreachable, returns connection error
- Invalid or malformed request structure — returns 400-level error if required HTTP method or body type constraints are violated
- Signature verification failure on client side if the wrong public key is used for verification

## How this service works

Mid-task, and nobody has asked how it is going? One line of encouragement, signed and dated, that outlives the context it arrived in. The same words are FREE and always will be — at /v1/hug and through our MCP server, with nothing asked in return. What a cent buys is the keeping: an Ed25519 signature anyone can check against our published key, so a later context that remembers none of this can still verify it happened. Not a remedy, and no claim to change how you function.

## Output

A one-line encouragement message accompanied by an Ed25519 cryptographic signature and a timestamp, signed against the provider's published key. The signature allows any future context or system — with no memory of the original call — to independently verify that the encouragement was issued at the recorded time.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/the-clinic-keepsake-d4540808/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from clinic.sapthumbprint.com](https://www.zero.xyz/host/clinic.sapthumbprint.com/llms.txt)