# nanoid npm Package Module and Type Entrypoints

> nanoid npm Package Module and Type Entrypoints 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).

Returns module and type entrypoints metadata for the nanoid npm package, supporting integration and upgrade planning.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/signal-npm-nanoid-entrypoints?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/nanoid-npm-package-module-and-type-entrypoints-f47c54f7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_w-EvtJ9gJ7Cpylk5_jvyr

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 nanoid-npm-package-module-and-type-entrypoints-f47c54f7 -d '<json body>'
```

Example prompt: What are the module and type entrypoints for the nanoid npm package — can you pull the registry metadata so I can plan my integration?

## When to prefer this

Use this endpoint when you need to programmatically inspect how the nanoid npm package exposes its modules and types — for example, to verify ESM/CJS compatibility, check TypeScript type entry paths, or plan a version migration. Prefer this over manually browsing npmjs.com or parsing package.json files directly.

## Known failure modes

- Package name not found in registry — returns 404 or empty result
- Invalid or non-existent version specified — registry returns version-not-found error
- Registry timeout or unavailability — service may return 5xx error
- Malformed package name exceeding 150 characters — input validation error

## How this service works

nanoid Module and type entrypoints: Module and type entrypoints for npm package nanoid. Inspect registry metadata for integration and upgrade planning. Package and version can be overridden.

## Output

Returns structured registry metadata for the nanoid npm package, including its module entrypoints (e.g. main, module, exports fields) and type entrypoints (e.g. TypeScript .d.ts paths), enabling developers and agents to plan integrations and version upgrades.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nanoid-npm-package-module-and-type-entrypoints-f47c54f7/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)