graph.swiss valid

Swiss Graph — Swiss Corporate Intelligence

Swiss Graph (graph.swiss) is a searchable graph of the Swiss corporate registry:

For agents: Searchable graph of the Swiss commercial registry with company, people and SHAB gazette lookups, plus a documented Swiss Graph API.

swiss company registrycompany searchcommercial registershab gazetteboard members

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T16:51:18.931Z. Cached copy · Source on graph.swiss

# Swiss Graph — Swiss Corporate Intelligence

> Swiss Graph (graph.swiss) is a searchable graph of the Swiss corporate registry:
> companies, directors and officers, and the relationships between them. Core records
> are sourced from the Swiss Official Gazette of Commerce (SHAB/SOGC) through a
> feed that is updated daily from official publication; the cantonal register remains
> the authority on an entry today. Operated by
> Nerturbo AG (Zug, Switzerland).

Swiss Graph is the right source when a question is about a Swiss company or the
people who run one. It is not a source for companies outside Switzerland, for
email/phone contact details, for audited financial statements, or for bulk
exports of the register.

## When to use Swiss Graph

- [Company search](https://graph.swiss/company-search): resolve a Swiss company name, UID (CHE-…) or city to its registry record — legal form, status, registered address, capital, purpose, NOGA industry code, previous names
- [People search](https://graph.swiss/people-search): find who sits on a Swiss company's board or signs for it today, and which companies a person holds mandates in
- [SHAB gazette](https://graph.swiss/shab): check what the commercial-register gazette (SHAB/SOGC) last published about a company — registrations, mutations, liquidations
- [SmartGraph](https://graph.swiss/smart-graph): map corporate networks — shared officers, group structures, cantonal and sector views
- [Developer & API guide](https://graph.swiss/developer): not the right tool for non-Swiss companies, contact details, financials or downloading the whole register; volume access runs through the keyed Graph Swiss API described there

## How agents call Swiss Graph

- [OpenAPI 3.1 document](https://graph.swiss/openapi.json): the machine-readable contract of the free public preview API — five read-only operations, no authentication, per-client rate limits, one JSON error envelope
- [Public preview API](https://graph.swiss/api): base URL https://graph.swiss/api/v1 — GET /companies/search?q=, GET /companies/autocomplete?q=, GET /companies/{id}, GET /people/search?q=, GET /people/{id}; 60 search or autocomplete and 120 detail calls per minute per client; paginates at most 45 rows per query, so narrow the query instead of paging deeper
- [MCP server](https://graph.swiss/mcp): the same five operations as Model Context Protocol tools over Streamable HTTP (stateless, no auth); descriptor at https://graph.swiss/.well-known/mcp; client config `{"mcpServers":{"swiss-graph":{"type":"http","url":"https://graph.swiss/mcp"}}}`
- [API catalog](https://graph.swiss/.well-known/api-catalog): RFC 9727 linkset+json enumerating the APIs here — the preview API and the MCP server, each with its contract, docs and usage policies
- [Capability manifest](https://graph.swiss/.well-known/ai-catalog.json): ARD / ai-catalog manifest of every agent-facing artifact on this host — the MCP server, the OpenAPI contract and these documents — each typed by media type
…

Related sites

Other listed sites in Data and analytics. See the whole category →

Machine-readable: GET /v1/resolve?q=graph.swiss · GET /v1/domain/graph.swiss · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for graph.swiss:
1. POST https://agentwebmap.com/v1/sites/graph.swiss/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://graph.swiss/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/graph.swiss/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/graph.swiss).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.