Micro Policy Version Comparison
by mahastrategies.com in Other
Review a structured policy revision before release. Compare up to 40 caller-supplied clauses per version by stable ID, text and scope; report additions, removals and changes. Checks declared chronology, not legal effect, applicability or compliance.
POST https://www.mahastrategies.com/api/v1/micro/policy-version-comparison
Last 30 days
Status and outage history · Atom feed
- Uptime
- 100%
- Response time
- 513 ms typical, 804 ms slowest 5%
- Last check
- 3 h ago
- Next check
- any minute now
How to call it
POST https://www.mahastrategies.com/api/v1/micro/policy-version-comparison
Each call costs $0.017 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/micro/policy-version-comparison
content-type: application/json
{
"after": [
{
"clauseId": "retain",
"scope": "sandbox",
"text": "Retain for three days."
}
],
"afterSequence": 2,
"afterVersion": "v2",
"before": [
{
"clauseId": "retain",
"scope": "sandbox",
"text": "Retain for seven days."
}
],
"beforeSequence": 1,
"beforeVersion": "v1",
"dataClass": "synthetic",
"policyId": "example-policy"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
after | array | Yes | |
afterSequence | integer | Yes | |
afterVersion | string | Yes | |
before | array | Yes | |
beforeSequence | integer | Yes | |
beforeVersion | string | Yes | |
dataClass | string | Yes | One of: public, synthetic. |
policyId | string | Yes |
Example response
The provider's example. We can't check it without paying.
Example response, 26 lines
{
"amountBaseUnits": "17000",
"boundaries": [
"Public or synthetic inputs only. Caller labels are declarations,…"
],
"inputDigest": "sha256:7b79acb2a65dfb30f4c116e2c4e5b4d132e30dbeb6c0205acffe42c57…",
"offerId": "policy-version-comparison",
"receiptDigest": "sha256:d30406e9a7aec34b69314254146b7865961e2d935684e8b9c1a1a9179…",
"result": {
"added": [],
"afterDigest": "sha256:104dd5865b0149480461aa21a51f2edfa4ba0d51c60aad999496b0fa4…",
"beforeDigest": "sha256:2b44232263e7fe7e523c334678c39988458d71e04c3b82c3f6d1743df…",
"changed": [
{
"clauseId": "retain",
"fields": [
"text"
]
}
],
"legalEffectDetermined": false,
"policyId": "example-policy",
"removed": []
},
"version": "maha-microproducts/0.1"
}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.017.
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/micro/policy-version-comparison' \
-H 'content-type: application/json' \
--data-raw '{"after":[{"clauseId":"retain","scope":"sandbox","text":"Retain for three days."}],"afterSequence":2,"afterVersion":"v2","before":[{"clauseId":"retain","scope":"sandbox","text":"Retain for seven days."}],"beforeSequence":1,"beforeVersion":"v1","dataClass":"synthetic","policyId":"example-policy"}'
# 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/micro/policy-version-comparison' \
-H 'content-type: application/json' \
--data-raw '{"after":[{"clauseId":"retain","scope":"sandbox","text":"Retain for three days."}],"afterSequence":2,"afterVersion":"v2","before":[{"clauseId":"retain","scope":"sandbox","text":"Retain for seven days."}],"beforeSequence":1,"beforeVersion":"v1","dataClass":"synthetic","policyId":"example-policy"}' \
| 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.017 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.017" });
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.017 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwww.mahastrategies.com%2Fapi%2Fv1%2Fmicro%2Fpolicy-version-comparison&method=POST
const res = await pay("https://www.mahastrategies.com/api/v1/micro/policy-version-comparison", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"after": [
{
"clauseId": "retain",
"scope": "sandbox",
"text": "Retain for three days."
}
],
"afterSequence": 2,
"afterVersion": "v2",
"before": [
{
"clauseId": "retain",
"scope": "sandbox",
"text": "Retain for seven days."
}
],
"beforeSequence": 1,
"beforeVersion": "v1",
"dataClass": "synthetic",
"policyId": "example-policy"
}),
});
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.017 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.017"})
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/micro/policy-version-comparison",
json={
"after": [
{
"clauseId": "retain",
"scope": "sandbox",
"text": "Retain for three days.",
},
],
"afterSequence": 2,
"afterVersion": "v2",
"before": [
{
"clauseId": "retain",
"scope": "sandbox",
"text": "Retain for seven days.",
},
],
"beforeSequence": 1,
"beforeVersion": "v1",
"dataClass": "synthetic",
"policyId": "example-policy",
},
)
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 |
|---|---|---|---|---|
| 3 h ago | Passed | 402 | 613 ms | $0.017 |
| 7 h ago | Passed | 402 | 306 ms | $0.017 |
| 11 h ago | Passed | 402 | 644 ms | $0.017 |
| 15 h ago | Passed | 402 | 394 ms | $0.017 |
| 19 h ago | Passed | 402 | 389 ms | $0.017 |
| 22 h ago | Passed | 402 | 344 ms | $0.017 |
| 27 h ago | Passed | 402 | 1.6 s | $0.017 |
| 30 h ago | Passed | 402 | 441 ms | $0.017 |
| 34 h ago | Passed | 402 | 428 ms | $0.017 |
| 37 h ago | Passed | 402 | 804 ms | $0.017 |
| 41 h ago | Passed | 402 | 752 ms | $0.017 |
| 44 h ago | Passed | 402 | 271 ms | $0.017 |
| 2 days ago | Passed | 402 | 539 ms | $0.017 |
| 2 days ago | Passed | 402 | 733 ms | $0.017 |
| 2 days ago | Passed | 402 | 538 ms | $0.017 |