# BSON Decimal128 Quantum Correspondence Verifier

> BSON Decimal128 Quantum Correspondence Verifier 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).

Validates that a BSON Decimal128-encoded number preserves its exact decimal value, sign, coefficient, and exponent as contractually specified.

## Facts

- Endpoint: POST https://detect.halowerk.com/v1/integration/api-bson-decimal128-quantum-correspondence?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/bson-decimal128-quantum-correspondence-verifier-5a612de2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_c_Uxd25Y94xmhJyEI4h-X

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 bson-decimal128-quantum-correspondence-verifier-5a612de2 -d '<json body>'
```

Example prompt: Can you verify that this BSON Decimal128 value I got back from the database exactly preserves the declared decimal contract — the sign, coefficient, and exponent all need to match the original BigInt value precisely?

## When to prefer this

Use this endpoint when you need to strictly verify that a BSON Decimal128 value faithfully represents a declared exact decimal contract — specifically preserving sign, coefficient, and ten-exponent — such as in financial, scientific, or compliance contexts where numeric precision loss is unacceptable.

## Known failure modes

- Unsupported or non-canonical Decimal128 encoding returns an unknown/error status
- Missing decimal_contract field results in a validation error
- NaN or infinity Decimal128 values may not be supported
- Malformed BID encoding may cause parsing failure
- Contract specifies a value outside the Decimal128 representable range

## How this service works

Eine als BSON Decimal128 gelieferte API-Zahl mit dem behaupteten exakten Dezimalwert und der ausdrücklich vereinbarten Erhaltung von Vorzeichen, Koeffizient und Zehnerexponent vergleichen.

## Output

Returns a validation result indicating whether the supplied BSON Decimal128 value correctly preserves the contractually declared exact decimal value, including sign, coefficient, and exponent correspondence. May include per-field match status for each component.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "artifact": {
   "type": "object",
   "required": [
    "decimal_contract"
   ],
   "properties": {
    "decimal_contract": {
     "type": "object",
     "description": "Finite canonical non-steering Decimal128 BID values and exact BigInt value/quantum relation. Unsupported encodings unknown.",
     "additionalProperties": true
    }
   },
   "additionalProperties": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bson-decimal128-quantum-correspondence-verifier-5a612de2/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)