# Buy a domain on BWEZE, registered in your name

> Search a name and its first-year price, pay from your workspace wallet, and register it in your own name. How .rw purchases work while accreditation is pending.

Source: https://domains.bweze.com/guides/buy-a-domain/ · Updated 2026-11-19

Buying a domain on BWEZE registers it and attaches it to one of your projects in one step. The price comes out of your workspace's prepaid wallet in RWF, and the domain is registered in your name.

## Search

Pass a bare name to check it across `.com`, `.app`, `.dev`, `.io`, `.co`, `.xyz` and `.rw`, or a full domain to check that one:

```bash
curl "https://api.bweze.com/v1/domains/search?q=mycompany" \
  -H "authorization: Bearer bw_sk_..."
```

From the CLI: `bweze projects domains search mycompany`.

Each result gives the `domain`, whether it is `available`, and `priceMinor`, the price of the first year in RWF. `priceMinor` is `null` when BWEZE does not sell that domain. BWEZE sells one name under a suffix, such as `mycompany.com` or `mycompany.co.rw`, and does not sell subdomains.

For `.rw` there is also `GET /v1/domains/rw/{name}`. It accepts publishable keys (`bw_pk_...`), so you can call it from a browser or an app. It returns `available` as `true`, `false` or `null`, and `null` means the registry could not be reached: treat the name as unknown. From the CLI: `bweze domain check mycompany`.

## Suffixes and prices

BWEZE sells these suffixes:

| Group  | Suffixes                                                                                                             |
| ------ | -------------------------------------------------------------------------------------------------------------------- |
| Rwanda | `.rw`, `.co.rw`, `.org.rw`                                                                                           |
| Others | `.com`, `.net`, `.org`, `.app`, `.dev`, `.io`, `.co`, `.ai`, `.xyz`, `.site`, `.online`, `.store`, `.tech`, `.cloud` |

Prices are per year and depend on the suffix; they are on the [pricing page](/pricing/). They come from BWEZE's published price list, `GET /v1/pricing`, and a price only goes up with 30 days' notice. The docs give the first year's price and do not describe renewal charges yet.

## Who can buy, and how it is paid

Workspace owners and admins can buy domains; developers and members cannot. An API token needs `dns:create`.

The first year's price leaves the wallet when you buy, as a `domain_charge` in your transactions. Domains are paid from the wallet alone, never from your plan's usage credit. If the wallet cannot cover the price, the purchase is refused with `402 insufficient_balance`, which adds `priceMinor` and `availableMinor`. Retrying fails until the wallet is topped up, and only workspace owners can top up, under **Billing**, by mobile money or card.

These refusals charge nothing either:

| Code                     | Why                                                                             |
| ------------------------ | ------------------------------------------------------------------------------- |
| `409 domain_taken`       | The domain is already registered                                                |
| `409 domain_unavailable` | It is already being bought through BWEZE, so a retried request never pays twice |
| `400 domain_not_sold`    | BWEZE does not sell this suffix, or it is a subdomain                           |

## Registered in your name

The domain is registered in your name. The `registrant` you send is its owner on record: the registrant and admin contact at the registry. The registry keeps these details and may show some of them in WHOIS lookups.

```bash
curl -X POST https://api.bweze.com/v1/projects/PROJECT_ID/register-domain \
  -H "authorization: Bearer bw_sk_..." -H "content-type: application/json" \
  -d '{
    "domain": "mycompany.rw",
    "registrant": {
      "name": "Aline Uwase",
      "organization": "My Company Ltd",
      "email": "aline@mycompany.rw",
      "phone": "+250.788123456",
      "street": ["KG 7 Ave"],
      "city": "Kigali",
      "countryCode": "RW"
    }
  }'
```

Required: `name`, `email`, `street` (one to three lines), `city` and `countryCode` (two letters). Optional: `organization`, `phone` (`+<country code>.<number>`; Rwandan numbers like `0788123456` are converted), `state` and `postalCode`.

The details are saved for the workspace, so a later purchase can leave `registrant` out. With nothing saved, a purchase without it is refused with `400 registrant_required`. Sending changed details makes them the new default; domains bought earlier keep the details they were bought with.

From the CLI:

```bash
bweze projects domains buy PROJECT_ID mycompany.rw \
  --name "Aline Uwase" --email aline@mycompany.rw \
  --street "KG 7 Ave" --city Kigali --country RW
```

The CLI shows the price and the owner before it buys. Without owner flags it uses the saved owner; with none saved, it asks in a terminal and refuses under `--yes` or `--json`.

## After you pay

A purchase is in one of three states:

- `registered`: the registrar accepted it at once.
- `requested`: BWEZE is registering it by hand, and it is already paid for. For most suffixes no registrar is connected yet, so for those a purchase starts here.
- `failed`: the domain could not be registered. The full price goes back to your wallet as a `domain_refund`, and `refund_transaction_id` is set.

`GET /v1/projects/{id}/register-domain` lists the project's purchases and the saved owner.

A domain bought through BWEZE is delegated to BWEZE's nameservers, `ns1.bweze.com` and `ns2.bweze.com`, and wired to your project automatically, with no DNS step on your side. Those nameservers do not answer on the public internet yet; the [DNS docs](https://docs.bweze.com/docs/dns) carry a notice until they do. For how records work there, see [DNS records](/guides/dns-records/).

## .rw today

For `.rw` names, `.co.rw` and `.org.rw` included, BWEZE is building a direct connection to RICTA, the registry. BWEZE is not yet an accredited `.rw` registrar, so that path is off. Until it is on, `.rw` availability is answered over RDAP, and a purchase is recorded as `requested` and completed by hand. The API is the same either way.

You pay up front. If the registry refuses the name, or BWEZE cannot complete it by hand, the full price goes back to your wallet. [How BWEZE will register .rw domains](/resources/epp-and-the-rw-registry/) explains the direct path and where accreditation stands.

## Full reference

Endpoints, fields and CLI flags are in the [domains docs](https://docs.bweze.com/docs/domains#buy-a-domain---post-v1projectsidregister-domain). Charges and refunds are in [Billing](https://docs.bweze.com/docs/billing#domains), and the `.rw` registry path in [BWEZE as a registrar](https://docs.bweze.com/docs/registrar).

## Sources

- [BWEZE docs: Domains](https://docs.bweze.com/docs/domains)
- [BWEZE docs: Billing (Domains)](https://docs.bweze.com/docs/billing)
- [BWEZE docs: BWEZE as a registrar (EPP)](https://docs.bweze.com/docs/registrar)
- [BWEZE docs: DNS](https://docs.bweze.com/docs/dns)
- [BWEZE docs: API reference (Domains)](https://docs.bweze.com/docs/api)
- [BWEZE docs: Workspaces and roles](https://docs.bweze.com/docs/workspaces)
- [BWEZE docs: CLI](https://docs.bweze.com/docs/cli)
- [BWEZE docs: Error codes](https://docs.bweze.com/docs/errors)
