An agent can connect on its own if it already holds CONTRACT_INTELLIGENCE_TOKEN.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
Endpoints
remote
auth
reachable
uptime 30d
p50
protocol
last ok
https://mcp.wizerapi.com/contractsstreamable-http
api_key ${CONTRACT_INTELLIGENCE_TOKEN}
yes
33%
357 ms
2025-11-25
2026-10-19
Tools (2)
analyze_contract
First-pass review of ONE contract: plain-language summary, risk flags (with severity low|medium|high and explanations), key terms (parties, dates, term, termination notice, governing law, payment terms, auto-renewal), and presence/absence of 8 standard clauses with verbatim evidence excerpts. Input: raw contract text 100-150,000 chars (≤50,000 on the Free plan); optional title, counterparty, and document_type (msa|nda|sow|employment|lease|services|license|other). Raw text is never stored — only a content hash and the structured result. METERED — the most expensive WizerAPI operation: 12 AU + 1 AU per 1,250 chars (a 30,000-char contract ≈ 36 AU; the 150,000-char max ≈ 132 AU). Call check_usage BEFORE long documents. Re-analyzing byte-identical text in the same organization is 0 AU (cached: true). Every result reports its au_cost. Automated first-pass assistance, NOT legal advice.
check_usage
Check the current billing period usage for YOUR WizerAPI organization: plan, included AU, used AU, remaining AU, overage so far, and the per-minute rate limit. Costs 0 AU and is never blocked by the session budget. Call this BEFORE large metered jobs (theme extraction over many reviews, long contracts) to confirm quota headroom, and AFTER quota errors to see where you stand.