# Protein Measurements Provenance Edge Audit

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

Binds protein measurements to their exact dataset, protein, isoform, sequence, and method source by auditing provenance edges on supplied records.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/protein-measurements/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045314/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/protein-measurements-provenance-edge-audit-f7f361a4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IubARUWhSdXPUAiL0YiFF

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-provenance-edge-audit-f7f361a4 -d '<json body>'
```

Example prompt: I have 15 protein measurement rows from a public dataset and I need to audit their provenance — can you bind each row to its exact dataset, protein isoform, sequence, and method source so I can confirm full traceability?

## When to prefer this

Use this endpoint when you need to formally audit and document the provenance chain of protein measurement data — specifically binding rows to dataset, isoform, sequence, and method source. Prefer this over generic data validation when the goal is scientific traceability for proteomics data prior to publication, regulatory submission, or downstream analysis pipelines.

## Known failure modes

- Rows array exceeds 32 item limit — request rejected
- Sources array exceeds 32 item limit — request rejected
- dataClass not set to 'public' or 'synthetic' — validation error
- nonpersonalMetadata not set to true (const constraint) — request rejected
- Insufficient or ambiguous source references preventing provenance binding
- Payment of 0.045314 USDC not fulfilled — 402 response

## How this service works

Bind protein measurements to exact dataset/protein/isoform/sequence/method source Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns provenance bindings that link each submitted protein measurement row to its exact dataset, protein identifier, isoform, sequence, and measurement method source, along with any audit flags or attribution gaps detected in the supplied records.

## 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/protein-measurements-provenance-edge-audit-f7f361a4/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)