# Hono NPM Install Lifecycle Hooks

> Hono NPM Install Lifecycle Hooks is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-17).

Retrieves install lifecycle hook metadata for the hono npm package to support integration and upgrade planning

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/signal-npm-hono-install-hooks?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hono-npm-install-lifecycle-hooks-ae7dcf9d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eSolJUHeu53DRAEdLQ98g

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 hono-npm-install-lifecycle-hooks-ae7dcf9d -d '<json body>'
```

Example prompt: Can you pull the install lifecycle hooks for the hono npm package at version 4.2.0 so I can check what scripts run during installation before we add it to our project?

## When to prefer this

Use this endpoint when you need to inspect exactly what lifecycle scripts hono executes during npm installation, particularly for security audits, CI pipeline vetting, or upgrade impact analysis. Prefer this over manually querying npm registry when you need a structured, agent-consumable response with payment handled via x402.

## Known failure modes

- Invalid or non-existent package version returns an error or empty result
- Malformed version string may cause a lookup failure
- Rate limiting or payment failure (x402) results in a 402 response
- Registry unavailability causes timeout or 503 error

## How this service works

hono Install lifecycle hooks: Install lifecycle hooks for npm package hono. Inspect registry metadata for integration and upgrade planning. Package and version can be overridden.

## Output

Returns registry metadata for the hono npm package including install lifecycle hook definitions (preinstall, install, postinstall scripts), version details, and related metadata useful for integration auditing and upgrade planning.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "package": {
   "type": "string",
   "default": "hono",
   "maxLength": 150
  },
  "version": {
   "type": "string",
   "maxLength": 100
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hono-npm-install-lifecycle-hooks-ae7dcf9d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)