Resolve
Managed superpowers first.
Resolve is the access layer that starts agents on Rhumb-managed capabilities through governed API key or wallet-prefund, then lets operators bring their own systems in only when the workflow actually needs them.
The promise is simple: managed superpowers first, secure bridges second.
Managed superpowers first
Start with Rhumb-managed capabilities so an agent can search, extract, generate, verify, enrich, and route work without you provisioning a pile of vendor accounts first.
Bring your systems only when needed
When the job touches your CRM, warehouse, Slack, GitHub, or internal tools, switch to BYOK or Agent Vault and keep control of your own systems of record.
One surface, not a tool graveyard
Agents discover capabilities, resolve the right provider, estimate cost, and execute through the same Resolve surface instead of learning a new integration for every task.
Before you wire this deeper
Want to inspect the trust story first? Read Trust, inspect the public Methodology, or use the provider dispute path if a score, coverage claim, or launch claim looks wrong.
Product promise
Start with managed magic. Bring your systems only on the boundary.
Start with a managed capability layer that feels like agent superpowers. Search the web, scrape pages, generate images, validate emails, enrich people and companies, find candidates, classify documents, transform media, and more, all through one surface.
Then, when the workflow crosses into your actual business systems, connect only the systems that matter. CRM, support, GitHub, Slack, databases, warehouses, storage, and internal APIs stay under your control through BYOK or Agent Vault.
Agents can use Resolve as a wide capability layer on its own, or as the bridge between broad managed capabilities and tightly-scoped operator-owned systems.
Default mental model
1. Ask for the capability
Think in jobs to be done, not vendor APIs.
2. Use the managed path first
If Rhumb can provide the capability directly, the agent should not need separate upstream accounts.
3. Connect systems only on the boundary
Bring BYOK or Agent Vault only when the workflow touches your own data, permissions, or production systems.
4. Keep one operational surface
Discover, resolve, estimate, and execute through the same Resolve interface.
Lane 1
Managed superpowers
Broad, zero-config capabilities where Rhumb owns the provider accounts and the capability itself is the product.
Lane 2
Secure bridges into your systems
Tight, scoped access when the job needs your data, your permissions, or your production environment.
- CRM and support systems
- Slack, GitHub, and internal collaboration tools
- databases, warehouses, and object storage
- deployments, CI, and control-plane systems
- operator-owned APIs and internal business tools
Credential paths
Three credential paths, one trust story
Resolve should not force every capability through the same trust model. Rhumb-managed, BYOK, and Agent Vault each exist for a reason.
Default magic
Rhumb-managed
Best for zero-config utility capabilities where Rhumb can own the provider account and expose the capability as the product.
Your systems
BYOK
Use when the capability touches your account data, workspace, or production systems and you want direct control over the upstream credential.
Agent-native custody
Agent Vault
Use when the credential should stay encrypted in Rhumb custody, scoped to the agent, and be injected only at execution time.
Honest current state
The promise is bigger than today’s launchable surface.
Current launchable scope: research, extraction, generation, and narrow enrichment — not general business-agent automation.
Not every service or capability in the index is executable through Rhumb today. Discovery breadth is wider than current callable coverage.
Why this matters
For operators
Fewer vendor accounts to provision up front, fewer keys scattered across tools, and a clearer path to controlled system access only where it matters.
For agents
A much broader useful action surface on day one, with the option to reach into customer-owned systems without abandoning the same interface.
For product
Managed superpowers create the magical first experience. Secure bridges create depth, retention, and operational legitimacy.
For launch
The win condition is not raw connector count. It is whether an agent feels suddenly more capable after getting Resolve once.