Vat Determine
by usaref.dev in Markets & finance
Cross-border VAT treatment for a digital-services sale: place of supply, who accounts, rate basis, registration trigger — the applied rule cited to the statute (EU, UK & South Africa; defined supply pairs)
https://usaref.dev/v1/vat/determine- Price
- $0.1
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 858 ms
- 937 ms slowest 5%
- Last check
- Passed
- 3 h ago, next any minute now
Reliability
How to call it
POST https://usaref.dev/v1/vat/determine
Each call costs $0.1 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://usaref.dev/v1/vat/determine
content-type: application/json
{
"buyer_country": "de",
"buyer_type": "unknown",
"seller_country": "us"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
buyer_country | string | Yes | Buyer's country, ISO 3166-1 alpha-2 |
buyer_type | string | No | unknown (default) = buyer identified only by wallet address — treated as B2C under default rules and explicitly flagged in the response One of: B2B, B2C, unknown. |
receipt | boolean | No | Optional. true adds an Ed25519 answer receipt on a paid 200, incluedd in this price. Not a certified extract. |
seller_country | string | Yes | Seller's country, ISO 3166-1 alpha-2 (EL accepted for Greece, UK for United Kingdom) |
Example response
The listing has no example response.
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.1.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://usaref.dev/v1/vat/determine' \
-H 'content-type: application/json' \
--data-raw '{"buyer_country":"de","buyer_type":"unknown","seller_country":"us"}'
# 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://usaref.dev/v1/vat/determine' \
-H 'content-type: application/json' \
--data-raw '{"buyer_country":"de","buyer_type":"unknown","seller_country":"us"}' \
| 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.1 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.1" });
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.1 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fusaref.dev%2Fv1%2Fvat%2Fdetermine&method=POST
const res = await pay("https://usaref.dev/v1/vat/determine", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"buyer_country": "de",
"buyer_type": "unknown",
"seller_country": "us"
}),
});
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.1 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.1"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://usaref.dev/v1/vat/determine",
json={
"buyer_country": "de",
"buyer_type": "unknown",
"seller_country": "us",
},
)
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 | 859 ms | $0.1 |
| 8 h ago | Passed | 402 | 842 ms | $0.1 |
| 12 h ago | Passed | 402 | 979 ms | $0.1 |
| 16 h ago | Passed | 402 | 858 ms | $0.1 |
| 20 h ago | Passed | 402 | 894 ms | $0.1 |
Show 10 older checks
| 24 h ago | Passed | 402 | 881 ms | $0.1 |
| 28 h ago | Passed | 402 | 826 ms | $0.1 |
| 32 h ago | Passed | 402 | 224 ms | $0.1 |
| 35 h ago | Passed | 402 | 766 ms | $0.1 |
| 39 h ago | Passed | 402 | 876 ms | $0.1 |
| 43 h ago | Passed | 402 | 951 ms | $0.1 |
| 46 h ago | Passed | 402 | 926 ms | $0.1 |
| 2 days ago | Passed | 402 | 838 ms | $0.1 |
| 2 days ago | Passed | 402 | 835 ms | $0.1 |
| 2 days ago | Passed | 402 | 849 ms | $0.1 |