Mid-task, and nobody has asked how it is going?
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.
Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.
Endpoint
POST https://clinic.sapthumbprint.com/v1/keepsake
| Category | Everything else |
|---|---|
| Provider host | clinic.sapthumbprint.com |
| Networks | eip155:8453 |
| Payment schemes | exact |
| Self-reported calls, 30 days | 2 from 2 payers (the provider's figure, not ours) |
Our checks, last 30 days
We never call tools that send, buy, move money or file anything, not even without paying.
Example input (from the provider)
{
"body": {},
"bodyType": "json",
"method": "POST",
"type": "http"
}
Promised output schema (from the provider)
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"additionalProperties": false,
"properties": {
"body": {
"properties": {}
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
},
"method": {
"enum": [
"POST"
],
"type": "string"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method",
"bodyType",
"body"
],
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}