80trust / 100

Tw Localize Check

by TariffMonkee in Documents & files

x402 APIPassing, checked 2 h ago

Taiwan localization check for Traditional Chinese text: flags mainland (PRC) wording in traditional characters that still reads as non-Taiwanese, with the Taiwan-correct replacement, category, severity and reason per flag. Optional fix=true returns corrected text. Uses a curated glossary of 47 terms; a judgment layer on top of simplified-to-traditional conversion, not a substitute for it.

POST
https://tariffmonkee.com/paid/tw-localize-check
Price
$0.02
per call in USDC
Uptime
100%
last 30 days
Response time
164 ms
1.9 s slowest 5%
Last check
Passed
2 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://tariffmonkee.com/paid/tw-localize-check

Each call costs $0.02 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://tariffmonkee.com/paid/tw-localize-check
content-type: application/json

{
  "fix": true,
  "text": "請在軟件中打開視頻會議,連接公司網絡後把數據庫備份到硬盤,再用短信通知服務器管理員。打印機和鼠標放在便利店旁的辦公室。"
}

Parameters

ParameterTypeRequiredDescription
fixbooleanNoIf true, also return a corrected version of the text with flagged terms replaced.
textstringYesTraditional Chinese text to check for mainland/Hong Kong wording.

Example response

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

Example response, 51 lines
{
  "corrected_text": "請在軟體中打開視訊會議,連接公司網路後把資料庫備份到硬碟,再用簡訊通知伺服器管理員。印表機和滑鼠放在便利商店旁的辦公室。",
  "disclaimer": "Flags known mainland/Hong Kong wording rendered in Traditional Chinese characters, with a Taiwan-correct replacement and a plain-language reason. This is a curated glossary, not a full linguistic model: it will miss any term not yet catalogued, and it does zero grammar or register analysis beyond th...",
  "flag_count": 10,
  "flags": [
    {
      "category": "tech",
      "context_note": null,
      "occurrences": 1,
      "positions": [
        2
      ],
      "rationale": "Mainland wording for \"software\" even when rendered in traditional characters; Taiwan's standard term is 軟體.",
      "severity": "high",
      "taiwan_term": "軟體",
      "term": "軟件"
    },
    {
      "category": "tech",
      "context_note": null,
      "occurrences": 1,
      "positions": [
        7
      ],
      "rationale": "Mainland wording for \"video conference\"; Taiwan's standard term is 視訊會議.",
      "severity": "high",
      "taiwan_term": "視訊會議",
      "term": "視頻會議"
    },
    {
      "category": "tech",
      "context_note": "網絡 is legitimate Taiwan usage for an abstract non-tech network, e.g. 人際網絡 (social network) or 供應鏈網絡 (supply chain network). Only flag in a computing/internet context.",
      "occurrences": 1,
      "positions": [
        16
      ],
      "rationale": "Mainland wording for \"network/internet\" in a computing/technology context; Taiwan's standard tech term is 網路.",
      "severity": "medium",
      "taiwan_term": "網路",
      "term": "網絡"
    }
  ],
  "sources": [
    "Curated by TariffMonkee from established Taiwan-vs-mainland terminology divergence and general bilingual knowledge of both regions' standard usage.",
    "A subset cross-checked against a public Taiwan/mainland vocabulary comparison (yakyacker.com) -- see each flagged term's 'source' provenance is not exposed per-call in v1, but is recorded in the underlying glossary table.",
    "NOT yet reconciled term-by-term against Microsoft's published zh-TW/zh-CN style guides -- a disclosed gap, not a completeness claim.",
    "Live glossary: ats-usage D1 database, table tw_localize_glossary (47 terms at launch, 2026-09-06)."
  ],
  "terms_checked": 47,
  "verified_on": "2026-09-06"
}

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.02.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://tariffmonkee.com/paid/tw-localize-check' \
  -H 'content-type: application/json' \
  --data-raw '{"fix":true,"text":"\u8acb\u5728\u8edf\u4ef6\u4e2d\u6253\u958b\u8996\u983b\u6703\u8b70\uff0c\u9023\u63a5\u516c\u53f8\u7db2\u7d61\u5f8c\u628a\u6578\u64da\u5eab\u5099\u4efd\u5230\u786c\u76e4\uff0c\u518d\u7528\u77ed\u4fe1\u901a\u77e5\u670d\u52d9\u5668\u7ba1\u7406\u54e1\u3002\u6253\u5370\u6a5f\u548c\u9f20\u6a19\u653e\u5728\u4fbf\u5229\u5e97\u65c1\u7684\u8fa6\u516c\u5ba4\u3002"}'

