Capabilities¶
Capability docs describe what Occam can do as product areas — not individual MCP tools. For tool pickers and schemas, start at the Reference overview or Tool index.
Start here (human + agent): Why Occam — advantages and knobs — one page that contrasts Occam with generic fetch and lists the knobs that matter.
Who needs this¶
- Operators deciding which surfaces to enable
- Developers mapping a workflow onto Occam’s domains
- Readers who want stable vs experimental boundaries before diving into tools
Domains¶
Web access¶
Fetch and reachability: how Occam climbs from cheap HTTP to browser extract, and how egress / proxies / SSRF controls apply.
- Acquisition — gated HTTP → browser ladder
- Networking and proxies — egress, proxies, private-URL policy
Knowledge processing¶
How extracted content is shaped for context windows, and how site recipes (playbooks) steer structured reads.
- Materialization — token budgets and structured output
- Playbooks — site recipes and signature model
Runtime¶
Long-lived operator concerns: authenticated sessions and day-2 CLI / packaging.
Experimental¶
Opt-in surfaces that are not part of the stable default tool set. Enable only when you accept the documented flags and failure modes.
- Experimental — watch, crosscheck, batch, failure atlas
Related¶
- Task routing — which tool for which job
- Trust and security — honesty, receipts, install safety
- Architecture overview — user-level execution model