Dashboard
The dashboard is the first screen you see after signing in. It changes based on where you are in the setup journey. Before your first account type, the dashboard shows a setup checklist. Complete each step in order: request your first vaults, create an account type, configure your SIWE domain, and review the integration guide. The checklist disappears once you finish. After setup, the dashboard shows three metrics: total account types, pending flow plans, and total user accounts. A table lists your top 5 account types by account count with status indicators. The quick start card stays visible at the top. It shows your publishable key, an npm install command, and a “Copy to LLM” button that exports your full SDK context. Use this to paste into an AI assistant when building your integration.Catalog
The catalog shows every vault scored by Blend’s risk vendors. Browse by vendor, filter by chain or risk tier, and request the vaults you want.Vendor tabs
Switch between vendor tabs to see different vault categories. Each tab has its own filtering and search.
Filtering and search
The Philidor tab supports filtering by chain, risk tier, and free-text search. Each vault card shows the score, chain, protocol name, and current APY. The risk tiers break down like this:Requesting vaults
Select up to 5 vaults at a time and click Request. Blend provisions on-chain infrastructure for each vault you request. Once activated, the vault appears in your organization’s catalog and you can use it in account type allocations. Vault requests go through a short approval window. You’ll see the status on your catalog page.Account types
Account types are the products your users interact with. Each one ties together vault allocations, credentials, and flow plan settings.Settings
Every account type has these settings:Vault config lifecycle
When you change allocations on an account type, the new config goes through a pipeline before it goes live.
Weight-only changes (same vaults, new percentages) skip Pending and Provisioning. They go straight to Ready with a 24-hour timelock.
Emergency bypass is available for the timelock. You’ll need to type the account type name to confirm. Use this only when you need to deploy changes immediately.
Pausing an account type
Pausing blocks new deposits. The SDK returns a 423 status code for deposit attempts, and deposit-related session transitions (lock, submit) are also blocked. Existing positions keep earning yield. Withdrawals always work - your users can get their money out at any time. You can unpause whenever you’re ready.Accounts sub-page
Each account type has an Accounts tab showing all user accounts. The table is searchable by account ID, user address, or Safe address. Click any account to see which chains its Safe is deployed on. You can disable individual accounts here. Disabling an account stops Blend from serving deposit and withdrawal calldata, but the user keeps full ownership of their Safe and funds.Publishable key
Find the publishable key on the account type detail page under Settings. Each account type gets its own key. Pass it to the frontend SDK when you create aBlendSdk instance.
The key format is pk_live_ followed by 64 hex characters. It’s safe to include in client-side code.
Portal operations
Manage flow plans, credentials, and your team day-to-day.
Test with Try Position
Test deposits and withdrawals directly in the portal.