Katalis Website Legal API

The Website Legal API from Katalis — 1 operation(s) for website legal.

GitHub OpenAPI

Operations 1

GET /api/v1/website-legal The legal basics a UK business website must have, and who's behind the site #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/meetkatalis-com:meetkatalis-com-website-legal-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

meetkatalis-com-website-legal-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Katalis UK Business Intelligence Website Legal API
  version: 1.9.0
  description: 'UK company checks from the official record, on one key: the checking record a developer can trust before their business works with, pays, hires from or bids against a UK company. Companies House (profiles, officers, PSCs, charges, filings, filed accounts read into plain figures), the Payment Practices reports and the PPN 018 tests, public contracts won, the Register of licensed sponsors, HMRC''s anti-money-laundering register, the SRA, CQC and charity registers (each with a daily change feed), the UK Sanctions List, the gender pay gap, Environment Agency registrations, directors'' and PSCs'' ID verification against their deadlines, every deadline a company has (also as a calendar feed), and a change feed with signed webhooks for any company you watch. Alongside: the document readers (Modern Slavery statements, Ofsted and CQC reports, charity accounts), the Business Score and fit assessment, tender matching, AI visibility, and the design APIs (brand kit, generative art, effects, logos). Every reply says where it came from and carries the source''s attribution; people''s details go only to verified accounts. Get a free API key (100 credits a month, no card) at https://meetkatalis.com/developers and send it as the `x-api-key` header. Also: every API as Markdown at https://meetkatalis.com/apis.md, an MCP server for AI agents at https://meetkatalis.com/mcp, live status at https://meetkatalis.com/apis/about.

    Response conventions (since 2 October 2026): keys are camelCase on every endpoint; a registered company is `company: { name, number, status, statusDetail?, filingsOverdue?, ... }` on the register endpoints; the enrichment family (enrich, score, assess, brand-kit, ai-visibility, tender-match) keeps `business` / `profile` with `companyNumber` where one was matched, because its subject may be any business; an error reply that echoes what was asked for says `query`. Every error carries `code` and `requestId`; every reply an `x-request-id` header (since 1.9.0, 10 October 2026, the keyless and demo calls and the unknown-path 404 included); a charged reply `x-credits-remaining`; a reply that gave credits back `x-credits-refunded`; an error reply that was charged (a lookup that found nothing still ran) says `creditsCharged`. `company` carries `status` (and `statusDetail`, `filingsOverdue` when they apply) wherever the register was read for the reply; the report-based APIs (payment practices, PPN 018, gender pay gap, will-they-pay) give the name and number their report carries. Rate limits: monthly credit quota per plan plus a burst ceiling of 60 requests/minute per key (429 with no credit used). A request that fails on our side (any 5xx, including one that runs past its time limit) gives its credits back, and the x-credits-refunded header says how many; in a batch, items we couldn''t read are credited back and creditsRefunded says how many. Contains public sector information licensed under the Open Government Licence v3.0. Environment Agency register data is used under the Environment Agency Conditional Licence.'
  contact:
    name: Katalis
    url: https://meetkatalis.com/apis
    email: katalis@meetkatalis.com
  license:
    name: Katalis API Terms of Use (data from public sources keeps its own licence, e.g. the Open Government Licence v3.0)
    url: https://meetkatalis.com/apis/terms
  x-logo:
    url: https://meetkatalis.com/icon.svg
    altText: Katalis
servers:
- url: https://meetkatalis.com
tags:
- name: Website Legal
paths:
  /api/v1/website-legal:
    get:
      operationId: checkWebsiteLegal
      x-credits: 4
      summary: The legal basics a UK business website must have, and who's behind the site
      description: Reads the homepage and its linked legal and contact pages, visits the site in a real browser (nothing clicked) to see which advertising or tracking cookies land before consent, matches the company details shown to Companies House, checks the privacy notice covers the basics, the ICO fee register, and the contact details the E-Commerce Regulations ask for. Each check carries its result (pass, warn, fail), what we saw, the rule and what to do. "behind" is the registered company the site states or confirms (confirmed true) or the best name match (confirmed false). 4 credits; a site that couldn't be read is not charged.
      security:
      - ApiKeyAuth: []
      parameters:
      - name: url
        in: query
        required: true
        description: The website (a domain or URL)
        schema:
          type: string
          maxLength: 500
      - name: company
        in: query
        required: false
        description: The company number, if you know it
        schema:
          type: string
      responses:
        '200':
          description: url, behind {name, number, status, how, confirmed, note?, alternatives?}, registrationsStated?, legal {score|null, checks[] {code, result, found, rule, advice?}, couldntCheck[], notApplicable[] {code, reason}}, pagesRead[]
        '400':
          description: Missing or invalid url, or a page on a platform
        '401':
          description: Missing or wrong x-api-key
        '422':
          description: The site couldn't be read; credits given back
      tags:
      - Website Legal
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key