Nothing is published yet — here is exactly what is coming
There is no ORVEXIA package on npm, no public API and no documentation site. This page is the honest version of a developer portal: the plan, the principles, and how to get in early.
Before you try: @orvexia/sdk does not exist on npm, orvexia is not a CLI you can install, and there is no api.orvexiatech.com. If you find any of those published somewhere, it is not us.
What we are building, and where each piece stands
Stages are updated as they change. None of them is available today.
Typed SDKs In design
TypeScript first, then Python. Generated from the API description so the types cannot drift from the server.
REST API In design
Predictable resources, cursor pagination, idempotency keys on writes, and a version in the URL that we do not break.
CLI Not started
For the things a dashboard is bad at: bulk imports, environment promotion, and running the same command in CI.
Signed webhooks In design
Every payload signed, every delivery retried with backoff, and a log you can replay from.
Sandbox Not started
A free environment with seeded data, so the first integration never touches anything real.
Logs & usage Not started
Request logs you can search and quota visible before you hit it, not in the invoice.
Five commitments we are designing against
Want it early?
Early access will go to people building something specific, because that is the feedback worth having. Tell us what you would integrate and with what.