Markbase vs VATComply

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms866236
P95 · ms1568851
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit30 req/window · 29 remaining · resets 1783519324Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Markbase vs VATComply: common questions

Which is more reliable, Markbase or VATComply?

On our scheduled checks, VATComply leads on measured uptime — Markbase at 99.02% versus VATComply at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Markbase or VATComply?

VATComply has the lower median latency in our checks — Markbase responds in 866 ms versus VATComply at 236 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Markbase and VATComply need an API key?

Neither needs a paid key — Markbase is callable with no signup, and VATComply is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Markbase and VATComply from the browser?

Yes — both Markbase and VATComply send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Markbase and VATComply free for commercial use?

Markbase has unclear commercial terms, and VATComply has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.