Use the same live backend from scripts, CI, and local shells. Install once, sign in or set a key, and print clean Markdown on demand.
npm install -g contextplusplus
contextplusplus login
contextplusplus process https://example.com --format markdownBest path when you want the hosted backend, quota tracking, and no local provider secrets.
/ setup in three steps
01
The published package is contextplusplus. For persistent use, install it once; for smoke tests, npx is enough.
02
Use contextplusplus login for the hosted flow, or set CONTEXTPLUSPLUS_API_KEY + CONTEXTPLUSPLUS_API_URL in CI.
03
Run process against any supported public URL and feed stdout directly into agents, scripts, or local files.
/ output proof
The CLI returns the same cleaned Markdown the API and MCP surfaces produce, so your shell scripts and your agents stay in sync.
This domain is for use in documentation examples without needing permission. Avoid use in operations.
illustrative shape — real output via convert_url / process
/ the catalog
live from GET /v1/services · v1.0.3
click any provider to preview context++ output
/ faq
No. The hosted backend is the default path. Local mode exists for development, but the published CLI is designed to work against the branded production API.
Yes. Set CONTEXTPLUSPLUS_API_KEY and CONTEXTPLUSPLUS_API_URL, then run contextplusplus process in your pipeline.
It is the same engine and quota model behind a terminal-first interface. Pick the surface that fits the workflow without changing the output shape.
/ pricing
CLI, MCP, and the HTTP API all sit on the same conversion engine and subscription model. Pick the surface that fits the workflow.
See pricing →For steady, predictable pipelines.
Higher limits for production load.
checkout via Stripe · POST /v1/billing/checkout · cancel anytime in the billing portal