B2B Domain Enrichment and EU VAT VIES Impressum

# Source-backed legal identity, public contacts and live EU VAT verification Source-backed legal identity, public business contacts and live EU VAT verification: turn a company domain into reviewable evidence for your CRM. This B2B domain enrichment API combines website contact extraction, domain-to-company lookup, EU VAT validation and DNS email intelligence in one JSON contract. Use the full inspection for account research and supplier onboarding, or select a focused endpoint when you only need a VAT check, an Impressum scraper or an email provider lookup. The international legal scraper reads a bounded selection of public pages, starting with the homepage and following legal notices such as Impressum, legal, terms, privacy, about, aviso legal and mentions légales. German Impressum extraction helps DACH company-data workflows collect legal names, labelled addresses, stated directors and commercial-register references. Company suffixes include GmbH, AG, Ltd, PLC, Inc., LLC, Corp., S.A.S., S.L. and B.V. Page text and supported Organization JSON-LD can supply candidates. Extracted fields retain source excerpts, extraction methods and observation dates. Owner, third-party and uncertain entity associations help separate the website operator from a hosting or payment provider. Multiple plausible entities remain candidates; JSON-LD and register references remain website statements, not official verification. The EU VAT number validator checks supported identifier structures and calls the European Commission's official VIES REST service when an eligible VAT is available. Send a VAT directly or use domain-to-VAT discovery. Association evidence informs candidate selection; ambiguous candidates are not silently treated as the website operator. The JSON response distinguishes valid, invalid, unavailable and timed-out checks, with the official company name and fiscal address when VIES supplies them. An available identity comparison reports legal-name similarity, not domain ownership. Teams replacing a VIES SOAP/XML integration can consume JSON here; the implemented upstream connector uses REST, not SOAP. A valid VAT does not determine an invoice's tax treatment. DNS inspection returns MX records, SPF and DMARC with provider evidence. Segment accounts by Google Workspace, Microsoft 365, Zoho or Proton receiving infrastructure, or inspect bounded recursive SPF include/redirect paths for supported email marketing services. RFC 9989 discovery reports an effective DMARC policy and explicit query limits. This email technology stack describes DNS observations; it does not inventory every website technology or verify mailbox delivery. Missing records, failed lookups and monitoring-only DMARC policies remain separate outcomes. Connect Clay's HTTP API enrichment, an n8n HTTP Request node or Make's HTTP module, then map accepted fields into your CRM. Through JoJ's platform-provided MCP server, Claude Code, Cursor and compatible Windsurf or OpenAI-powered agent applications can discover these operations as tools. Ask an agent to enrich a domain, validate an EU VAT or inspect a DMARC policy, and retain the returned evidence in its answer. There is no separate MCP server to deploy. Each inspection has a four-second application work budget and explicit partial-result warnings. Complete web observations may be reused for up to 6 hours; complete DNS observations use the minimum observed TTL, capped at 1 hour. Live VIES checks are never cached. `fresh=true` bypasses reads and writes. `module_cache` exposes reuse and expiry; source evidence preserves its observation date. This is neither a worldwide latency guarantee nor a promised match rate. Start with a few representative domains, review source coverage and ambiguity, then scale using the published quota. A completed inspection costs one credit, including useful partial or empty results; errors report zero JoJ usage. ## Connect your MCP client Use `https://mcp.jojapi.com/b2b-domain-enrichment-vat-impressum-api` with a compatible HTTP MCP client. Copy the authentication settings from the listing’s Connect dialog and use a JoJ consumer key for this API. Keep evidence excerpts, source URLs, observation dates, quality field statuses and warnings in agent answers. MCP calls use the same gateway, plan quota and billing as HTTP requests.