Deli handles the credentials.
Store API keys in an encrypted vault, grant scoped access via OAuth, and proxy calls to OpenAI, Anthropic, Stripe, and GitHub — without exposing raw keys.
Store your API keys securely. Grant scoped access to platforms. Revoke anytime. Your keys, your control.
Integrate OAuth 2.0 with PKCE. Proxy API calls through Deli. Never touch user credentials.
Authenticate via client credentials. Get short-lived tokens. Make proxied API calls with full audit trail.
Deli's core infrastructure is live and deployed. Here's what you can use right now, and what's on the way.
API keys are encrypted with AES-256-GCM at rest. Decrypted only in-memory during proxy forwarding. Never logged, never exposed.
Full authorization server with consent screens, authorization codes, refresh tokens, and token revocation. RFC 6749, 7636, 7009, and 8414 compliant.
Route requests to OpenAI, Anthropic, Stripe, and GitHub through Deli. We inject credentials server-side, you get responses.
Fine-grained permission model. Every proxied request is logged with service, endpoint, status code, and response time.
Generate time-limited shareable links for stored credentials. One-time-use, password-protected, or open. Full audit trail on access.
Run a local HTTP proxy. Agents use placeholder tokens — real credentials are injected only for allowlisted hosts. No cloud required for local development.
withdeli-cli on npm for agent auth from the terminal. @deli/sdk for TypeScript with PKCE, service helpers, and Express/Next.js integrations.
Link Ethereum addresses to agents via ERC-8004. Per-call crypto payments for proxied API calls. Infrastructure is built — activation is coming.
Where we are and where we're headed.
Store your keys securely, or integrate Deli OAuth into your app. Either way, you're up in minutes.