# Planetary Measurements - Declared Bound Audit

> Planetary Measurements - Declared Bound Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.01016/call, status unknown (last checked 2026-10-16).

Validates that exact finite planetary measurement values fall within caller-supplied quantity/unit bounds, auditing declared records without independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/planetary-measurements/declared-bound-audit?utm_source=zero.xyz
- Price: $0.01016/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/planetary-measurements-declared-bound-audit-ab77424e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xqRKQaHrVrBrVmXB4SWbB

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 planetary-measurements-declared-bound-audit-ab77424e -d '<json body>'
```

Example prompt: Check whether these 5 public planetary measurement records all fall within my declared bounds — mass must be no more than 1.989e30 kg and radius no more than 696340 km — and give me a full declared-bound audit report.

## When to prefer this

Choose this endpoint when you need to audit declared planetary measurement records against explicit caller-supplied quantity and unit bounds in a single batch call, particularly for public or synthetic (non-personal) data. It is best suited for compliance-style audits where you supply both the measurements and the acceptable bounds and want a structured comparison result. It is not appropriate for independent third-party certification, personal data, or free-form celestial data queries.

## Known failure modes

- Invalid or non-finite measurement values cause rejection
- More than 32 measurements or bounds items exceed array limits
- Mismatched units between measurements and bounds produce audit errors
- Missing required nonpersonalMetadata true flag causes request failure
- Unsupported dataClass value outside public/synthetic enum causes validation error
- Empty measurements or bounds arrays (below minItems:1) are rejected

## How this service works

Compare exact finite values with one matching inclusive caller-supplied quantity/unit bound in the full declared Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a declared-bound audit report comparing each supplied planetary measurement value against the caller-specified inclusive quantity/unit bounds, indicating whether each measurement matches, exceeds, or falls below the declared bounds. The response covers all supplied measurement-bound pairs (up to 32 each) and is scoped to the declared record analysis only — no independent certification is performed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "bounds": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "measurements": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/planetary-measurements-declared-bound-audit-ab77424e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.mahastrategies.com](https://www.zero.xyz/host/www.mahastrategies.com/llms.txt)