# 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://tariffmonkee.com/paid/tw-localize-check' \
  -H 'content-type: application/json' \
  --data-raw '{"fix":true,"text":"\u8acb\u5728\u8edf\u4ef6\u4e2d\u6253\u958b\u8996\u983b\u6703\u8b70\uff0c\u9023\u63a5\u516c\u53f8\u7db2\u7d61\u5f8c\u628a\u6578\u64da\u5eab\u5099\u4efd\u5230\u786c\u76e4\uff0c\u518d\u7528\u77ed\u4fe1\u901a\u77e5\u670d\u52d9\u5668\u7ba1\u7406\u54e1\u3002\u6253\u5370\u6a5f\u548c\u9f20\u6a19\u653e\u5728\u4fbf\u5229\u5e97\u65c1\u7684\u8fa6\u516c\u5ba4\u3002"}' \
  | 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Ftariffmonkee.com%2Fpaid%2Ftw-localize-check&method=POST
const res = await pay("https://tariffmonkee.com/paid/tw-localize-check", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "fix": true,
    "text": "\u8acb\u5728\u8edf\u4ef6\u4e2d\u6253\u958b\u8996\u983b\u6703\u8b70\uff0c\u9023\u63a5\u516c\u53f8\u7db2\u7d61\u5f8c\u628a\u6578\u64da\u5eab\u5099\u4efd\u5230\u786c\u76e4\uff0c\u518d\u7528\u77ed\u4fe1\u901a\u77e5\u670d\u52d9\u5668\u7ba1\u7406\u54e1\u3002\u6253\u5370\u6a5f\u548c\u9f20\u6a19\u653e\u5728\u4fbf\u5229\u5e97\u65c1\u7684\u8fa6\u516c\u5ba4\u3002"
  }),
});
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://tariffmonkee.com/paid/tw-localize-check",
        json={
            "fix": True,
            "text": "\u8acb\u5728\u8edf\u4ef6\u4e2d\u6253\u958b\u8996\u983b\u6703\u8b70\uff0c\u9023\u63a5\u516c\u53f8\u7db2\u7d61\u5f8c\u628a\u6578\u64da\u5eab\u5099\u4efd\u5230\u786c\u76e4\uff0c\u518d\u7528\u77ed\u4fe1\u901a\u77e5\u670d\u52d9\u5668\u7ba1\u7406\u54e1\u3002\u6253\u5370\u6a5f\u548c\u9f20\u6a19\u653e\u5728\u4fbf\u5229\u5e97\u65c1\u7684\u8fa6\u516c\u5ba4\u3002",
        },
    )
    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
2 h agoPassed402114 ms$0.02
6 h agoPassed402164 ms$0.02
10 h agoPassed402116 ms$0.02
14 h agoPassed4021.2 s$0.02
18 h agoPassed4021.0 s$0.02
Show 10 older checks
22 h agoPassed40262 ms$0.02
26 h agoPassed4021.3 s$0.02
29 h agoPassed4021.3 s$0.02
32 h agoPassed40292 ms$0.02
35 h agoPassed402412 ms$0.02
38 h agoPassed40267 ms$0.02
41 h agoPassed402128 ms$0.02
44 h agoPassed4021.1 s$0.02
2 days agoPassed402121 ms$0.02
2 days agoPassed4021.9 s$0.02