Orb to Metronome Migration
v1.2.3Point this agent at your Orb codebase and ask it to plan your migration.
What it does
- Map your Orb integration (metrics, pricing, subscriptions, webhooks)
- Plan a phased migration with code snippets at each step
- Scaffold the Metronome setup calls
- Sandbox — execute scaffold against a Metronome test environment and report PASS/PARTIAL/FAIL evidence
- Stripe evidence (optional) — read one exact delivered Stripe test Invoice and compare verified expectations
Current scope
This solution scaffolds Metronome resources and optional customer/contract billing-provider linkage to an existing Stripe test-mode connection in Metronome. An optional Stripe test key enables read-only validation of one exact delivered test Invoice. The solution does not create Stripe fixtures, execute payments, replace Stripe webhooks, or replace portal flows.
Prerequisites
METRONOME_API_TOKEN— Metronome test environment tokenMETRONOME_BASE_URL— explicit environment URL, for examplehttps://api.staging.metronome.com- For Stripe delivery tests: connect a Stripe test account to the Metronome environment with Metronome's OAuth flow
STRIPE_TEST_KEY— optional; read-only exact-Invoice validation only
What’s included
- Orb to Metronome Migration AssistantAgentTemplate
Crawls Orb codebases, plans migrations, generates Metronome scaffolding, and validates Metronome plus optional read-only Stripe test evidence.
Get started
Publish your work where your customers look
Package one repetitive manual workflow, and every customer installs the same thing.
Calls are with a founder, not a sales team.