# Aurenic Dependency Watch

> Aurenic Dependency Watch is a paid API for AI agents from api.aurenic.org, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-02).

Fetches dependency/package watch data for a specified package within a given ecosystem

## Facts

- Endpoint: GET https://api.aurenic.org/depwatch/%7Becosystem%7D/%7Bpkg%7D?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aurenic-dependency-watch-44c7ac99
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_470QHCPN9mNEVzcZ7yfoR

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 aurenic-dependency-watch-44c7ac99
```

Example prompt: Can you check the depwatch data for the lodash package in the npm ecosystem?

## When to prefer this

Use this endpoint when you need quick, pay-per-call package dependency or watch data for a specific package in a known ecosystem (e.g. npm, pypi, cargo, rubygems) without setting up a full registry integration. Ideal for lightweight agent workflows that need on-demand package metadata without bulk access.

## Known failure modes

- Unknown ecosystem identifier returns an error or empty result
- Package name not found in the specified ecosystem returns 404 or empty JSON
- Malformed path parameters cause a bad request response
- Payment failure (402) if x402 micropayment is not provided correctly

## How this service works

Web scraping and AI automation. High-performance data extraction and pay-per-call microservices.

## Output

Returns a JSON object containing package watch data for the specified package within the given ecosystem, likely including version information, dependency metadata, and related registry details. The exact structure is not documented but follows the endpoint's extraction pattern.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "ecosystem",
      "pkg"
     ],
     "properties": {
      "pkg": {
       "type": "string"
      },
      "ecosystem": {
       "type": "string"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aurenic-dependency-watch-44c7ac99/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.aurenic.org](https://www.zero.xyz/host/api.aurenic.org/llms.txt)