Rhumb status
Answered our latest tool-list check 3 hours ago with 9 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 2 of 2 checks
- Last seen working
- 17 Nov, 06:17 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 17 Nov, 06:17 | Answered | 1.6 s | 9 |
| 16 Nov, 06:16 | Answered | 1.4 s | 7 |
Tools (9)
Read from the server on 17 Nov 2026.
- resolve
- Which model to call for a need, on the providers the user has accounts with: the provider's own model id, its price, capabilities and the reason. Give `providers` and a `task` or a `purpose`; add `needs`, `budget`, `origin` and other constraints to narrow it. `shape` asks for a team or an escalation ladder instead of one model. Counts as one call. An answer of `no_candidate` names what ruled every
- plan
- Reads a description of the work (a prompt, tags, attachment types and sizes) into a need, then resolves it as `resolve` does. Use `resolve` when you can state the task or purpose yourself; use this when you only have the user's words. Counts as more than one call. The answer depends on these goals; have the ones that matter in hand from the plan, the repository or the user before calling: cost (`o
- stack
- For an agent that has to work with named systems (Linear, GitHub, Postgres…): what to connect for each, and which model to call. Give `systems`, `target` (local or cloud) and the `harness` the agent runs in; add `model.providers` to get a model too. Each system's choice is its owner's own MCP server or command-line tool, or none, picked by fixed rules from public records and not reviewed; `warning
- platform
- Where an app's agent runs: give `requires` (baa, gpu, private_network, edge, long_running, websockets, scheduled_jobs, large_uploads) with `longest_turn_seconds` and `largest_upload_mb` where they apply, and the goals you have. The answer is `major` (a platform is warranted: a requirement no curated runtime meets, a model provider it hosts, or an account held; name its `system` in a `stack` call n
- list_models
- The catalog's models with each provider's offering, price, capabilities and quality scores, filtered by task, providers and needs. Returns 20 models unless `limit` says otherwise; page with `offset`. Counts as one call.
- get_model
- One model by id (`vendor/model`, e.g. `anthropic/claude-sonnet-4.5`): every provider's offering with its price history, capabilities, limits and dates, and the model's quality scores. Counts as one call.
- list_purposes
- The purpose presets `resolve` accepts: named jobs such as reading receipts or a coding agent, each with the task, needs and budget it stands for. Free.
- list_goals
- The goals an answer depends on (cost, depth, where a model's maker is based, where data may stay, languages, the kind of data, the accounts already held), each with one question to ask the user, the options to offer and the parameters each answer is sent as, and the rules for asking. Call it once when planning an app. Free.
- get_vocabulary
- Every name the other tools accept: tasks, capabilities and their levels, providers, origin groups, budgets and team strategies. Free.