# Protein Measurements - Reference Integrity Map

> Protein Measurements - Reference Integrity Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035155/call, status unknown (last checked 2026-10-20).

Binds protein measurement rows to exact declared protein/isoform/sequence-revision/digest identifiers to verify reference integrity without fetching or inferring sequence identity or structure.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/protein-measurements/reference-integrity-map?utm_source=zero.xyz
- Price: $0.035155/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/protein-measurements-reference-integrity-map-25df4bf9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Znyyaw3xpFGl4Oq-OHM5n

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 protein-measurements-reference-integrity-map-25df4bf9 -d '<json body>'
```

Example prompt: I have up to 20 protein measurement rows and 5 protein declarations — all marked as public data with nonpersonalMetadata true — can you run a reference integrity check to confirm each measurement row is correctly bound to its declared protein isoform, sequence revision, and digest without inferring anything about the sequence itself?

## When to prefer this

Use this endpoint when you need to enforce strict reference binding between protein measurement records and their declared protein/isoform/sequence-revision/digest identities — especially for audit, compliance, or pre-publication integrity checks on small batches (up to 32 rows/proteins). It is not appropriate when you need sequence inference, structural analysis, or external database lookups.

## Known failure modes

- Exceeding 32 rows or 32 proteins returns a validation error
- Missing nonpersonalMetadata:true field causes rejection
- Invalid or unsupported dataClass enum value returns an error
- Malformed protein or row declarations result in binding failures
- Digest/revision mismatches flagged as integrity failures rather than system errors
- Missing required fields in rows or proteins arrays cause schema validation errors

## How this service works

Bind measurements to exact protein/isoform/sequence-revision/digest declarations without fetching or inferring sequence identity, structure or Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a reference integrity map that indicates, for each submitted measurement row, whether it is correctly bound to the declared protein, isoform, sequence revision, and digest pin. Results reflect only the supplied declarations — no external sequence fetching, structural inference, or independent certification is performed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "proteins": {
   "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/protein-measurements-reference-integrity-map-25df4bf9/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)