# Alloy Measurements Source Coverage Map

> Alloy Measurements Source Coverage Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035189/call, status unknown (last checked 2026-10-25).

Binds alloy measurement records to an owner/subject/revision/content/source frame and maps declared source coverage, producing hash-keyed coverage declarations for audit and evidence review.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/alloy-measurements/source-coverage-map?utm_source=zero.xyz
- Price: $0.035189/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/alloy-measurements-source-coverage-map-7c000cb1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nmad141VU_B7VqJ8WRT15

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 alloy-measurements-source-coverage-map-7c000cb1 -d '<json body>'
```

Example prompt: I have 12 alloy measurement rows and 5 source references I need to bind into a source coverage map — the data is public and contains no personal metadata, so mark nonpersonalMetadata as true. Can you run the source coverage mapping on them?

## When to prefer this

Use this endpoint when you need to formally bind alloy measurement records to their declared provenance frame (owner, subject, revision, content, source) for audit, evidence, or compliance purposes. It is best suited for pre-certification documentation workflows where declared source coverage — not independent certification — is the required output. Prefer this over generic data-linking tools when working specifically with alloy lot/method/composition-basis records in public or synthetic data classes.

## Known failure modes

- rows or sources arrays outside 1–32 item bounds returns validation error
- dataClass value outside allowed enum ('public','synthetic') causes rejection
- nonpersonalMetadata not set to boolean true causes request rejection
- malformed row or source objects cause binding failure with descriptive error
- hash collisions in declared identifiers may produce ambiguous coverage entries

## How this service works

Bind record references to an exact owner/subject/revision/content/source frame; hash-shaped strings are declarations, not independently verified source bytes for alloy lot/method/composition-basis Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a hash-keyed source coverage map that binds each supplied measurement row to its declared owner, subject, revision, content, and source frame. Declarations are provided as hash-shaped strings representing stated provenance, not independently verified source bytes. The response includes binding status per row and coverage annotations per source reference.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/alloy-measurements-source-coverage-map-7c000cb1/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)