@mybestie/check

@mybestie/check

CLI and stdio MCP for Bestie Check. Workspace packages (@repo/check-*) are bundled into Node bins; they are not published dependencies.

Preparing a document is always available. An agent can put a document into Check custody and read the free Claim and Assumption Quick Look: the claims the document makes and the assumptions they rest on.

Paid verification follows the server. quote, create, verify and repair run only when the Check server reports paid checks ready for your credential (check capabilities shows paidExecution.available). Otherwise they exit 4 with paid_execution_unavailable and the server's reason, after one read-only capabilities call, and dispatch nothing. Paid runs stay quote-bound: approve with the quote id, its hash and a credit ceiling. A bare --approve is always rejected, and nothing in this package approves spend for you.

npx @mybestie/check login
npx @mybestie/check capabilities
npx @mybestie/check prepare --file memo.pdf --wait --progress
npx @mybestie/check prepare --text "…" --wait --until first-claim
npx @mybestie/check inspect --upload <uploadHandleId>
npx @mybestie/check retry --upload <uploadHandleId>
npx @mybestie/check mcp

The stdio MCP server lists the paid tools only when the server says paid checks are ready; CHECK_MCP_AVAILABILITY=preparation|full overrides that explicitly.

Every command prints JSON on stdout (errors as JSON on stderr). A preparation snapshot carries nextAction: wait, review (Quick Look finished; partial if some units failed), retry (run check retry), replace_source (ingestion failed; prepare the same source again), or put_bytes.

Exit	Meaning
0	success (prepare --wait / wait: nextAction is review)
1	API or internal error
2	usage error
3	a valid state that needs you to act (retry, replace_source, put_bytes)
4	not available: paid verification is not open on this server for this account
5	timed out while still running; nothing failed, wait again
130	cancelled

check login runs a device/loopback PKCE flow against the Check API: it creates an S256 challenge, opens the browser authorize URL, polls /token, and stores the one-time token in a local credentials file (Unix 0600 / Windows ACLs). The CLI never reads a WorkOS session cookie. BESTIE_API_KEY still overrides the stored file. AI_GATEWAY_API_KEY is unrelated and ignored.

check mcp serves the same preparation tools over stdio (inspect_capabilities, prepare_deliverable, prepare_file_upload, confirm_file_upload, get_preparation, retry_preparation, plus reads of existing checks). Paid tools are not listed; CHECK_MCP_AVAILABILITY=full is for surfaces whose paid route is released.

Published on the public npm registry as @mybestie/check (@bestie is a third-party npm user and cannot be used). The journey contract is packages/check-api-contracts/AGENT-JOURNEY-CONTRACT.md in the monorepo.