# Ontario Protocol x402 Listing Refresh

> Ontario Protocol x402 Listing Refresh is a paid API for AI agents from ontarioprotocol.com, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-13).

Refreshes an existing Ontario provider listing profile, re-running HTTP 402 readiness checks, Coinbase Bazaar retrieval, and agent-payment-policy validation to diagnose why agents aren't buying a given x402 API.

## Facts

- Endpoint: POST https://ontarioprotocol.com/api/x402/refresh-listing
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ontario-protocol-x402-listing-refresh-362540c2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lWNABN6ua6isUQ4WIE52o

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 ontario-protocol-x402-listing-refresh-362540c2 -d '<json body>'
```

Example prompt: I just fixed the HTTP 402 responses on my API — can you refresh my Ontario listing 'lst_abc123' so agents can find and buy it again?

## When to prefer this

Use this endpoint after making changes to your x402 API (fixing 402 headers, updating pricing, changing payment policies) and needing the Ontario Bazaar listing to reflect those changes and re-pass agent-payment-policy checks. Prefer this over the free diagnostic endpoint when you have an existing paid listing (lst_ ID) and want to actually update the live profile, not just test readiness.

## Known failure modes

- Invalid listing_id format (must match ^lst_[A-Za-z0-9_-]+$) returns validation error
- Expired or already-used paid_refresh_tx credit token returns credit redemption error
- Listing not found for the given listing_id returns 404-style error
- Underlying HTTP 402 endpoint still failing causes refresh to complete but verification_status remains non-ready
- Payment not settled causes refresh to be blocked
- Rate limiting or network timeout on Bazaar retrieval causes partial failure

## How this service works

Find the first reason agents are not buying your x402 API. Test HTTP 402 readiness, Coinbase Bazaar retrieval, buyer-task fit, and agent payment policy free.

## Output

Returns a refreshed listing object with updated verification status (e.g. 'ready'), a schema-versioned Ontario x402 listing profile (ontario.x402_listing_profile.v1), and a top-level status field confirming the refresh completed or identifying the blocking issue.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "listing_id": {
   "type": "string",
   "pattern": "^lst_[A-Za-z0-9_-]+$",
   "description": "Existing paid Ontario provider profile identifier."
  },
  "paid_refresh_tx": {
   "type": "string",
   "description": "Optional one-time retry credit returned after a settled refresh could not complete."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "example": {
  "status": "refreshed",
  "listing": {
   "id": "lst_example",
   "verification_status": "ready"
  },
  "profile": {
   "schema": "ontario.x402_listing_profile.v1"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ontario-protocol-x402-listing-refresh-362540c2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ontarioprotocol.com](https://www.zero.xyz/host/ontarioprotocol.com/llms.txt)