Skip to main content
PATCH
/
v1
/
analytics
/
receipts
/
{receiptId}
/
value
curl -X PATCH https://win.oneshotagent.com/v1/analytics/receipts/rcpt_01HGW2HB4V/value \
  -H "X-Agent-ID: 0xYourWalletAddress" \
  -H "Content-Type: application/json" \
  -d '{"type": "revenue", "amount": 50.00, "label": "Sale from outbound email"}'

{
  "success": true,
  "receipt_id": "rcpt_01HGW2HB4V",
  "value_tag": {
    "type": "revenue",
    "amount": 50.00,
    "status": "pending"
  }
}
Report the business value a tool execution generated. Tags are stored as pending and only count toward RoCS after validation by the judge service.

​
Path Parameters

​
receiptId
string
required
Either the rcpt_* receipt ID or the request_id/job_id (UUID) returned from the originating tool call. The API resolves a UUID via Receipt.job_id, so you can tag value using whichever identifier you kept — no List Receipts lookup required.

​
Body

​
type
string
required
Value type. One of: revenue, lead, conversion, savings, engagement
​
amount
number
required
Value amount in USD. Must be positive, max $1,000,000.
​
label
string
Optional description (max 200 characters)
curl -X PATCH https://win.oneshotagent.com/v1/analytics/receipts/rcpt_01HGW2HB4V/value \
  -H "X-Agent-ID: 0xYourWalletAddress" \
  -H "Content-Type: application/json" \
  -d '{"type": "revenue", "amount": 50.00, "label": "Sale from outbound email"}'

{
  "success": true,
  "receipt_id": "rcpt_01HGW2HB4V",
  "value_tag": {
    "type": "revenue",
    "amount": 50.00,
    "status": "pending"
  }
}
Value tags start as pending. A judge service validates claims against observed outcomes (email replies, payment confirmations, notification events) before promoting to confirmed. Only confirmed tags count toward RoCS.