# Procurement Notices - Export Semantic Parity

> Procurement Notices - Export Semantic Parity is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.039335/call, status unknown (last checked 2026-10-16).

Compares two sets of parsed procurement notice record projections for semantic parity, preserving all buyer/notice/kind/jurisdiction/revision pins while ignoring record order.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/procurement-notices/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039335/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/procurement-notices-export-semantic-parity-bfd32db5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RnQ9u9qAsZQsj-5Kz3z5t

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 procurement-notices-export-semantic-parity-bfd32db5 -d '<json body>'
```

Example prompt: Compare these two procurement notice record sets — the before list has up to 32 entries from last week's export and the after list has the revised version — and tell me if they are semantically equivalent with all buyer, jurisdiction, and revision pins preserved, treating the data as public.

## When to prefer this

Use this endpoint when you need to verify semantic equivalence between two versions of a procurement notice record set while preserving all pinned fields (buyer, notice kind, jurisdiction, revision) and ignoring record ordering. Prefer it over raw-byte comparison tools when structural reordering is expected but semantic content must remain identical. It is not a certification service for underlying procurement artifacts.

## Known failure modes

- Input arrays exceed 32-item limit causing validation error
- dataClass not set to 'public' or 'synthetic' causing rejection
- nonpersonalMetadata not set to boolean true causing request failure
- Mismatched pin structures causing ambiguous parity result
- Empty or malformed record projections returning inconclusive comparison

## How this service works

Compare parsed typed record projections, preserving all pins and scope while ignoring order; not raw-byte equality or proof of the underlying artifact for buyer/notice/kind/jurisdiction/revision-pinned procurement Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a semantic parity assessment indicating whether the before and after procurement notice record projections are equivalent when order is ignored, with details on whether all typed pins (buyer, notice kind, jurisdiction, revision) are preserved. Does not perform raw-byte comparison or certify the underlying procurement artifacts.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/procurement-notices-export-semantic-parity-bfd32db5/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)