# Public profiles & offers

> Publish a provider identity and individual computer/model offers while keeping Serving under separate control.

A public profile lets developers discover the computer/model offers you choose to publish. Manage it in [Provider profile](/dashboard/provider-profile). Publication is optional and separate from Serving and Auto routing.

## Create your public identity

Save a profile with a display name, unique handle, and short description. An HTTPS website and avatar are optional. The public page uses `/providers/{handle}`.

| Field        | Limit                                                                      |
| ------------ | -------------------------------------------------------------------------- |
| Display name | 1–80 characters; cannot be blank.                                          |
| Handle       | 3–40 lowercase letters, digits, or hyphens; starts with a letter or digit. |
| Description  | Up to 160 characters.                                                      |
| Website      | Optional HTTPS URL, up to 300 characters, without embedded credentials.    |
| Avatar       | PNG, JPEG, or WebP; decoded size up to 256 KiB.                            |

Save the profile before uploading an avatar. Your public details are self-described; Router does not present them as verified identity or reputation. Choose details you intend to share publicly.

## Publish individual offers

1. Follow [provider setup](https://router.optimai.network/docs/providers/getting-started.md) and save pricing for a supported computer/model revision.
2. Open Provider profile and review your saved offers. New offers start unpublished.
3. Set a public computer name for each offer you want developers to discover. It can contain up to 60 characters.
4. Publish the individual offer and publish your profile. Both must be published for public visibility.

An offer identifies one computer and exact model revision with separate input/output rates. Several offers can belong to one profile. Offers can remain visible while busy or offline; publication does not prove available capacity. Review offers marked as needing review after a model revision changes.

The public response contains your chosen computer name and opaque offer ID, rather than account IDs, device IDs, or private computer names. Review your chosen public name before publishing.

## Unpublish and restore

```mermaid
flowchart LR
  accTitle: Public offer visibility
  accDescr: An offer is publicly visible only when its profile and individual offer are published. Hiding the profile retains individual offer flags, so republishing restores flagged offers. Publication is separate from Serving and Auto eligibility.
  Profile[Profile status] --> Check[Both published?]
  Offer[Offer status] --> Check
  Check -->|Yes| Visible[Visible offer]
  Check -->|No| Hidden[Hidden offer]
```

| Action                | Effect                                                                                                                             |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| Unpublish one offer   | Hides that offer and blocks new manual acceptance for it.                                                                          |
| Unpublish the profile | Hides the public profile, avatar, and all its offers; blocks new manual acceptance. Individual offer publication flags stay saved. |
| Republish the profile | Restores visibility for offers whose individual publication flags remain enabled.                                                  |
| Stop Serving          | Changes whether the computer can accept work; publication is a separate setting.                                                   |

Unpublishing does not stop Serving or remove otherwise eligible capacity from Auto. It does not change already accepted requests: they finish under their saved quotes and normal settlement rules. Price changes also leave accepted quotes unchanged.

> **Publication is separate from readiness**
> Publishing adds public discovery and manual choice. To make capacity available, keep the supported Core Node flow connected and Serving with the matching model and saved price. No administrator approval is required; eligibility checks still apply. Source support does not establish availability in a published Desktop package.

Developers can [choose your offer](https://router.optimai.network/docs/choosing-a-provider.md) per API request or for their current Playground conversation. See [Serving controls](https://router.optimai.network/docs/providers/sharing-controls.md) for stopping participation, and the [provider API reference](https://router.optimai.network/docs/api/providers.md) for account-authenticated profile and offer management.