Introduction

What is Sgovr

Sgovr is the layer between an agent and the businesses it wants to act on. Instead of scraping brittle human-facing pages, an agent reads a machine-readable capability spec, then invokes actions through a gateway that verifies a scoped mandate, enforces limits and policy, settles payment, and records a tamper-evident audit trail. It is MCP-compatible at the call layer, with discovery, identity and payments rails on top.

The three-step flow

• Discover - query the registry in natural language and get back relevance-ranked, verified providers.
• Understand the terms - read the provider's capability spec: actions, input/output schemas, auth scopes, pricing and rate limits.
• Safely transact - invoke an action under a signed mandate; the gateway authorizes, settles and audits it for you.

Quickstart

Install a client SDK, or wire Sgovr into an MCP host. The SDK guides below walk through a complete discover → mint → invoke → refund example.

# 1. install the client SDK
npm install @sgovr/sdk        # or: pip install sgovr-sdk
 
# 2. discover a provider and invoke an action
#    (see the SDK guides for the full, runnable example)
 
# 3. or connect any MCP host via SSE - no per-provider setup
claude mcp add --transport sse sgovr-sse https://mcp.sgovr.eu/sse

Core concepts

• Provider - a business that registers a capability spec and exposes actions.
• Action - a single callable operation, either none (free, e.g. a search) or transactional (moves money, e.g. a booking).
• Mandate - a signed, scoped, time-limited credential a principal issues to an agent: allowed scopes, a spend cap, and an expiry.
• Gateway - the runtime that every invocation flows through: verify & authorize → score risk & enforce limits → settle → audit.

Pick your path