Religion Name Disambiguation
by Tamil Divine-Name Disambiguation in Search & web
Resolve an exact supported Tamil divine-name spelling to source-scoped records in a pinned registry. Keeps ambiguity and name coincidence explicit. No fuzzy universal synonym search, full source text or theological certification. New modular adapter: retained result recovery for 24 hours, minimal receipt metadata for 90 days. Existing live route unchanged.
https://www.mahastrategies.com/api/v1/library/religion/name-disambiguation- Price
- $0.014
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 209 ms
- 2.7 s slowest 5%
- Last check
- Passed
- 3 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://www.mahastrategies.com/api/v1/library/religion/name-disambiguation
Each call costs $0.014002 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/library/religion/name-disambiguation
content-type: application/json
{
"dataClass": "public",
"expectedRegistryDigest": "sha256:43e894685dfb4d8ca91ce6069cc182f273af4398e739bb388740f4dfd1f9a56a",
"name": "Mayon"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
dataClass | string | Yes | One of: public, synthetic. |
expectedRegistryDigest | string | Yes | |
name | string | Yes |
Example response
The provider's example. We can't check it without paying.
Example response, 39 lines
{
"data": {
"chargedAmount": "14002",
"inputHash": "sha256:bdc148e5edfee861fc3c19b913f77657fb4f441b1fdeee1bee5c87ad9…",
"limitations": [
"Public or synthetic inputs only. Caller labels are declarations,…"
],
"productId": "divine-name-disambiguation",
"result": {
"candidates": [
{
"boundary": "This identifies a research subject, not every similarly spelled …",
"entity": "Māyōṉ (Tamil literary-religious figure)",
"evidence": [
{
"boundary": "This is one scholar’s reconstruction from literary evidence. Its…",
"frame": "scholarly-interpretation",
"locator": "pp. 73–84: section I; section II introduction; section II.A.1–4;…",
"rightsBasis": "Open university repository copy; paraphrase and limited quotatio…",
"sourceId": "yamashita-1995-mayon-tirumal",
"url": "https://repository.dl.itc.u-tokyo.ac.jp/record/27137/files/ioc12…"
}
],
"relationship": "source-scoped-subject"
}
],
"registryDigest": "sha256:43e894685dfb4d8ca91ce6069cc182f273af4398e739bb388740f4dfd…",
"state": "ambiguous",
"universalIdentityEstablished": false
},
"resultHash": "sha256:d28a4b991c4158170b644acb1bb0fbe2501ea61629aa717ffa0b1ce80…",
"sourceContractAmount": "14000",
"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.014002.
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/library/religion/name-disambiguation' \
-H 'content-type: application/json' \
--data-raw '{"dataClass":"public","expectedRegistryDigest":"sha256:43e894685dfb4d8ca91ce6069cc182f273af4398e739bb388740f4dfd1f9a56a","name":"Mayon"}'
# 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/library/religion/name-disambiguation' \
-H 'content-type: application/json' \
--data-raw '{"dataClass":"public","expectedRegistryDigest":"sha256:43e894685dfb4d8ca91ce6069cc182f273af4398e739bb388740f4dfd1f9a56a","name":"Mayon"}' \
| 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.014002 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.014002" });
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.014002 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwww.mahastrategies.com%2Fapi%2Fv1%2Flibrary%2Freligion%2Fname-disambiguation&method=POST
const res = await pay("https://www.mahastrategies.com/api/v1/library/religion/name-disambiguation", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"dataClass": "public",
"expectedRegistryDigest": "sha256:43e894685dfb4d8ca91ce6069cc182f273af4398e739bb388740f4dfd1f9a56a",
"name": "Mayon"
}),
});
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.014002 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.014002"})
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/library/religion/name-disambiguation",
json={
"dataClass": "public",
"expectedRegistryDigest": "sha256:43e894685dfb4d8ca91ce6069cc182f273af4398e739bb388740f4dfd1f9a56a",
"name": "Mayon",
},
)
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 | 217 ms | $0.014 |
| 8 h ago | Passed | 402 | 165 ms | $0.014 |
| 13 h ago | Passed | 402 | 2.7 s | $0.014 |
| 18 h ago | Passed | 402 | 335 ms | $0.014 |
| 22 h ago | Passed | 402 | 176 ms | $0.014 |
Show 1 older checks
| 27 h ago | Passed | 402 | 209 ms | $0.014 |