CONTENTUM.COMA specialist. A plan. A result.

CONTENTUM.COM · Documentation

CONTENTUM documentation

Everything the system does, in one place: for companies that need security work done, for providers who do it, for the team that runs it and for AI agents that use it.

Summary

CONTENTUM.COM is a project market for cybersecurity and IT infrastructure. It shows where security work is needed and who can do it, and it gives both sides a short way to each other.

The public site lists open projects and public tenders, describes twelve service areas and offers tools: a passive security check for a domain, a NIS2 self-check, a vulnerability database and guides for buyers. The site is available in 20 languages.

Behind a login, the team runs the security tools (domain map, host check, Deep Scan with a report of about 40 pages, findings board) and the workspace for projects, providers and requests.

AI agents reach the public functions through an MCP server, an A2A agent, WebMCP and a JSON API, without an API key.

  • Find open security and infrastructure projects by service, country and region
  • Find public tenders with an open deadline
  • Check a domain from outside and get a report
  • Test whether NIS2 probably applies to an organisation
  • Look up any CVE and the vulnerabilities that are being exploited
  • Send a request and get matching providers
  • Map a domain, run a Deep Scan and track the findings on a board (team)
  • Let an AI agent do all public steps on its own

Contents

  1. What CONTENTUM is

    The parts of the system and who each part is for.

    The problem it solves · Three areas · Who uses it · What needs no account

  2. Project market

    Open projects on a globe and in a list, each with service, place and signal.

    Where projects come from · Signal types · The globe · Project list and project page · Anonymity

  3. Public tenders

    Open public tenders for security and infrastructure work, from the German-speaking countries and from the rest of the world.

    What is listed · What a tender page shows · Deadlines

  4. Countries, regions and services

    The same projects, arranged by place and by service area.

    Countries · Regions · Twelve service areas · Providers

  5. Requests: how the two sides meet

    One form for companies and providers, a reference number and an answer by e-mail.

    For companies · For providers · Protection against misuse · What happens inside

  6. CONTENTUM Check and NIS2 check

    Two self-checks: one for a domain, one for the question whether NIS2 applies.

    CONTENTUM Check · Limits of the check · NIS2 check

  7. Vulnerability database

    Every published CVE, and the ones that are being exploited right now.

    What is in it · How to find a record · From a vulnerability to help · Sources and freshness

  8. Guides

    Neutral background for buyers, checked against sources.

    Topics · How a guide is built · Languages

  9. Security tools: map, Deep Scan, report, board

    The tools of the team for looking at a company from outside. Behind a login.

    Domain map · Host check · Deep Scan · Permission · The report · Findings board

  10. Team workspace

    Where the team works on projects, providers and requests. Behind a login.

    Overview and project list · Project record · Board and map · Matrix and providers · Signals, requests and data

  11. Agent access

    The public functions as tools for AI agents. No API key.

    Four ways in · What agents can do · Limits and privacy · Machine-readable descriptions

  12. Data, privacy and languages

    Where the data comes from, what stays private, and the 20 languages.

    20 languages · Freshness · Privacy · For search engines and AI · Known limits

For AI agents

Agents use the public functions directly through an MCP server, an A2A agent, WebMCP and a JSON API. This documentation is also available as one Markdown file.

Updated: