Skip to main content
Always use the scoped name @elding/sdk. npm install elding (without the @elding/ scope) installs an unrelated third-party package, not Elding.
Write your HTTP API integrations once and use them in both development and production. Switching between the local proxy and direct provider access is automatic.

configure()

The recommended pattern: write once and deploy anywhere.
Elding only handles HTTP API keys. DATABASE_URL, JWT_SECRET, REDIS_URL, and other non-HTTP variables remain with your hosting platform.