putty
API ReferenceLedger

List your payment receipts

Returns the caller's own payment orders and their status, most recent first. This is a read-only viewer over what already exists: it never sends a transaction, never signs, and holds no key. Every query is owner-scoped, so another user's order can never appear here. A `txHash` is shown for the user to verify on a block explorer; putty does not broadcast it.

GET
/receipts

Returns the caller's own payment orders and their status, most recent first. This is a read-only viewer over what already exists: it never sends a transaction, never signs, and holds no key. Every query is owner-scoped, so another user's order can never appear here. A txHash is shown for the user to verify on a block explorer; putty does not broadcast it.

Query Parameters

limit?integer

How many orders to return, newest first.

Range1 <= value <= 100
Default50

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/receipts"
{  "receipts": [    {      "id": "string",      "orderId": "string",      "pack": "string",      "quoteUsd": "string",      "token": "string",      "amount": "string",      "status": "pending",      "txHash": "string",      "createdAt": "string",      "updatedAt": "string"    }  ]}

Ask the user for a secret POST

Creates a request for the user to enter a value in the dashboard. The value is never part of this request and never comes back through it: the user types it into a secure input, which stores it with `PUT /secrets/{name}` and marks the request `set`.

List the tools the MCP server exposes GET

Returns the MCP server's tool list as a plain JSON array. Every entry is the same descriptor the MCP `tools/list` response carries, so the docs site and an MCP client see the same tools in the same order. The `subcategories` array pairs each top-level category with the distinct subcategory labels that fall under it, so a client can render the docs grouping without re-scanning `tools`.