Dashboard
Start or resume setup from the Dashboard.
Sidebar
The left sidebar holds every dashboard destination.
| Destination | Route | What you find there |
|---|---|---|
| Dashboard | /dashboard | The QuickStarts and the work to continue. |
| Gateways | /gateways | Your gateways. Open one to edit, test, activate, or pause it. |
| Recipes | /dashboard/recipes | Your Recipes, and the link to create a Recipe. |
| Analytics | /analytics | Calls, payment states, and call outcomes for your gateways. |
| API Keys | /api-keys | The API keys of the account. Only an Owner can manage them. |
| Playground | /playground | Try a service. Send a paid call from the browser. |
| Spend Grants | /developer/spend | Device commands, grant approval, and payment requests. |
| Balances | /settings/balances | Your balances and the payout accounts. |
| Studio | /explore | A row at the foot of the sidebar. It opens Explore, where a build in Studio starts. |
The bell at the head of the sidebar opens the notifications inbox.
QuickStarts
The Dashboard shows three QuickStarts. It does not show a gateway inventory. Open Gateways to view the gateway inventory for the active account.
| QuickStart | Route | Complete when |
|---|---|---|
| Publish an API | /gateways/new | A gateway is active. |
| Authorize an agent | /developer/spend | A grant is active. |
| Create a Recipe | /dashboard/recipes/new | A Recipe is published. |
Gateway and Recipe resume actions select their saved account before the focused route opens.
Each card has a factual outcome, a Docs link, and a dismiss control. Publish an API turns an existing service into an agent-ready product. Authorize an agent sets bounded spend authority with limits and expiry. Create a Recipe combines tools into a reusable workflow.
Each card shows one guide step. Arrow controls move between steps. Progress dots show the current step. The route action says Start, Continue, or Review. Start uses warm gold. It opens the focused route from a fixed card footer.
The Dashboard shows four equal card columns on wide screens. It uses two columns below 1080px and one below 680px. You can dismiss one card without dismissing the other cards. The Dashboard keeps each dismissal in your browser. If you dismiss every card, the Dashboard hides the QuickStarts. Continue remains when saved work needs action.
Each card shows one status.
| Status | Meaning |
|---|---|
| Ready to start | The source has no saved item. |
| In progress | A saved item needs an action. |
| Complete | The QuickStart completion rule is true. |
Pending, denied, revoked, and expired grants show In progress. Draft gateways and draft Recipes also show In progress. The Dashboard has no blocked status.
Continue
Continue is named Continue where you left off. It lists draft or paused gateways, grants that are not active, and draft Recipes. The Dashboard shows at most five rows, and at most two rows of each kind. The most recent rows come first. Continue has no control to show more rows. Open Gateways or Recipes for the full lists. The Dashboard hides Continue when it has no rows.
A gateway or Recipe row selects its account before it opens the focused route.
If Bazantic cannot read a source, the related card remains actionable. The source adds no Continue row.
Pending organization invites remain above the QuickStarts. Invite decisions are not a QuickStart.
Focused routes
/gateways/new owns Connect, Review, Save, and Activate. It saves incomplete setup as a draft.
/developer/spend owns device commands, approval, funding, and payment requests. An active grant completes authorization.
For a pending grant, return to the requesting agent. Create a new grant after the pending grant expires.
Funding and a first payment request are optional after activation. Team requests remain in Organization settings.
/dashboard/recipes/new and the Recipe editor own Describe, Review, Save, Test, and Publish.
Recipe recovery uses the caller, active account, and page path. A Recipe test advises the next action for its saved revision.
A current complete test advises publication. A missing, stale, failed, cancelled, or timed-out test advises review or another test.
The test does not gate publication. The existing saved-draft and input-schema rules still apply.
Use Playground to try a service. Playground is outside the QuickStart set.