Spanish Company CIF NIF Lookup from Website

# Spanish Company CIF NIF Lookup from Website ## Start with a website. Get a company identity you can inspect. This API turns a Spanish company website into structured legal-company data: corporate CIF/NIF, legal name, source page and an explicitly stated fiscal address when available. Built for CRM enrichment, supplier onboarding and company-data workflows. ### When to use this API - Start with a URL, even when you do not know the company NIF. - Spanish corporate NIF structure and check-character validation, combined with a contextual legal-name match. - Inspect the original legal/contact page through `found_at`. Conflicting identities return an explicit error. - One JSON request and response. Pay per lookup without a monthly base subscription. ### Request Send `POST /v1/extract` with `Content-Type: application/json`, your marketplace API key and this body: ```json {"url":"https://www.futuroinformatica.com/"} ``` Responses include `success`, `domain`, `legal_name`, `tax_id`, `tax_id_valid`, `tax_address` and `found_at`. A fiscal address is returned only when explicitly labelled and attributable to the company. ### Scope and billing Public static HTML only. Personal DNI/NIE, browser-rendered pages and PDFs are excluded. Corporate NIF checksum validation does not confirm registration with AEAT or VIES, domain ownership or current tax status. Missing or ambiguous data is returned explicitly instead of guessing. The public plan costs $0.01 per processed lookup, including negative and ambiguous results, with 10 requests per minute. Marketplace fees and gateway/server-error billing rules apply. The extraction work budget is five seconds; network and gateway overhead are additional. ### Use with AI agents through MCP Connect an HTTP-compatible MCP client to `https://mcp.jojapi.com/spanish-company-tax-data`. Set `Authorization: Bearer YOUR_JOJ_API_KEY` as a connection header and use the listing's current plan. The documented extraction endpoint becomes a tool that accepts a company website URL. The MCP tool wraps the HTTP JSON payload inside `body`. Supply tool arguments such as: ```json {"body":{"url":"https://www.futuroinformatica.com/"}} ``` For a direct HTTP request, send only the inner `{"url":"..."}` object as the request body. The URL is required in both cases. For an agent workflow, supply a public Spanish company website, check `success`, retain `found_at` as evidence, and review ambiguous or missing results instead of inferring a tax ID. Use the **OpenAPI spec** and **MCP server** links on the listing for the current schema. Tool execution uses the same gateway and billing rules as ordinary API calls. ### Typical workflows - Add the published corporate tax ID and legal name to a CRM record that already has a website. - Prepare a supplier record for human review with the source page attached. - Match a company domain to the identity stated on its legal notice page. Extraction and check-character validation are separate from official company or tax registration verification.