Idiomatic Ruby.
Not just a REST shim.
A real Ruby gem — not a thin REST wrapper. Works in Rails, Sidekiq jobs, and Hanami apps.
Integration flow
Host
Not just a REST shim
Auth
ORSA_API_KEY
Tools
3 ready workflows
Start free, no card required, most teams ship a first integration in under ten minutes.
The integration should feel
like a product surface
These pages now explain the workflow the integration enables, not just the installation command.
Resource-oriented objects
First-class error types
Sidekiq-friendly retries
From install command
to production workflow
The page now teaches how the integration fits into the customer's stack before asking them to copy setup code.
Install (preview)
Install the integration and attach one Orsa API key.
Use extraction tools
Resource-oriented objects First-class error types Sidekiq-friendly retries
Rails signup
After UserCreated job, enqueue `Orsa::Brand.retrieve(domain)`.
- Setup format
- rubyCopy-ready setup block included below.
- Auth
- ORSA_API_KEYSame key for every endpoint and integration.
- Workflow count
- 3Rails signup, Billing, Admin
- Docs
- API referenceUse docs once the integration is connected.
Install (preview)
Keep setup concrete and copy-ready, then show the higher-value workflows the integration makes possible.
# Gemfile
gem "orsa-ruby", github: "orsa-dev/orsa-ruby"One key,
many surfaces
Integrations should not feel like wrappers around JSON. They should show how Orsa becomes a reusable context layer inside the tools teams already use.
- Use Orsa from automation tools, AI clients, no-code builders, or your own product.
- Reuse the same endpoint contracts across integrations and custom code.
- Move from a single connected workflow to a broader context platform without changing vendors.
Workflow 01
Rails signup
After UserCreated job, enqueue `Orsa::Brand.retrieve(domain)`.
Workflow 02
Billing
Parse statement descriptors in a Sidekiq worker.
Workflow 03
Admin
Render brand previews in ActiveAdmin dashboards.
What teams build
once this is connected
Integrations should map to jobs: enrichment, context capture, routing, and automation that makes Orsa part of the customer's existing stack.
Rails signup
After UserCreated job, enqueue `Orsa::Brand.retrieve(domain)`.
Billing
Parse statement descriptors in a Sidekiq worker.
Admin
Render brand previews in ActiveAdmin dashboards.
Connect Orsa
where your team already works
Start with the integration, then use the same API key for every extraction and brand context workflow.
One API key for every Orsa endpoint · No card required to start.