# Validate .bowerrc

> Validate .bowerrc 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-15).

Validates a JSON document against the pinned SchemaStore definition for .bowerrc Bower configuration files, reporting JSON pointer paths and rule violations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-bowerrc-07c086d6-validate?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/validate-bowerrc-1bdad9bf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_O__c_HqiOgH7Z75NPt-ai

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 validate-bowerrc-1bdad9bf -d '<json body>'
```

Example prompt: Can you validate this .bowerrc JSON for me — I want to make sure it follows the correct schema before I commit it: {"directory": "bower_components", "registry": "https://registry.bower.io"}

## When to prefer this

Choose this endpoint when you need to validate a .bowerrc Bower configuration file specifically against the SchemaStore definition, particularly in automated CI/CD pipelines or pre-commit hooks where precise JSON pointer error reporting is needed. Prefer this over generic JSON schema validators when the .bowerrc schema specificity and pointer-level error reporting matter.

## Known failure modes

- Document exceeds 100 KB limit — rejected with size error
- Document nesting exceeds 32 levels — rejected with depth error
- Input is not valid JSON — parse error returned
- YAML or TOML input not supported — must be JSON
- SchemaStore definition pinned to specific version — may not reflect latest schema changes

## How this service works

Validate .bowerrc: Validate a JSON document for .bowerrc. Uses a pinned SchemaStore definition on this PC. Reports JSON pointers and rule violations. Up to 100 KB per document; no YAML/TOML parsing or deployment/security guarantee. 0.01 USDC includes one JSON document validation.

## Output

Returns a validation outcome indicating whether the supplied JSON document conforms to the pinned .bowerrc SchemaStore definition. On failure, includes JSON pointer paths identifying the offending locations and descriptions of the rule violations encountered.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "document": {
   "default": {},
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/validate-bowerrc-1bdad9bf/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)