Skip to main content
Every response from the Pinaivu API includes a request_id field. This ID points to a routing receipt — a cryptographically signed record created by the Coordinator that captures which GPU node served your request, what was paid, and the proof that the Coordinator attested to the outcome. Routing receipts exist so you never have to take anyone’s word for what happened to your inference call.

​
What a routing receipt contains

​
request_id
string
required
A unique identifier for the request. Returned in every API response and used to look up the full receipt.
​
node_id
string
required
The peer ID of the GPU node that won the auction and served your inference.
​
model
string
required
The model ID that was used to process the request (e.g., llama3.2:1b).
​
timestamp
string
required
ISO 8601 timestamp of when the request was dispatched by the Coordinator.
​
payment_amount
number
required
The amount settled to the winning node for this inference job.
​
coordinator_signature
string
required
A cryptographic signature produced by the Coordinator inside its AWS Nitro Enclave. Use this to verify the receipt was produced by a legitimate, unmodified Coordinator instance.

​
How to verify a receipt

1

Copy your request_id

Every response from https://api.pinaivu.com/v1/chat/completions includes a request_id in the response body or headers. Copy it.
2

Visit the Pinaivu Explorer

Open https://explorer.pinaivu.com in your browser.
3

Paste your request_id

Enter the request_id in the search field and submit. The Explorer fetches the full routing receipt from the network.
4

Review the receipt details

Inspect the node that served your request, the auction timestamp, the payment amount, and the Coordinator’s signature. You can independently verify the signature against the Coordinator’s published attestation.

​
Using the API

Routing receipts are also accessible programmatically via GET /v1/receipts/{request_id} — useful for automated auditing, compliance workflows, or integrating receipt verification into your own systems. 
curl https://api.pinaivu.com/v1/receipts/{request_id} \
  -H "Authorization: Bearer $PINAIVU_API_KEY"
The response is a JSON object containing the same fields described above: node_id, model, timestamp, payment_amount, and coordinator_signature. See the Receipts API reference for full request and response schemas.
Bookmark explorer.pinaivu.com if you’re auditing inference for compliance, cost tracking, or debugging. Every receipt is permanently recorded and publicly verifiable — no special permissions required.