# Vigent Vigent is a pay-per-use Czech legal database for external agents. This is the website/account foundation. Legal retrieval and CLI/MCP/SDK releases are not activated. Never invent an install command or endpoint, and never ask for secrets in chat. ## Get started Connect the agent you already work with. ### Start with the source Vigent is being built as a Czech legal database for external agents. Your agent handles the conversation, reasoning and final answer. Vigent provides legal source material and its available source and time context. ### Create your account Use the account sign-in page. Email links and Google sign-in become available when their providers are configured. Both methods use your verified email address to identify the same account. ### Prepare access The account console supports creating named, expiring API keys. A key appears once; keep it in a secret manager or your agent's protected credential store. Never paste it into a chat or public repository. ### Connect a client The public vigent-clients repository is the home for CLI, MCP and Python/TypeScript SDK implementations. It currently contains the repository foundation; no client package, install command or remote MCP endpoint has been released. The legal query service is not activated. ### Follow availability Use the coverage and interface guides to find the actual release state. Account setup alone does not activate paid legal retrieval or grant free usage. ## Authentication Account sessions and credentials for your agents. ### Email and Google Email sign-in uses a one-use link that expires within 15 minutes. The message shows its lifetime. Opening a link does not sign you in; choose Continue. If you open it in another browser, confirm the email address that received the link. Google signs in through the backend, which verifies that Google is authoritative for the verified address. ### API keys Create a key in API keys, give it a name and choose its expiry. Copy it before dismissing the one-time display. Keys are stored only as hashes. Revoking a key invalidates it immediately; expired keys cannot authenticate. Keys are account-scoped. ### Sessions The account uses a Secure, HttpOnly, SameSite=Lax cookie, short-lived signed access tokens and revocable server-side login records. Sign out ends the current login; Settings can sign out every login. Credentials are never saved in local browser storage. ### Client authorization CLI device approval and remote MCP OAuth consent have separate browser surfaces. They remain inactive until the actual client authorization service is wired. Browser cookies are not MCP credentials. ## Sources and time Know the source, version and effective date behind legal material. ### Initial data families The product scope covers Czech legislation from e-Sbírka and Czech court decisions. An archived source snapshot is not proof that the live service can query it. Served source coverage and freshness must be published before data access is activated. ### Version and effective date A document's publication, wording version and effective period are different facts. The data integration must preserve them so an agent can distinguish current text from a historical version. No specific source's coverage is claimed by this foundation. ### Provenance and notices Source-linked material must carry required attribution and source-specific notices, including where original texts are free and copies are not authentic. Paid serving requires a review of each source's reuse terms. Always check the original publisher when authenticity matters. ## CLI Command-line access for local tools and coding agents. ### Repository The CLI will live in the public vigent-clients repository alongside MCP and the SDKs. This foundation does not publish a CLI executable or installation command. ### Authentication boundary The intended flow is browser-approved device sign-in or a protected API key supplied through the client. The browser approval surface is reserved; it cannot issue client credentials before protocol wiring is implemented. ### Release criteria A released CLI must provide documented install/login commands, structured output, stable errors and a source-backed retrieval workflow. Those implementations are separate work. ## MCP Legal-data tools inside an external agent. ### Local and remote The MVP includes local stdio and remote HTTP MCP support. Both are future implementations in the public client repository; no live endpoint or client configuration is published here. ### Authorization A local server will use the CLI's protected credentials or an API key. A remote server will support per-user OAuth authorization for clients such as Claude and ChatGPT; it will not authenticate using the web session cookie. ### What stays with your agent Vigent does not host a chat session or provide an answer agent. The external agent chooses tools, interprets retrieved source material and interacts with you. ## Python and TypeScript SDKs Use the same database in your own agent applications. ### Two supported languages Python and TypeScript SDKs belong in vigent-clients. No package name, import statement or install command is released by this repository foundation. ### Shared API contract Future SDKs will use the agreed legal-data API, return provenance/version metadata and report authentication, limit and availability errors consistently. The current account API is separate from that future data contract. ### Credential handling Keep API keys on the server or in protected agent environments. Never embed them in public browser bundles or source control. ## Usage and billing Pay per use, with visible usage and bounded spend. ### Pricing model Vigent is pay per use, priced in USD. The planned model-backed retrieval uses prepaid credits to bound provider spend. The final operation prices and purchase amounts depend on measured costs and have not been activated. ### No implicit charges There is no subscription, automatic free-credit grant or usable paid-query allowance in this foundation. Billing and purchase controls remain unavailable until a rate card, payment processing and the data service are verified. ### Your account Usage and Billing show actual service states. They do not display invented zero-cost usage or a fabricated credit balance. Once activated, the internal usage ledger will be the source of charges; Stripe will collect the final approved amounts, not meter queries. ### Out of credit Paid data requests must stop before exceeding available funds. Replenishment will be offered only through verified purchase controls, with approved amounts and final tax/payment details. ## Availability and limits The exact boundary of the current foundation. ### Available foundation This release prepares the public website, account API, sign-in/provider integration code and credential-management surfaces. A provider is available only when configured; the sign-in page reads that state. ### Data and clients Legal retrieval, corpus activation, CLI/MCP/SDK implementations and final remember-stack wiring belong to separate work. There is no query endpoint, remote MCP service or released client package to call yet. ### Data boundaries No contract drafting/review service, hosted chatbot, autonomous agent, document-upload workspace or legal-search console is part of the MVP. Current court-access restrictions remain in force; this site does not resume crawling. ### Failures and recovery If a sign-in method is unavailable, use a configured method or return later. Expired email links need a new request. Revoke lost keys and create replacements. Requests fail closed when accounts, client authorization or paid data are unavailable.