> ## Documentation Index
> Fetch the complete documentation index at: https://docs.robase.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For chatbots and coding agents, start at /guides/ai-agents.
> Hosted MCP: POST https://api.robase.dev/mcp (Streamable HTTP). Auth: Authorization: Bearer robe_… or robe_agent_….
> Phase 1 tools: get_pricing, send_otp, verify_otp, get_otp, send_sms, get_sms. No payment or top-up tools.
> Call get_pricing; treat listed:true as marketed markets (NG, GH, KE, ZA, GB, BJ, CI, US). Do not invent countries or delivery percentages.
> Prefer OTP-shaped tests such as "Your Robase test OTP is 123456". Do not send Hello or Good morning as tests. Match errors on error.type.

# Setup wizard

> What each step on /app/setup asks for, what you can skip, and why a top-up comes before any send.

Open [Setup](https://robase.dev/app/setup) after you create an account. The address keeps the step in the query (`?step=1`, `?step=2`, or `?step=3`) so a refresh stays on the same screen. Progress saves after each step.

A new workspace walks four steps: **Business**, **Add credits**, **Sender ID**, and **Test send**. The setup address renders the first three. Test send is the last step, and it lives on the [overview](https://robase.dev/app).

## Business

This step stores how the workspace is billed and how messages are worded.

| Field | What it is for |
| - | - |
| Billing country | Tax and company checks, and the starting point for the billing currency. |
| Billing currency | The currency a top-up is charged in. You can change it until the first paid top-up settles. After that it stays locked. Contact support to change a locked currency. |
| Language | English or French. This language is used for the OTP and SMS you send, and for the emails we send your team. |
| Timezone | How the dashboard shows times. The API still returns UTC. |
| OTP delivery | Optional. SMS only is the default. You can change it later under Settings. |

Saving this step is what marks the business details done.

## Add credits

This step is required. The screen marks it required, and there is no skip.

A new account starts with **0 credits**. There is no free trial. A send needs a balance, so the first successful top-up has to land before any OTP or SMS goes out. Until it does, the API refuses the send with **402** `insufficient_credits` and nothing is sent.

The first successful top-up adds **10 bonus credits**, once per account. The bonus is not itself a purchase. Later top-ups do not add it again.

Credit prices are not printed here. Read the live list from `GET /v1/pricing`, or from [Pricing](https://docs.robase.dev/sms/pricing.md) and the billing page, which both use that response.

## Sender ID

Transactional SMS needs the workspace's own approved sender ID. Without one, `POST /v1/sms/send` returns **422** `sender_id_required` and nothing is charged. OTP uses Robase sender names, so a login code does not wait on this step.

You can skip the step after the workspace is funded. The button reads **Skip for now, I only need OTP**. The note on that screen says OTP uses Robase sender names, transactional SMS needs your own approved sender ID, you can request one from Sender IDs after the first successful top-up, and approval usually takes 1 to 4 weeks.

Applying for a sender ID needs at least one successful credit purchase. Bonus credits do not count as that purchase. Sender ID rules exist for several countries, and the dashboard lists the countries currently open. See [Sender IDs](https://docs.robase.dev/sms/sender-ids.md).

If the skip does not open the dashboard, the page says it could not open the dashboard. Stay on the step and try again. The gate opens only after the business step is saved and a purchase has succeeded.

## Test send

Test send is step 4. It is not a screen on `/app/setup`. When steps 1 to 3 are done, setup sends you to the overview, where the test is. A `?step=4` address is not a setup screen. The step counts as done only after that test message is delivered.

The test uses real credits and sends to a real phone. See [Test send](https://docs.robase.dev/dashboard/test-send.md).

## What you can reopen

A step you have already reached can be opened again from the progress rail, including with `?step=`. A step you have not reached yet is rewritten to the first unfinished screen. You cannot jump to Sender ID before the top-up, and you cannot jump to Add credits before Business is saved.

## Older workspaces

A workspace created before the current rules sees Business and then the overview. Saving Business leaves setup. Setup also stays closed when it was already completed, when the workspace has a paid top-up, or when it already has a successful send.

Those workspaces keep the sender setup they already had. New workspaces follow the rule above: transactional SMS needs their own approved sender ID.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.