Neural Distribution Drift
by Summary feature drift report in Security & trust
Compare up to 24 public/synthetic feature summaries: mean differences, reference-standardized shifts and variance ratios. Explicitly flags zero reference variance. Counts and variance convention are declared, not verified; not a distribution test or clinical inference. No raw EEG, participant identifiers or full participant signals. 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/verify/neural/distribution-drift
Last 30 days
Status and outage history · Atom feed
- Uptime
- 100%
- Response time
- 201 ms typical, 201 ms slowest 5%
- Last check
- 9 h ago
- Next check
- any minute now
How to call it
POST https://www.mahastrategies.com/api/v1/verify/neural/distribution-drift
Each call costs $0.010027 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/verify/neural/distribution-drift
content-type: application/json
{
"dataClass": "synthetic",
"features": [
{
"current": {
"count": 100,
"mean": "5",
"variance": "8"
},
"name": "band-power",
"reference": {
"count": 100,
"mean": "2",
"variance": "4"
}
}
],
"maxStandardizedMeanShift": "1",
"varianceConvention": "population"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
dataClass | string | Yes | One of: public, synthetic. |
features | array | Yes | |
maxStandardizedMeanShift | string | Yes | |
varianceConvention | string | Yes | One of: population, sample. |
Example response
The provider's example. We can't check it without paying.
Example response, 32 lines
{
"data": {
"chargedAmount": "10027",
"inputHash": "sha256:c39173f5b0424174a53137b2d599aa0e6871a5798923dc742cb7711d6…",
"limitations": [
"Public or synthetic inputs only. Caller labels are declarations,…"
],
"productId": "feature-distribution-drift",
"result": {
"dataClass": "synthetic",
"distributionTestPerformed": false,
"features": [
{
"meanDifference": "3",
"name": "band-power",
"standardizedMeanShift": "1.5",
"state": "mean-shift-flagged",
"varianceRatio": "2"
}
],
"participantSignalsIncluded": false,
"varianceConvention": "population"
},
"resultHash": "sha256:6d1eb6b0bbadf11d4a5b861487c5644874eb07e81faf5c63b82fc69b9…",
"sourceContractAmount": "43000",
"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.010027.
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/verify/neural/distribution-drift' \
-H 'content-type: application/json' \
--data-raw '{"dataClass":"synthetic","features":[{"current":{"count":100,"mean":"5","variance":"8"},"name":"band-power","reference":{"count":100,"mean":"2","variance":"4"}}],"maxStandardizedMeanShift":"1","varianceConvention":"population"}'
# 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/verify/neural/distribution-drift' \
-H 'content-type: application/json' \
--data-raw '{"dataClass":"synthetic","features":[{"current":{"count":100,"mean":"5","variance":"8"},"name":"band-power","reference":{"count":100,"mean":"2","variance":"4"}}],"maxStandardizedMeanShift":"1","varianceConvention":"population"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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.010027 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.010027" });
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.010027 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwww.mahastrategies.com%2Fapi%2Fv1%2Fverify%2Fneural%2Fdistribution-drift&method=POST
const res = await pay("https://www.mahastrategies.com/api/v1/verify/neural/distribution-drift", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"dataClass": "synthetic",
"features": [
{
"current": {
"count": 100,
"mean": "5",
"variance": "8"
},
"name": "band-power",
"reference": {
"count": 100,
"mean": "2",
"variance": "4"
}
}
],
"maxStandardizedMeanShift": "1",
"varianceConvention": "population"
}),
});
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.010027 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.010027"})
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/verify/neural/distribution-drift",
json={
"dataClass": "synthetic",
"features": [
{
"current": {
"count": 100,
"mean": "5",
"variance": "8",
},
"name": "band-power",
"reference": {
"count": 100,
"mean": "2",
"variance": "4",
},
},
],
"maxStandardizedMeanShift": "1",
"varianceConvention": "population",
},
)
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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 9 h ago | Passed | 402 | 201 ms | $0.01 |