# TaskForge X402 Catalog Endpoint Health Audit

> TaskForge X402 Catalog Endpoint Health Audit is a paid API for AI agents from qaegxjxaavxdqihfgzhr.supabase.co, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Checks up to 100 public catalog API endpoints for reachability, HTTP status codes, response latency, and launch readiness without triggering paid calls.

## Facts

- Endpoint: GET https://qaegxjxaavxdqihfgzhr.supabase.co/functions/v1/taskforge-x402-gateway/CATALOG_ENDPOINT_HEALTH_AUDIT
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/taskforge-x402-catalog-endpoint-health-audit-f8a8ef50
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AkSol3Kv7Pv7b5etMtr6c

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 taskforge-x402-catalog-endpoint-health-audit-f8a8ef50
```

Example prompt: Can you run a health audit on these 50 catalog endpoints and tell me which ones are reachable, what HTTP status codes they return, and which ones look ready to launch?

## When to prefer this

Choose this endpoint when you need to bulk-validate the reachability and HTTP health of multiple catalog API endpoints in a single call without triggering paid usage on those endpoints. It is especially useful for pre-launch readiness audits, marketplace catalog monitoring, or diagnosing degraded third-party integrations at scale (up to 100 endpoints per call).

## Known failure modes

- Exceeding 100 entries in the catalog_entries array returns a validation error
- Malformed or non-URI URLs in the input cause individual entry failures
- Endpoints behind authentication or firewalls may appear unreachable even if healthy
- Network timeouts on slow endpoints may be misreported as failures
- Missing required 'url' field on any catalog entry object causes request rejection

## How this service works

Use to check up to 100 public catalog endpoints for reachability, HTTP status, latency, and launch readiness without making paid calls.

## Output

Returns per-endpoint health data for each submitted catalog URL, including reachability status (up/down), HTTP status code, response latency, and a launch readiness assessment — all without triggering any paid API calls on the checked endpoints.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "catalog_entries": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "url"
    ],
    "properties": {
     "id": {
      "type": "string"
     },
     "url": {
      "type": "string",
      "format": "uri"
     }
    }
   },
   "maxItems": 100
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/taskforge-x402-catalog-endpoint-health-audit-f8a8ef50/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from qaegxjxaavxdqihfgzhr.supabase.co](https://www.zero.xyz/host/qaegxjxaavxdqihfgzhr.supabase.co/llms.txt)