Incident Notes Duplicate Record Identities
by mahastrategies.com in Developer tools
Group event identities within an incident and source revision, distinguishing equal from conflicting event fingerprints. No incident deduplication across unknown deployments. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.
https://www.mahastrategies.com/api/v1/context/incident-notes/duplicate-record-identities- Price
- $0.01
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 180 ms
- 180 ms slowest 5%
- Last check
- Passed
- 3 h ago, next any minute now
Reliability
How to call it
POST https://www.mahastrategies.com/api/v1/context/incident-notes/duplicate-record-identities
Each call costs $0.010297 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/incident-notes/duplicate-record-identities
content-type: application/json
{
"dataClass": "synthetic",
"events": [
{
"eventDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"id": "e1",
"incidentId": "i1",
"sourceRevision": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
}
],
"nonpersonalMetadata": true
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
dataClass | string | Yes | One of: public, synthetic. |
events | array | Yes | |
nonpersonalMetadata | boolean | Yes |
Example response
The provider's example. We can't check it without paying.
Example response, 29 lines
{
"data": {
"chargedAmount": "10297",
"inputHash": "sha256:44e92980d65de8f439f885476d4e324a87af319248c58ad978a5f9fad…",
"limitations": [
"Public or synthetic nonpersonal metadata only; these are caller …"
],
"productId": "incident-notes-duplicate-record-identities",
"result": {
"authoritativeSourcesConsulted": false,
"domainValidationEstablished": false,
"findings": [],
"method": "incident-notes-duplicate-record-identities/1",
"metrics": [
{
"key": "event-identity-groups",
"recordId": "cohort",
"value": "1"
}
]
},
"resultHash": "sha256:2a932afde38e552d694cc21c45169338c52bb3047f6dde1b4c194360d…",
"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.010297.
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/incident-notes/duplicate-record-identities' \
-H 'content-type: application/json' \
--data-raw '{"dataClass":"synthetic","events":[{"eventDigest":"sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","id":"e1","incidentId":"i1","sourceRevision":"sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"}],"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/incident-notes/duplicate-record-identities' \
-H 'content-type: application/json' \
--data-raw '{"dataClass":"synthetic","events":[{"eventDigest":"sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","id":"e1","incidentId":"i1","sourceRevision":"sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"}],"nonpersonalMetadata":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.010297 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.010297" });
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.010297 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwww.mahastrategies.com%2Fapi%2Fv1%2Fcontext%2Fincident-notes%2Fduplicate-record-identities&method=POST
const res = await pay("https://www.mahastrategies.com/api/v1/context/incident-notes/duplicate-record-identities", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"dataClass": "synthetic",
"events": [
{
"eventDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"id": "e1",
"incidentId": "i1",
"sourceRevision": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
}
],
"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.010297 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.010297"})
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/incident-notes/duplicate-record-identities",
json={
"dataClass": "synthetic",
"events": [
{
"eventDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"id": "e1",
"incidentId": "i1",
"sourceRevision": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
},
],
"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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Passed | 402 | 180 ms | $0.01 |
| 7 h ago | Passed | 402 | 223 ms | $0.01 |
| 16 h ago | Passed | 402 | 178 ms | $0.01 |