Cross-border VAT treatment for a digital-services sale: place of supply, who accounts,…
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)
by usaref.dev · discovered, not yet claimed by its owner · updated 2026-10-08
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
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)
Tags: vat · tax · cross-border · x402-sellers · bazaar
Call contract
- Method
- POST
- Input
- json
- Output
- json
- Last paid call
- 2026-10-08
{
"buyer_country": "de",
"buyer_type": "unknown",
"seller_country": "us"
}{
"example": {
"buyer_identity_flag": "string",
"destination_liability": {},
"disclaimer": "string",
"eservices_definition": {},
"receipt": {},
"rule": {},
"status": "ok",
"vida_flag": "string",
"workings": [
"value"
]
},
"type": "string"
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/40582.jsonfor the price and payment options. - Pay. Call
GET https://usaref.dev/v1/vat/determine. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.1 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 1 calls · 1 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.1 | 0x1F0409ccD20A2fb497d4DeCeF4E17e9d0688FeA6 | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x1F0409ccD20A2fb497d4DeCeF4E17e9d0688FeA6",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "100000",
"amountUsd": 0.1,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"properties": {
"buyer_identity_flag": {
"description": "Present when the buyer was unidentified: records the B2C-default assumption",
"type": "string"
},
"destination_liability": {
"description": "Present when a supplier-side treatment (e.g. SA zero-rating) coexists with a verified destination-country VAT obligation — carries the companion rule",
"type": "object"
},
"disclaimer": {
"type": "string"
},
"eservices_definition": {
"description": "What counts as an electronically-supplied service, with citation",
"type": "object"
},
"receipt": {
"description": "Only when receipt=true on a paid 200. kind answer_receipt. Verify at /certified/public-key.",
"type": "object"
},
"rule": {
"description": "The applied rule: place_of_supply, who_accounts_for_vat, rate_basis, registration_or_threshold, reporting, statutory citation, notes",
"type": "object"
},
"status": {
"description": "Paid responses always carry a matched rule — out-of-scope pairs are refused free (422) before payment",
"enum": [
"ok"
],
"type": "string"
},
"vida_flag": {
"description": "Forthcoming EU ViDA changes affecting these rules (2027/2028/2030)",
"type": "string"
},
"workings": {
"description": "The classification reasoning that selected the rule",
"type": "array"
}
},
"required": [
"status",
"workings",
"disclaimer"
],
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {
"buyer_identity_flag": "string",
"destination_liability": {},
"disclaimer": "string",
"eservices_definition": {},
"receipt": {},
"rule": {},
"status": "ok",
"vida_flag": "string",
"workings": [
"value"
]
},
"type": "string"
}Examples
curl -X POST 'https://usaref.dev/v1/vat/determine' -H 'Content-Type: application/json' --data '{"buyer_country":"de","buyer_type":"unknown","seller_country":"us"}'
# -> 402 Payment Required; read PAYMENT-REQUIRED
# retry the identical request with PAYMENT-SIGNATUREconst res = await fetch("https://usaref.dev/v1/vat/determine", {
"method": "POST",
"headers": {
"content-type": "application/json"
},
"body": "{\"buyer_country\":\"de\",\"buyer_type\":\"unknown\",\"seller_country\":\"us\"}"
});
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
import json
res = httpx.request("POST", "https://usaref.dev/v1/vat/determine", json=json.loads("{\"buyer_country\":\"de\",\"buyer_type\":\"unknown\",\"seller_country\":\"us\"}"))
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- usaref.dev
- Endpoint
- https://usaref.dev/v1/vat/determine
- Machine-readable
/resources/40582.json