Skip to content
BUMIT

BUMIT

Trust infrastructure for business and autonomous transactions.

Verify Swiss businesses using authoritative evidence.

Machine-readable decisions · Source provenance · REST API

Read the API docs View capabilities
BUMIT returns structured checks, evidence provenance, freshness, reasons, and one deterministic profile decision.

Try BUMIT

Verify a Swiss business with your AI assistant

First connect BUMIT to your assistant as an MCP server. Pasting the prompt alone does not connect it. Once connected, the assistant can call the verify_business tool.

MCP URL
https://bumit.ai/mcp
prompt
Using the BUMIT verify_business tool, verify a Swiss company using its UID. Show its commercial-register status, available sanctions and regulatory checks, and the provenance and freshness of the information. Clearly distinguish verified findings from unavailable or unsupported checks.
Setup instructions

The MCP tools

Three tools, three distinct jobs

All three are available at the same MCP endpoint. Only verify_business produces a verification decision; the other two are register retrieval and never verify anything.

  • verify_business

    One-call verification of a Swiss business by UID or exact legal name. Returns a deterministic outcome, the checks performed, and the evidence behind them.

  • search_companies

    Searches the commercial register by name and returns bounded candidates. Discovery only: nothing is selected, ranked or verified.

  • get_company_profile

    Retrieves one company's canonical register profile by UID, with provenance and a freshness envelope. Retrieval only: FOUND is not a verification result.

What BUMIT does

Evidence in. Deterministic decision out.

A software system sends a Swiss business identifier or verification request. BUMIT evaluates available authoritative evidence and returns structured checks, provenance, and a deterministic decision.

  1. 01

    Request

  2. 02

    BUMIT

  3. 03

    Authoritative sources

  4. 04

    Deterministic rules

  5. 05

    PASS / REVIEW / FAIL / UNKNOWN

  6. 06

    Reasons + evidence + provenance

Machine-first example

One request. Explicit uncertainty.

The documentation UID is synthetic. UNAVAILABLE is returned when required production evidence is unavailable; it is neither a positive nor a negative finding.

REST / JSON

Provenance

Versioned rules

Request
POST /api/v1/verify-business
{ "uid": "CHE-000.000.000" }
Response excerpt
{
  "resolution": { "outcome": "UNAVAILABLE" },
  "result": {
    "outcome": "UNAVAILABLE",
    "derivation": "DETERMINISTIC_REQUIRED_CHECKS"
  },
  "caller_identity_used": false
}

The boundary of PASS

Every applicable mandatory check of the configured verification profile obtained sufficient usable evidence and none produced REVIEW or FAIL.

PASS does not mean safe to transact, complete KYB, legal approval, risk-free, ownership or control screened, or signatory authority confirmed. Every response exposes these boundaries structurally; results are informational and not legally binding.