78trust / 100

Tool Context Required Field Coverage

by mahastrategies.com in Onchain & crypto

x402 APIPassing, checked 50 min ago

Report missing tool, contract and argument digest declarations in supplied call-context metadata. No arguments, credentials, tool execution or model context is loaded. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

POST https://www.mahastrategies.com/api/v1/context/tool-context/required-field-coverage

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
197 ms typical, 197 ms slowest 5%
Last check
50 min ago
Next check
any minute now

How to call it

POST https://www.mahastrategies.com/api/v1/context/tool-context/required-field-coverage

Each call costs $0.010095 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/context/tool-context/required-field-coverage
content-type: application/json

{
  "calls": [
    {
      "argsDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
      "contractDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
      "id": "c1",
      "toolId": "tool1"
    }
  ],
  "dataClass": "synthetic",
  "nonpersonalMetadata": true
}

Parameters

ParameterTypeRequiredDescription
callsarrayYes
dataClassstringYes One of: public, synthetic.
nonpersonalMetadatabooleanYes

Example response

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

Example response, 29 lines
{
  "data": {
    "chargedAmount": "10095",
    "inputHash": "sha256:f89977c007b5924b12f1e9788fe8005d83f7e697347fee81de8f609b0…",
    "limitations": [
      "Public or synthetic nonpersonal metadata only; these are caller …"
    ],
    "productId": "tool-context-required-field-coverage",
    "result": {
      "authoritativeSourcesConsulted": false,
      "domainValidationEstablished": false,
      "findings": [],
      "method": "tool-context-required-field-coverage/1",
      "metrics": [
        {
          "key": "missing-tool-fields",
          "recordId": "tool",
          "value": "0"
        }
      ]
    },
    "resultHash": "sha256:5115317a2eacc638e0909cb45e2580bb6058796c7800e4fbaf2432830…",
    "version": "maha-typed-metadata-audit/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.010095.

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/context/tool-context/required-field-coverage' \
  -H 'content-type: application/json' \
  --data-raw '{"calls":[{"argsDigest":"sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","contractDigest":"sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","id":"c1","toolId":"tool1"}],"dataClass":"synthetic","nonpersonalMetadata":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/context/tool-context/required-field-coverage' \
  -H 'content-type: application/json' \
  --data-raw '{"calls":[{"argsDigest":"sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","contractDigest":"sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","id":"c1","toolId":"tool1"}],"dataClass":"synthetic","nonpersonalMetadata":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.010095 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.010095" });
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.010095 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwww.mahastrategies.com%2Fapi%2Fv1%2Fcontext%2Ftool-context%2Frequired-field-coverage&method=POST
const res = await pay("https://www.mahastrategies.com/api/v1/context/tool-context/required-field-coverage", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "calls": [
      {
        "argsDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
        "contractDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
        "id": "c1",
        "toolId": "tool1"
      }
    ],
    "dataClass": "synthetic",
    "nonpersonalMetadata": 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.010095 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.010095"})
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/context/tool-context/required-field-coverage",
        json={
            "calls": [
                {
                    "argsDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
                    "contractDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
                    "id": "c1",
                    "toolId": "tool1",
                },
            ],
            "dataClass": "synthetic",
            "nonpersonalMetadata": 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
50 min agoPassed402213 ms$0.01
10 h agoPassed402197 ms$0.01