78trust / 100

Biology Qpcr Run Quality

by qPCR run-quality check in Other

x402 APIPassing, checked 38 min ago

Check supplied Ct replicates, efficiency and control declarations against fixed research QC bands; report Ct SD and failed conditions. No diagnostic validation. New modular adapter: retained result recovery for 24 hours, minimal receipt metadata for 90 days. Existing live route unchanged.

POST
https://www.mahastrategies.com/api/v1/compute/biology/qpcr-run-quality
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
192 ms
216 ms slowest 5%
Last check
Passed
38 min ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

How to call it

POST https://www.mahastrategies.com/api/v1/compute/biology/qpcr-run-quality

Each call costs $0.010042 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://www.mahastrategies.com/api/v1/compute/biology/qpcr-run-quality
content-type: application/json

{
  "ct": [
    22,
    22.2,
    22.1
  ],
  "dataClass": "synthetic",
  "efficiency": 1,
  "meltSinglePeak": true,
  "noRTNegative": true,
  "noTemplateNegative": true,
  "referenceStable": true
}

Parameters

ParameterTypeRequiredDescription
ctarrayYes
dataClassstringYes One of: public, synthetic.
efficiencynumberYes
meltSinglePeakbooleanYes
noRTNegativebooleanYes
noTemplateNegativebooleanYes
referenceStablebooleanYes

Example response

The provider's example. We can't check it without paying.

Example response, 31 lines
{
  "data": {
    "chargedAmount": "10042",
    "inputHash": "sha256:ce837e5ed4d4bd86f7a5c37959631499e2f0bae9ff126faaf3a1a0d1c…",
    "limitations": [
      "Public or synthetic inputs only. Caller labels are declarations,…"
    ],
    "productId": "biology-qpcr-run-quality",
    "result": {
      "findings": {
        "assayValidated": false,
        "ctSD": 0.1,
        "declarationsComplete": true,
        "issues": [],
        "meanCt": 22.1
      },
      "limitations": [
        "Public or synthetic research inputs only; no patient, personal g…"
      ],
      "methodVersion": "maha-science50/1.0.0",
      "numericPrecision": "IEEE754-double; finite outputs rounded to 12 significant digits"
    },
    "resultHash": "sha256:31efd7595e8a4aca2997b4a8e1d896a5229332edc4156fdd3057d3714…",
    "sourceContractAmount": "42001",
    "version": "maha-legacy-adapter/1"
  },
  "proof": {
    "settlement_id": "0x00000000000000000000000000000000000000000000000000000000000000…"
  },
  "success": true
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.010042.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://www.mahastrategies.com/api/v1/compute/biology/qpcr-run-quality' \
  -H 'content-type: application/json' \
  --data-raw '{"ct":[22,22.2,22.1],"dataClass":"synthetic","efficiency":1,"meltSinglePeak":true,"noRTNegative":true,"noTemplateNegative":true,"referenceStable":true}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://www.mahastrategies.com/api/v1/compute/biology/qpcr-run-quality' \
  -H 'content-type: application/json' \
  --data-raw '{"ct":[22,22.2,22.1],"dataClass":"synthetic","efficiency":1,"meltSinglePeak":true,"noRTNegative":true,"noTemplateNegative":true,"referenceStable":true}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.010042 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.010042" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.010042 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwww.mahastrategies.com%2Fapi%2Fv1%2Fcompute%2Fbiology%2Fqpcr-run-quality&method=POST
const res = await pay("https://www.mahastrategies.com/api/v1/compute/biology/qpcr-run-quality", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "ct": [
      22,
      22.2,
      22.1
    ],
    "dataClass": "synthetic",
    "efficiency": 1,
    "meltSinglePeak": true,
    "noRTNegative": true,
    "noTemplateNegative": true,
    "referenceStable": true
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.010042 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.010042"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://www.mahastrategies.com/api/v1/compute/biology/qpcr-run-quality",
        json={
            "ct": [
                22,
                22.2,
                22.1,
            ],
            "dataClass": "synthetic",
            "efficiency": 1,
            "meltSinglePeak": True,
            "noRTNegative": True,
            "noTemplateNegative": True,
            "referenceStable": True,
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
38 min agoPassed402319 ms$0.01
5 h agoPassed402216 ms$0.01
9 h agoPassed402192 ms$0.01
19 h agoPassed402164 ms$0.01