ai.capxule/capxule · v2026.10.13 · communication
Capxule is healthy: it completed an MCP handshake in 1984 ms and exposes 12 tools. It scores 63/100.
The context marketplace: expert guided journeys your assistant runs step by step.
Add to my toolfindr inventory →
Healthy · last checked 2026-10-14T08:59:51.835Z UTC
| Checked (UTC) | Status | Latency |
|---|---|---|
| 2026-10-14T08:59:51.835Z | ok | 1984 ms |
| health | 18.1 / 25 |
| authEase | 15 / 15 |
| toolQuality | 15 / 15 |
| maintenance | 7 / 15 |
| adoption | 0 / 10 |
| usage | 0 / 10 |
| security | 8 / 10 |
find_capsule Covers: 155 guided journeys across 17 areas: Finance (32, e.g. Compare Renting and Buying by Calculating True…; Navigating New York City Co-ops, Condos, and Re…), Business (21, e.g. Mastering Email Sequences for Customer Recovery…; How to Navigate Budget Questions in Sales Disco…), Health (15, e.g. list_categories Lists the areas the published guided journeys cover: each category slug, a readable label, how many journeys it holds and a few example titles. Use it when the user asks what is available, or before browse_catalog. Free; never costs a turn. Never say a price.browse_catalog Pages through the published guided journeys, optionally within one category (a slug from list_categories), featured first. Returns the same cards as find_capsule plus total and next_offset. Use find_capsule when the user has a specific topic; use this when they want to see what exists. Present a fewopen_journey Opens (or resumes) a guided journey and returns the session contract: `session` (keep it), the stop list (titles only), the capabilities, the limits in turns, the rights, and the first beat (static, costs nothing). Find-or-create: calling it again for the same journey returns the same session with `turn Sends the user's move and returns ONE whole beat: `answer`, `statement`, numbered `options` with opaque ids, `media`, `progress`, `limits` and `narration.text_fallback` (ready to relay). On a number or an option echoed back send `pick` with that option id (add `said` when the user said more); on anyjourney_state Where the user is in the journey: position (stop, visited of total), `remaining` (stops left, percent done, and each top-level topic's visited of total), mode, the goal line, the chosen way, practice stats, limits and a `resume_line` you can say. Hosts that render apps show it as a map card. Call itmake_artifact Composes the user's takeaway (kind "takeaway") from THIS conversation: what they asked, what landed, the stops they visited. Bound principals only: an open principal that has not bound an account gets not_available with reason bind_required and next = account_bind (offer to set the account up right handoff Mints a resume link and code for this session so the user can continue on the website or in another assistant. Call it before switching hosts or ending; give the user `resume_url` (or read them `resume_code`) and say `resume_line`. Costs nothing. Rules (binding): Relay `answer` and every `options[].restart_journey Starts the user's walk through a journey over: back to the first step, visited stops cleared, any drill or mock session closed. Turns already used stay used and the practice record is kept. Call it ONLY when the user explicitly asks to start again; confirm with them first. Returns the same session caccount_status Whether this connection is bound to an account, whether that account includes the premium journeys (`premium`, a flag) and unlimited web turns, the assistants connected to it (`delegations`, with their scopes in plain words), `manage_url` for the human (a web page; never a checkout), and for a machiaccount_bind Starts binding an account for the user without a web visit. Ask for an email in the user's own words, read back the masked address, then call with method email_code (the default); the user reads you the six-digit code and you call account_verify. Alternatives: magic_link (a link they tap), sms_code account_verify Completes account_bind: pass the challenge it returned and the code the user read you (digits only; spaces are fine). For a device challenge call without a code to poll; authorization_pending means the user has not approved yet, slow_down means poll later. Returns bound: true with the principal, thehttps://github.com/Capxule/capxule-ai · ? stars · last push ? · website