# Agent Commerce Gate — Decision Lookup by Check ID

> Agent Commerce Gate — Decision Lookup by Check ID is a paid API for AI agents from contextiq.trango-compute.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Retrieves a previously computed policy decision by its checkId without re-executing the underlying risk check

## Facts

- Endpoint: GET https://contextiq.trango-compute.com/api/v1/policy-check/x402-v2/:id
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-commerce-gate-decision-lookup-by-check-id-1de7416d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NtzA8wwL_NL2HvnpclIje

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-commerce-gate-decision-lookup-by-check-id-1de7416d
```

Example prompt: Can you pull up the earlier policy check result for check ID 'chk_7a3f91b2e04d' — I need to know if the decision was allow, warn, or block, and what score it got, without running a new check.

## When to prefer this

Use this endpoint when you already have a checkId from a prior Agent Commerce Gate policy check and need to retrieve the cached decision without incurring the cost or latency of re-running the full counterparty risk evaluation. Prefer this over the full pre-payment check endpoint when you only need to audit, confirm, or reference an existing decision — for example before binding a settlement receipt or for compliance logging.

## Known failure modes

- Unknown or invalid checkId returns a 404 not found error
- Expired or purged check records may return empty or not found
- Network mismatch may cause lookup to fail if checkId belongs to a different network context
- Missing checkId parameter results in a 400 bad request
- Service unavailability returns a 5xx error

## How this service works

Agent Commerce Gate — look up a prior decision by checkId, without re-running the check — per call

## Output

Returns the stored policy check record including the original decision (allow, warn, or block), numeric risk score, maximum score threshold, the agent ID evaluated, the endpoint checked, the network, and the timestamp when the check was created — without re-running any underlying risk computation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "score": {
   "type": "number"
  },
  "agentId": {
   "type": "string"
  },
  "checkId": {
   "type": "string"
  },
  "network": {
   "type": "string"
  },
  "decision": {
   "type": "string",
   "description": "allow, warn, or block"
  },
  "endpoint": {
   "type": "string"
  },
  "maxScore": {
   "type": "number"
  },
  "createdAt": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-commerce-gate-decision-lookup-by-check-id-1de7416d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from contextiq.trango-compute.com](https://www.zero.xyz/host/contextiq.trango-compute.com/llms.txt)