# ECMAScript Object Binding Rest Copy Exclusion Detector

> ECMAScript Object Binding Rest Copy Exclusion Detector is a paid API for AI agents from detect.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-11-04).

Analyzes an ECMAScript object destructuring to identify which own enumerable keys will remain in the rest object after bindings and inheritance exclusions, without exposing field values.

## Facts

- Endpoint: POST https://detect.halowerk.com/u/ecmascript-object-binding-rest-copy-exclusion?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ecmascript-object-binding-rest-copy-exclusion-detector-b915ed93
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QoH5UmwB96FtVZjrklIHq

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 ecmascript-object-binding-rest-copy-exclusion-detector-b915ed93 -d '<json body>'
```

Example prompt: Before I refactor this destructuring pattern, check which own enumerable keys would actually end up in the rest object and which get excluded because of explicit bindings or prototype inheritance — use this URL for the scenario: https://example.com/my-destructuring-case

## When to prefer this

Choose this endpoint when you need a precise, value-safe static analysis of which own enumerable keys survive into the rest object of an ECMAScript object destructuring — specifically when you need to distinguish between keys excluded by explicit bindings versus those absent due to prototype inheritance, without any property values being leaked. Useful for code refactoring validation, transpiler pre-checks, and educational tooling around ES6+ destructuring semantics.

## Known failure modes

- Invalid or unreachable URL returns an error indicating the resource could not be fetched
- URL does not point to a valid ECMAScript destructuring scenario, resulting in a parse or schema validation error
- Network timeout if the referenced URL is slow or unresponsive
- Scenario describes non-object destructuring (e.g. array patterns), which is out of scope

## How this service works

Prüft vor dem Umbau einer Objekt-Destrukturierung, welche eigenen aufzählbaren Schlüssel tatsächlich im Restobjekt verbleiben und welche wegen Bindungen oder Vererbung fehlen, ohne Feldwerte herauszugeben.

## Output

Returns a structured report of which own enumerable keys will be present in the rest object after destructuring, which are excluded because they are explicitly named in the binding pattern, and which are absent due to prototype inheritance — without disclosing any property values.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri",
   "pattern": "^https?://"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ecmascript-object-binding-rest-copy-exclusion-detector-b915ed93/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from detect.halowerk.com](https://www.zero.xyz/host/detect.halowerk.com/llms.txt)