# Valuation API Price History

> Valuation API Price History is a paid API for AI agents from valuation-api-production-1c7c.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-30).

Retrieves historical price data for assets or valuations tracked by this service

## Facts

- Endpoint: GET https://valuation-api-production-1c7c.up.railway.app/history?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/valuation-api-price-history-554b82fe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EySn8PzO3R_4pn1hNiaGM

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability valuation-api-price-history-554b82fe
```

Example prompt: Can you pull up the price history for this asset from the valuation API so I can see how prices have changed over time?

## When to prefer this

Use this endpoint when you need historical price or valuation data for assets tracked by this specific valuation service. It is suitable for trend analysis, auditing past prices, or providing context on how an asset's value has changed over time. Best used when the asset in question is already indexed by this valuation API.

## Known failure modes

- Missing or invalid query parameters returns an error
- Asset not found returns empty or 404 response
- Service unavailable on Railway deployment returns 503
- Payment not included or insufficient USDC results in 402 rejection
- Rate limiting may return 429 if called too frequently

## How this service works

Get price history

## Output

Returns a list or series of historical price data points with associated timestamps, showing how valuations have changed over time for the queried asset or entity.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/valuation-api-price-history-554b82fe/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from valuation-api-production-1c7c.up.railway.app](https://www.zero.xyz/host/valuation-api-production-1c7c.up.railway.app/llms.txt)