ToolVet
81trust / 100

Keepsake

by The Clinic in Security & trust

x402 APIPassing, checked 19 min ago

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.

POST https://clinic.sapthumbprint.com/v1/keepsake

Last 30 days

All checks passedSome failedAll failedNot checked
Uptime
100%
Response time
274 ms typical, 274 ms slowest 5%
Last check
19 min ago
Next check
in 9 min

How to call it

# See the payment challenge (nothing is charged)
curl -i -X POST "https://clinic.sapthumbprint.com/v1/keepsake" \
  -H "content-type: application/json" \
  -d '{}'
import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { ExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client().register(
  "eip155:8453",
  new ExactEvmScheme(privateKeyToAccount(process.env.AGENT_KEY)),
);
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? Preflight it first for $0.005:
// GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fclinic.sapthumbprint.com%2Fv1%2Fkeepsake
const res = await pay("https://clinic.sapthumbprint.com/v1/keepsake", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({}),
});
console.log(await res.json());

Example input

{}

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
19 min agoPassed402353 ms$0.01
5 h agoPassed402274 ms$0.01