The argument here is narrow and correct: a single model reading a filing produces claims that look identical whether or not they are supported. Running extraction and verification on different models catches the errors a self-check would agree with, and the output says which state each finding is in rather than flattening them. The cost framing follows from that — you are paying for two passes either way, so the comparison is against doing two frontier-model passes yourself. Raw contract text is not persisted by default; public filing metadata may be cached because the filings are public.
A hosted MCP and REST intelligence API for document evidence. The pipeline is the product: one model extracts structured findings with a verbatim quote and a source reference for each, then a different model cross-checks every finding against the original. Contradictions get flagged and unsupported claims get marked for review rather than presented as fact.
- SEC filing analysis by content, filing URL, ticker or CIK, covering 10-K, 10-Q and 20-F workflows — `analyze_public_filing`
- Contract review returning clauses, obligations, liability exposure, missing clauses, unusual terms, the evidence behind each, and human-review flags — `review_contract_risks`
- General evidence analysis on any document, with source-grounded findings, confidence and verification status — `analyze_document`
- Cheaper single-pass work when the two-model pipeline is more than the job needs: static web content extraction, fast summarisation, and JSON-preserving translation — `extract_web`, `summarize`, `delegate_bulk_translate`
- A free cost preview before any paid call, and a free health check — `estimate_cost`, `health_check`
- A stable output contract: every finding carries `claim`, `evidence`, `sourceRef`, `confidence` and `verificationStatus`, with an overall confidence on the analysis
No API key and no subscription for paid calls — settlement runs over the x402 protocol in USDC on Base or Solana, with the `exact` scheme, so paid endpoints need payment headers rather than an account. A wallet login is optional and only adds the dashboard, request history and API-key management. Connect at `https://amalgix.io/mcp` over Streamable HTTP. Pricing scales with document size; call the free cost estimate first. Two limits to plan around: paid analysis content is sent to third-party LLM providers, and the vendor asks you not to submit passwords, private keys, SSNs or regulated PII. Contract and filing output is evidence triage, not legal or investment advice.
One command — npx -y mcp-remote https://amalgix.io/mcp