Fully typed,
tree-shakeable.
First-class TypeScript for every endpoint. Tab-completion from `new Orsa()` through nested clients.
Integration flow
Host
tree-shakeable
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.
Native fetch transport
Automatic retries on 429/5xx
Strict request + response types
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
Install the integration and attach one Orsa API key.
Use extraction tools
Native fetch transport Automatic retries on 429/5xx Strict request + response types
Edge + Node
Same package in Next.js route handlers, workers, or scripts.
- Setup format
- bashCopy-ready setup block included below.
- Auth
- ORSA_API_KEYSame key for every endpoint and integration.
- Workflow count
- 3Edge + Node, Monorepos, Testing
- Docs
- API referenceUse docs once the integration is connected.
Install
Keep setup concrete and copy-ready, then show the higher-value workflows the integration makes possible.
pnpm add orsaOne 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
Edge + Node
Same package in Next.js route handlers, workers, or scripts.
Workflow 02
Monorepos
Share a thin wrapper that injects org-level API keys.
Workflow 03
Testing
Mock the `Orsa` class with stubbed sub-clients in Vitest.
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.
Edge + Node
Same package in Next.js route handlers, workers, or scripts.
Monorepos
Share a thin wrapper that injects org-level API keys.
Testing
Mock the `Orsa` class with stubbed sub-clients in Vitest.
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.