# Agent Embassy — Compute Market History

> Agent Embassy — Compute Market History is a paid API for AI agents from aemb.pro, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-11).

Returns historical price data for the GPU compute market, optionally filtered by GPU type, with a cryptographic receipt proving payment and action occurred.

## Facts

- Endpoint: POST https://aemb.pro/v1/markets/compute/history?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-embassy-compute-market-history-6da7b880
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Jrttfsg-O7yx2VtZbrvp6

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 agent-embassy-compute-market-history-6da7b880 -d '<json body>'
```

Example prompt: Pull the last 100 data points of H100 SXM compute market history from Agent Embassy and give me a verifiable receipt — use idempotency key 'hist-h100-run-001'.

## When to prefer this

Use this endpoint when you need verifiable, receipted historical GPU compute pricing data — particularly when an audit trail or proof-of-action is required. Prefer it over unauthenticated price feeds when you need cryptographic accountability for what was queried and when, or when building workflows that must demonstrate compliance with a payment-gated information access model.

## Known failure modes

- Payment authorization missing or invalid in live mode — returns 402 Payment Required
- GPU filter string exceeds 64 characters — validation error
- Limit outside range 1-200 — validation error
- Idempotency key collision returns cached original receipt even if inputs differ
- Agent wallet string too short in dev mode — validation error

## How this service works

Agents pay for work and prove what happened.

## Output

A JSON object containing the tool name, a proof chain array (request, authorization, action, proof, liability_boundary), completion status, the account wallet address, a unique receipt ID, and receipt version — confirming both the historical data retrieval and the payment authorization.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "gpu": {
   "type": "string",
   "description": "Optional GPU filter, e.g. 'H100 SXM' (max 64 chars). Omit for whole-market history"
  },
  "limit": {
   "type": "number",
   "description": "Max history points to return; integer 1-200. Defaults to 50"
  },
  "idempotency_key": {
   "type": "string",
   "description": "Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tool": "compute_history",
  "chain": [
   "request",
   "authorization",
   "action",
   "proof",
   "liability_boundary"
  ],
  "status": "complete",
  "account": "0x1111111111111111111111111111111111111111",
  "receipt_id": "emb_mno345",
  "receipt_version": "embassy-receipt/2"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-embassy-compute-market-history-6da7b880/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from aemb.pro](https://www.zero.xyz/host/aemb.pro/llms.txt)