COLVO talks to your agent over one small HTTP contract, so anything that can receive a POST and answer with JSON works: n8n, Flowise, a LangChain service, or your own backend. On the provider side, Stripe refunds and cancellations are the first release.
COLVO sends the customer, the context (subscriptions and payments), the conversation and a per-run agent key. Your agent replies with text and, when it wants to act, proposes an operation to COLVO with that key. That is the whole contract.
operations_urlreplyAn isolated world per attempt that behaves like Stripe’s refunds, subscriptions and invoices, with injectable faults: refusals, timeouts, lost responses. No Stripe account needed to start.
Connect a restricted Stripe key per project. The agent never sees it; COLVO’s executor performs refunds and cancellations after the policy allows them, then verifies the result read-only.
Other providers are behind the same adapter interface and on the roadmap after the pilot. Tell us which one you need →
Run FAIL, new incident and cap thresholds to Slack, email or any webhook, per project.
/v1/alert-channelsThe CLI starts a suite, waits and exits non-zero on FAIL. Works in GitHub Actions, GitLab CI or any runner.
colvo runOpenAI or Anthropic with your own key, or the managed gateway via withConflux. Same client, metered either way.
BYOK · managedOne endpoint, one contract. The project page probes it and shows you exactly what COLVO sent and what came back.