Private Law Wiki

Answer a question by quoting a published wiki article, or — when the question names one country, programme, tax regime, bank or legal form and asks one of its reviewed questions — with the reviewed structured answer and its verbatim official quotation. Never generated at request time; always carries the URL it came from. Returns confident=false with suggested reading when the corpus does not cover the question or when context genuinely conflicts. When the question names one reviewed object and several of its reviewed questions fit the wording without a confident match, the answer (if any) is an ordinary article quotation and structuredResolution carries the clarification: question_ambiguous with candidate topics and their admission state. A question naming several distinct reviewed objects, or mapped to one reviewed topic whose answer is withdrawn or held, returns confident=false, refusalReason structured_held and no article text; ask about one object or use answer_compare. Bare MSO means the Hong Kong Money Service Operator licence; use Management Services Organization or regulated-practice context for the broader platform concept. Ask in the language you want answered — Russian and English are both first-class.

Rank published articles for a query and return them with titles and URLs. Use when you want sources to read rather than a single answer. Search is sense-aware: bare MSO promotes only the Hong Kong Money Service Operator owner, professional-industry context promotes the regulated-practice platform, and genuinely conflicting context returns both with an explicit interpretation object.

The public endpoint defaults to format=json and textMode=compatible: the complete compact source graph is delivered once as JSON in content[0].text (96KiB whole-body cap), with a small wiki-bank-case-text/1 transport receipt in structuredContent. Text-only clients receive all native material except derived Markdown. Explicit summary puts the graph in structuredContent and only a notice in TextContent; use it only if your client consumes structuredContent. Explicit full preserves the previous full shape, up to2MiB. Internal callers without a boundary policy retain full compatible output. Compact overflow is held whole and offers a manual fresh-read full retry if your client accepts the larger response. Neither byte cap guarantees a model token limit. No material is truncated. The complaint desk's deterministic assessment for a frozen account, a closure notice, a document request, a stuck payment or a refused application: what to do now, the escalation ladder of the bank's jurisdiction (bank complaint, ombudsman or regulator, data access request), with recorded requirements, unresolved conditions and primary-source links, plus recorded response periods, cautions and the help that fits. Also returns the letters to send — the formal complaint and the data access request, in English with bracketed placeholders the person fills in themselves. The reported stage is an unverified intake fact; it does not establish completed steps or eligibility. No personal dates are calculated. calendarStatus explains the missing inputs. UK/EU complaint-response rules are returned separately as statutoryReply; the intake does not establish their applicable branch or a statutory due date. Pass holder whenever it is known: an ombudsman's door depends on whose account it is. Information, not legal advice. Never submit a person's contact details; hand them the complaint URL instead.

Return private.law's reviewed structured answer to a concrete question about one country, residence or citizenship programme, tax regime, bank or legal form — the statement, conditions and verbatim quotations from official sources with URLs and dates. Ask in natural language (the place must be named), or pass exact codes from answer_objects. When the question is not matched with confidence, found=false and candidates suggest known questions to clarify. Candidates are metadata only, carry no citation URL and do not establish that an answer is currently available. Pass object alone to list its known question topics with their canonical answerType. reason distinguishes invalid input, unknown public-catalog identities, a low-confidence match, the admission state of a matched topic (pinned for release, pending_native_pin, withdrawn, locale_not_covered; only a pinned topic is read) and held (a current projection hold named in hold); it never determines that no legal rule exists.

Return the reviewed answers to one question for several objects side by side (for example the minimum investment of several programmes, or a tax rate in several countries), each with its official quotations. Objects not covered are listed in missing — never guessed. Aliases count once; at least two distinct recognised objects are required. coverage describes answer availability for this request only, not completeness of law or personal applicability. Display missing objects and the coverage note when presenting partial results.

Enumerate active reviewed topic identities, including topics whose answers are currently held. A topic has at least one current native-content and reference-scope pin in the requested locale. reviewedQuestionCount counts these mapped questions; it is coverage, not current answer availability. Each object also carries answerCount: distinct questions with a currently available whole answer in the requested locale, counted over pinned cells (current native-content pin plus reference-scope pin), not variants, sources or articles. Held cells, including native_public_scope_held, are excluded from counts rather than failing the page. Limit is an upper bound: counted pages emit at most 4 objects and at most 64 candidate pairs, both over pinned cells only. Follow nextCursor until null; total counts matching reviewed topics, not answers. Only the selected page's answers are read. A completed source or policy hold can yield answerCount:0 without erasing the topic. Counts are observed in one read-only snapshot per page at countObservedAt; pages are not one shared snapshot. Invalid cursors return an error; only operational failures (projection resource caps, a stale or mismatched snapshot, a read error) return {error, reason: count_unavailable}, never partial or stale numbers. A pin does not establish current law or personal applicability.