Assay: settlement verification
Verify crypto payments really settled and how much arrived. 20 chains. Read only, no API key.
| Endpoint | https://fomox.io/api/assay/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 6 tools · grade A (100) · pin ts_c3a12ec0c64f7d28b24fdb45752eed5c · protocol 2025-06-18 |
| First / last listed | 2026-11-01 03:27 UTC / 2026-11-01 03:27 UTC |
| Grade over time | 2026-11-01: A (100), 6 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: verify_payment list_chains list_failure_modes evaluate_spend_policy run_sandbox_case check_sandbox_answer
verify_payment | Check whether a crypto payment really settled and how much was ACTUALLY delivered, which is often not the amount the transaction claims. Use this before crediting anyone for an incoming payment.
Returns `delivered` (what truly moved), `claimed` (what the transaction says), `mismatch` (true when they disagree), and `warnings` naming the specific trap with a remedy. `ok` is true ONLY when the payme params: chain, ref*, expect, rpcUrl |
list_chains | List every chain this service can verify, with the confirmation depth each needs before a payment is treated as final, and how deeply it can be verified. Call this if you are unsure whether a chain is supported or what to pass as `chain`. params: none |
list_failure_modes | List every known way a blockchain payment can appear successful while being worth less than it claims, or nothing at all. Each entry explains what the chain does, what it costs you when you get it wrong, and the one-line fix.
Useful when writing or reviewing code that credits users for incoming crypto payments. Every chain has its own dialect but they are all the same few lies, and the mitigation params: family |
evaluate_spend_policy | Check a proposed payment against spending limits that live OUTSIDE your context, where no instruction in a prompt, a message or a web page can change them. Returns a signed allow or deny with reasons.
Use this before executing any transfer on behalf of a user. It enforces velocity caps, per-action ceilings, recipient allowlists and asset allowlists. Because the rules are held server side and sign params: policyId*, policySecret*, action*, commit |
run_sandbox_case | Practise on a payment designed to deceive you, with no money at risk. Returns a verification result shaped exactly like a real one for one of 19 adversarial cases. Decide whether you would credit it, then call check_sandbox_answer to find out whether you were right and what the mistake would have cost.
Use this to test any agent or integration that handles incoming crypto payments BEFORE it handl params: caseId |
check_sandbox_answer | Score your decision on a sandbox case. Tell it whether you would have credited the payment and for how much, and it replies with whether that was correct and, if not, exactly what the error would have cost you in real units. This is the fastest way to find out whether your payment handling is actually safe. params: caseId*, credit*, amount |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.