Full beta toolkit

The same provider operation catalog is available through the REST API, CLI, local MCP and the hosted chab_operation_start tool. You can begin with guest credentials or guest browser OAuth without creating an account. The browser homepage offers convenient starting examples; API and CLI clients can use the complete supported catalog.

Supported does not guarantee that an operation is ready at this moment. GET /v1/health reports exact covered_operation_keys for healthy families. An operation without current coverage is paused even if another operation in its family works. Provider configuration changes and operator pauses can remove coverage immediately. GET /v1/cli/compatibility advertises the current guest operation keys and credential scopes. Use GET /v1/llm/models to select model aliases.

The manually monitored beta can retain a successful operation test while its deployed version and service configuration stay unchanged. An old test alone does not pause that mode, and does not promise continuous uptime. Operators receive stale-test and any-volume failure alerts; failures or configuration changes can still pause new starts. See Service Health.

Free credentials share promotional credits and the €10 free-use budget. Expensive operations may exhaust the remaining allowance sooner. Free language-model input is limited to 8,192 estimated tokens, file conversion to 2 MiB, research to 3 cited sources, and screenshots to the viewport rather than full-page capture. Research's source count does not replace the separate upstream work limits described in the budget guide.

Free accounts also have monthly request limits: 100 starts per family for scraping, screenshots, conversion and language models, and 10 for research. The daily request limits, available promotional credits and shared cash budget can stop work before those monthly limits are reached. Free file storage is limited to five files and 10 MiB retained, with a 2 MiB limit per file. Promotional starts do not accept callbacks or dry_run; those examples in individual endpoint references apply to eligible paid funding. Research comprehensive mode remains Scale-only.

For conversion, upload a file with POST /v1/files, wait for its state to become available, and pass {"source":{"type":"file_id","id":"fil_…"},"output_format":"text"} to POST /v1/convert/file. A previous artifact owned by the same principal can also be used where the endpoint accepts an artifact source. Translation accepts inline content or a reusable artifact; first convert an uploaded document when you need text for translation. Scanning, source ownership, retention and input format checks still apply.

Hosted MCP uses browser OAuth and explicit connection spending consent. A REST guest bearer token is not a hosted MCP OAuth token. Each hosted connection owns its operations and reusable artifacts; it cannot automatically read files or history created by another credential. Hosted MCP can start all 19 operations and retrieves screenshot, conversion and other file output through chab_operation_artifact: choose content: "inline" for bounded image/text content or content: "link" for a short-lived protected download. See Hosted MCP for paging, byte limits and the beta transfer allowance. A separate REST or CLI credential cannot fetch an artifact created by a hosted MCP connection. For your own conversion input, use the hosted MCP file-upload handoff when its tool is available. Connected Mail and Drive are closed in this initial accountless beta; they are not anonymously delegated. Account administration likewise requires the appropriate account access.