botchannels

Can I sell to this customer? botchannels answers yes or no - per buyer jurisdiction, under the VAT thresholds that apply to you - and keeps the counters.

Threshold routing API

decide answers yes or no for that buyer’s jurisdiction, under the thresholds that apply to you. report adds the sale to the counter. The free default policy blocks a sale that needs a registration you have not entered. Entering that registration opens the gate. Each answer cites its rule version.

How a decision is made

Phone verification for bots

An x402-paid call sends a one-time code by SMS through our Twilio subscription. The seller pays, or the buyer pays once. A buyer whose IP is outside the country they declare gets a SIM-country evidence record a later decision can cite.

The verification flow

Request

POST /decide HTTP/1.1

{
  "seller_id": "seller",
  "buyer_country": "DE",
  "buyer_region": null,
  "evidence": {
    "ip": "203.0.113.24",
    "ip_country": "DE",
    "ip_region": null,
    "phone_country": null
  },
  "amount": "1240.50",
  "currency": "EUR",
  "product_class": "digital_service",
  "pass_days": null
}

Response

yes

HTTP/1.1 200

{
  "decision": "yes",
  "reason": "open",
  "registration_that_opens_the_gate": null,
  "rule_version": "2026-10-14",
  "jurisdiction": "DE",
  "rate_hint": null
}

Placeholder values. Not a ruling. Draft field lists.

The free default policy is available now. Paid verification is priced later. No price is published.

A decision cites the rule version it used. That citation is a trace of which text was applied. Correctness stays with the reviewer. This is not legal or tax advice, and it is not a compliance guarantee.

Demo

Our own RPC endpoints are the first integration.