78trust / 100

Quantum Surface Code Resource Scenario

by Surface-code resource scenario in Developer tools

x402 APIPassing, checked 4 h ago

Calculate a surface-code resource scenario under an explicitly named layout and supplied error assumptions. For planning; not a demonstrated physical implementation. 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/quantum/surface-code-resource-scenario
Price
$0.1
per call in USDC
Uptime
100%
last 30 days
Response time
225 ms
4.7 s slowest 5%
Last check
Passed
4 h 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 · Watch with other listings

How to call it

POST https://www.mahastrategies.com/api/v1/compute/quantum/surface-code-resource-scenario

Each call costs $0.100016 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/quantum/surface-code-resource-scenario
content-type: application/json

{
  "cycles": 100,
  "dataClass": "synthetic",
  "distance": 5,
  "logicalQubits": 2,
  "physicalError": 0.001,
  "prefactor": 0.1,
  "threshold": 0.01
}

Parameters

ParameterTypeRequiredDescription
cyclesintegerYes
dataClassstringYes One of: public, synthetic.
distanceintegerYes
logicalQubitsintegerYes
physicalErrornumberYes
prefactornumberYes
thresholdnumberYes

Example response

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

Example response, 32 lines
{
  "data": {
    "chargedAmount": "100016",
    "inputHash": "sha256:7a5002685cca6dfb2a6fb74d7198343eee105fbf4a1415bc657160dc0…",
    "limitations": [
      "Public or synthetic inputs only. Caller labels are declarations,…"
    ],
    "productId": "quantum-surface-code-resource-scenario",
    "result": {
      "findings": {
        "assumptions": [
          "rotated patches: 2*d^2-1 physical qubits per logical qubit"
        ],
        "errorPerLogicalCycle": 0.0001,
        "physicalQubits": 98,
        "unionBoundFailure": 0.02
      },
      "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:68ec39bb1a9e5d55e2a17198edd7b0e00947c64ad4bf8c0bd18f7e5c0…",
    "sourceContractAmount": "99000",
    "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.100016.

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/quantum/surface-code-resource-scenario' \
  -H 'content-type: application/json' \
  --data-raw '{"cycles":100,"dataClass":"synthetic","distance":5,"logicalQubits":2,"physicalError":0.001,"prefactor":0.1,"threshold":0.01}'

# 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/quantum/surface-code-resource-scenario' \
  -H 'content-type: application/json' \
  --data-raw '{"cycles":100,"dataClass":"synthetic","distance":5,"logicalQubits":2,"physicalError":0.001,"prefactor":0.1,"threshold":0.01}' \
  | 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.100016 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.100016" });
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.100016 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwww.mahastrategies.com%2Fapi%2Fv1%2Fcompute%2Fquantum%2Fsurface-code-resource-scenario&method=POST
const res = await pay("https://www.mahastrategies.com/api/v1/compute/quantum/surface-code-resource-scenario", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "cycles": 100,
    "dataClass": "synthetic",
    "distance": 5,
    "logicalQubits": 2,
    "physicalError": 0.001,
    "prefactor": 0.1,
    "threshold": 0.01
  }),
});
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.100016 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.100016"})
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/quantum/surface-code-resource-scenario",
        json={
            "cycles": 100,
            "dataClass": "synthetic",
            "distance": 5,
            "logicalQubits": 2,
            "physicalError": 0.001,
            "prefactor": 0.1,
            "threshold": 0.01,
        },
    )
    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
4 h agoPassed4024.7 s$0.1
9 h agoPassed402362 ms$0.1
13 h agoPassed402225 ms$0.1
17 h agoPassed402196 ms$0.1
21 h agoPassed402193 ms$0.1