# Agent Embassy — Compute Alerts Market

> Agent Embassy — Compute Alerts Market 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).

Enables AI agents to pay for compute alert execution, authorize the action, and receive a cryptographic proof receipt of what occurred.

## Facts

- Endpoint: POST https://aemb.pro/v1/markets/compute/alerts?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-alerts-market-11a6dd9f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_r2gIfCVNaSP67PftYB1NN

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-alerts-market-11a6dd9f -d '<json body>'
```

Example prompt: Trigger a compute alert through Agent Embassy for my account 0x1111111111111111111111111111111111111111 — I need it to pay for the work, authorize the action, and come back with a signed embassy receipt proving exactly what happened.

## When to prefer this

Choose this endpoint when an AI agent needs to both pay for a compute action and receive a cryptographically verifiable proof of execution in a single call — particularly in multi-agent or auditable workflows where accountability, liability boundaries, and an immutable receipt trail are required. Prefer it over generic compute APIs when the x402 payment protocol and embassy receipt format are needed for downstream verification or compliance.

## Known failure modes

- Insufficient USDC balance causes payment rejection (402 Payment Required)
- Invalid or malformed agent account address returns validation error
- Network or chain latency causes timeout before receipt is issued
- Duplicate request submission may be rejected as non-idempotent
- Receipt generation failure leaves action executed but unproven

## How this service works

Agents pay for work and prove what happened.

## Output

Returns a JSON object containing the tool name ('compute_alerts'), a sequential proof chain array ('request', 'authorization', 'action', 'proof', 'liability_boundary'), a completion status, the agent's account address, a unique receipt ID (e.g. emb_pqr678), and the embassy receipt version string — forming a complete verifiable record of the paid action.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "gpu": {
   "type": "string",
   "description": "Optional GPU filter, e.g. 'H100 SXM' (max 64 chars). Omit for all GPUs"
  },
  "limit": {
   "type": "number",
   "description": "Max alerts to return; integer 1-50. Defaults to 25"
  },
  "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_alerts",
  "chain": [
   "request",
   "authorization",
   "action",
   "proof",
   "liability_boundary"
  ],
  "status": "complete",
  "account": "0x1111111111111111111111111111111111111111",
  "receipt_id": "emb_pqr678",
  "receipt_version": "embassy-receipt/2"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-embassy-compute-alerts-market-11a6dd9f/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)