Datasets Schema Evolution
by Dataset Schema Evolution Plan in Security & trust
Compare old/new field declarations for directional breaking changes. No semantic-equivalence proof or data migration.
POST https://www.mahastrategies.com/api/v1/verify/datasets/schema-evolution
Last 30 days
Status and outage history · Atom feed
- Uptime
- 100%
- Response time
- 186 ms typical, 186 ms slowest 5%
- Last check
- 12 min ago
- Next check
- in 18 min
How to call it
POST https://www.mahastrategies.com/api/v1/verify/datasets/schema-evolution
Each call costs $0.010064 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/datasets/schema-evolution
content-type: application/json
{
"after": [
{
"name": "x",
"nullable": true,
"required": false,
"type": "number",
"unit": "m"
}
],
"before": [
{
"name": "x",
"nullable": true,
"required": false,
"type": "integer",
"unit": "m"
}
],
"dataClass": "synthetic",
"rejectExtraFields": true
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
after | array | Yes | |
before | array | Yes | |
dataClass | string | Yes | One of: synthetic, public. |
rejectExtraFields | boolean | Yes |
Example response
The provider's example. We can't check it without paying.
Example response, 29 lines
{
"data": {
"inputHash": "sha256:69d74e38ac36abfcbc0a1791e309d5bdc582069ea77562af4b60b4ef8…",
"limitations": [
"Schema and integrity checks do not certify scientific truth, com…"
],
"productId": "dataset-schema-evolution-plan",
"receiptDigest": "sha256:89f464fce8dd2b7c52eff1004eba74848bdf5ea8c95082d19c7fa7c08…",
"result": {
"changes": [
{
"breaksDeclaredOldRecords": false,
"field": "x",
"kind": "type_changed"
}
],
"declaredCompatibility": "no_declared_break",
"direction": "new_schema_accepts_records_per_old_declaration",
"recordsExecutedAgainstSchema": false,
"semanticEquivalenceProved": false
},
"resultHash": "sha256:f3d47c02b1bada2a560f81065574bb8c571af3647a598488141ccbc7f…",
"version": "maha-workflow/1.0.0"
},
"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.010064.
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/datasets/schema-evolution' \
-H 'content-type: application/json' \
--data-raw '{"after":[{"name":"x","nullable":true,"required":false,"type":"number","unit":"m"}],"before":[{"name":"x","nullable":true,"required":false,"type":"integer","unit":"m"}],"dataClass":"synthetic","rejectExtraFields":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/verify/datasets/schema-evolution' \
-H 'content-type: application/json' \
--data-raw '{"after":[{"name":"x","nullable":true,"required":false,"type":"number","unit":"m"}],"before":[{"name":"x","nullable":true,"required":false,"type":"integer","unit":"m"}],"dataClass":"synthetic","rejectExtraFields":true}' \
| 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.010064 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.010064" });
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.010064 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwww.mahastrategies.com%2Fapi%2Fv1%2Fverify%2Fdatasets%2Fschema-evolution&method=POST
const res = await pay("https://www.mahastrategies.com/api/v1/verify/datasets/schema-evolution", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"after": [
{
"name": "x",
"nullable": true,
"required": false,
"type": "number",
"unit": "m"
}
],
"before": [
{
"name": "x",
"nullable": true,
"required": false,
"type": "integer",
"unit": "m"
}
],
"dataClass": "synthetic",
"rejectExtraFields": 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.010064 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.010064"})
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/datasets/schema-evolution",
json={
"after": [
{
"name": "x",
"nullable": True,
"required": False,
"type": "number",
"unit": "m",
},
],
"before": [
{
"name": "x",
"nullable": True,
"required": False,
"type": "integer",
"unit": "m",
},
],
"dataClass": "synthetic",
"rejectExtraFields": 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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 12 min ago | Passed | 402 | 194 ms | $0.01 |
| 10 h ago | Passed | 402 | 186 ms | $0.01 |