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

# Verified publishers

> How the verified publisher badge works: prove you control your website's domain with a DNS TXT record, apply for review, and keep the badge.

Verified publishers carry a blue tick next to their name — on marketplace cards, on their API pages and on their publisher profile. It tells API consumers that JoJ API has checked that the publisher is the organization it claims to be.

The badge is two things at once: a mechanical proof that you control your website's domain, and an editorial decision by our team that the profile genuinely represents that organization. Only approved publishers show the tick; every other state is visible to you alone.

## Who can apply

* **Organizations with their own domain.** Verification binds to the registrable domain of the **website** on your public profile (Settings → Account → Public profile links). Shared hosting domains where anyone can get a subdomain — `github.io`, `vercel.app`, `notion.site` and the like — cannot be verified.
* **Publishers with at least one API.** The badge is shown on your APIs, so create one in the Studio first. At review time we expect at least one listing to be **Public**.
* **Profiles that match the website.** The display name, logo and links on your profile should present the same organization as the website, and the website should show a verifiable identity (legal name, about or imprint page, contact details).

## Verifying your domain

1. Set your website under **Settings → Account → Public profile links** and save.
2. In the **Verified publisher badge** card, click **Verify domain**. You get a TXT record to publish.
3. Add the record at your DNS provider and click **Check DNS**. DNS changes can take a few minutes to propagate; you can check once a minute.
4. Once the record is found, the domain is verified and **Apply for the badge** appears.

The record to publish:

| Field | Value                                                                          |
| ----- | ------------------------------------------------------------------------------ |
| Type  | `TXT`                                                                          |
| Name  | `_jojapi.your-domain.com` (some DNS panels want only the host part, `_jojapi`) |
| Value | `jojapi-verify=…` — a token unique to your account                             |

Your website URL can point anywhere on the domain — `https://www.example.com/about` verifies `example.com`. Subdomains of country second-level domains work as expected (`example.co.uk`).

## Review

Applying sends your profile to our team. We look at the domain, the website, the profile and the APIs you publish, and email you with the decision — usually within a few business days.

If the application is **not approved**, the reasons are shown in the settings card and in the email. You can apply again **14 days** after the decision, once the points are addressed; the domain does not need to be verified again unless the website changed.

## Keeping the badge

The badge stays bound to the domain you verified:

* **Keep the TXT record in place.** It is re-checked regularly. If the record goes missing you get an email, and if it is still missing after **30 days** the verification lapses and the badge is removed.
* **Keep the website on the same domain.** Changing the website on your profile to a different domain resets the verification immediately — verify the new domain and apply again.
* **Keep the profile honest.** The badge can be revoked if the profile stops representing the organization or for trust and safety reasons; the reasons are shared with you, and you may apply again after the cooldown.

A lapsed or revoked badge never affects your APIs, subscriptions or payouts — only the tick.