Skip to main content
Pinaivu produces a routing receipt for every inference request. The receipt records the node that ran your job, the payment amount, and a cryptographic signature from an AWS Nitro Enclave — an isolated, attested execution environment that cannot be tampered with. This lets you independently verify any result without trusting Pinaivu or the serving node.

​
Step 1: Get the request_id

Every response from the Pinaivu gateway includes a request_id field at the top level of the JSON response body. Capture it from any API call. 
{
  "id": "chatcmpl-abc123",
  "object": "chat.completion",
  "model": "llama3.2:1b",
  "request_id": "pnv_req_7f3a9c2e1b084d5f8e6a0c3d2b1f4e7a",
  "choices": [
    {
      "index": 0,
      "message": {
        "role": "assistant",
        "content": "Hello! How can I help you today?"
      },
      "finish_reason": "stop"
    }
  ]
}
Save the value of request_id — you will use it to retrieve the receipt in the next step.

​
Step 2: Look up the receipt

You have two options for retrieving a receipt: the REST API or the Explorer UI.
Send a GET request to the receipts endpoint, passing your request_id in the path and your API key in the Authorization header.
curl https://api.pinaivu.com/v1/receipts/pnv_req_7f3a9c2e1b084d5f8e6a0c3d2b1f4e7a \
  -H "Authorization: Bearer sk-pnv-..."
A successful response looks like this:
{
  "request_id": "pnv_req_7f3a9c2e1b084d5f8e6a0c3d2b1f4e7a",
  "node_id": "node_9d2f1c7b3a504e8d9b6c2f0a1e3d7c5b",
  "model": "llama3.2:1b",
  "timestamp": "2024-11-14T09:32:11Z",
  "payment_amount": "0.000042 USDC",
  "coordinator_signature": "0x3045022100a7f3...c2d91b"
}

​
Understanding the receipt fields

FieldDescription
request_idUnique identifier for the inference request, returned in every API response.
node_idThe peer GPU node on the Pinaivu network that executed the inference.
modelThe model name and version that served the request (e.g., llama3.2:1b).
timestampISO 8601 UTC timestamp of when the inference was completed.
payment_amountThe amount paid to the serving node for this request.
coordinator_signatureCryptographic signature produced by Pinaivu’s AWS Nitro Enclave, binding all fields above.

​
Use cases for verification

  • Auditing AI outputs — prove exactly which model and node produced a given response
  • Cost tracking — reconcile per-request payment amounts against your usage budget
  • Compliance reporting — attach routing receipts to AI-generated content as tamper-evident provenance records
  • Debugging latency issues — identify which node served a slow request and correlate with node history in the Explorer
The signature is produced inside an AWS Nitro Enclave — an isolated, attested execution environment. This means the signature cannot be forged, even by Pinaivu itself.