Run the five failure checks.
These controlled fixtures confirm the hosted Rust verifier. They do not test your customer integration.
FROM A TEST RECORD TO YOUR FIRST CUSTOMER
Connect one workflow.
Know when it’s ready.
Start in your support team’s test environment. Define the refund policy, connect an independent reader, and check failure recovery before real actions.
Keep your existing agent.
Use the SDK with your own actions and independent state reader. Follow the acceptance procedure for a normal refund, a timeout after commit, a rejected action, and a duplicate attempt.
Read the customer guide03 · CHECK YOUR ACCOUNT
One key for your customer.
Runtime keys are scoped to one customer. Paste yours to check its allowance. It stays in this page’s memory and is sent only to Horizon.
Checking managed service availability…
Put the runtime key in your server’s HORIZON_API_KEY environment variable. Keep your administration key separate. Never expose either key in browser code or a public repository.
GUIDED PILOT · $500 ONCE
Prove it on your workflow.
One refund workflow, 30 days, 10,000 runs, two setup sessions, and a shared acceptance review. No automatic renewal or charge from this form. Once scope and setup are agreed, we send a private Stripe payment invitation.
Acceptance means your test records confirm the expected outcome, failures block later actions, retries do not duplicate refunds, and setup is repeatable.