# Provider profiles & trust

Every organization can maintain a **public profile** at `/providers/{slug}`. Profiles help consumers and agents evaluate who is behind an API.

## Fields

- Display name & slug
- Avatar (upload or `https://` URL)
- Bio (≤ 160 chars) & long-form about (markdown)
- Website, docs URL, support email, location
- Socials: GitHub, X, LinkedIn, Discord, YouTube, Telegram
- `public_profile` toggle

## Visibility

- Opt-in via `public_profile: true`, **or**
- Automatically listable when the org has **live APIs**

## Trust badges

| Badge | Meaning |
|-------|---------|
| Email verified | Owner email verified |
| Terms accepted | Ozma platform/reseller terms attested at publish |
| Provider terms | Optional API-scoped legal document (display or required acceptance) |
| Payouts verified | Stripe Connect account linked |
| Founding Provider | Launch founding flag |

## Agent access

```bash
npx @ozma_app/cli providers
npx @ozma_app/cli providers acme
npx @ozma_app/cli profile show
npx @ozma_app/cli profile update --bio "…" --website https://… --public
```

REST: `GET /v1/providers`, `GET /v1/providers/:slug`, `GET|PATCH /v1/me/profile`, `PATCH /v1/provider/apis/:id` (metadata + completeness scorecard).

## Legal documents

Providers may publish terms, privacy, and other documents via `POST /v1/provider/documents` → activate. See [Publish & verify](/docs/guides/publish-api).

MCP tools: `list_providers`, `get_provider_profile`, `get_my_profile`, `update_my_profile`.