Partner Program | OpenModels Documentation

Use the Partner workspace to create your own OpenModels-powered marketplace, select model routes, set markup, publish a public storefront, and track usage attributed to your Partner ID.

Setup checklist

The Partner overview shows the setup steps and the current workspace summary.

Partner overview with setup checklist, Partner ID, referred users, usage volume, and estimated payout

Complete these steps before publishing:

Configure the storefront.
Add models and select provider routes.
Choose a partner plan.
Configure SEO.
Preview the public marketplace.
Publish when the marketplace is ready.

Configure the storefront

Open Storefront and set the fields that appear on the public marketplace page.

Storefront settings with Partner ID highlighted

Key fields:

Field	Purpose
Partner ID	Used in public URLs and partner attribution. Copy this value when you need to share or verify attribution.
Marketplace name	The display name shown on your marketplace.
Short description	The public description for your marketplace landing page.
Contact channels	Optional public contact methods. Empty fields are hidden.

Add models

Open Models, click Add model, choose the model route, and set the markup for your marketplace price.

Distributor models table with Add model button highlighted

The table shows the upstream route, base input and output prices, markup, final marketplace prices, and status. Keep models enabled only when the selected provider route is ready for users.

Choose a plan

Open Plan and choose the plan that matches the number of models and controls you need.

Partner plan page showing Launch, Growth, and Scale plans

The Launch plan is the smallest publishing plan. Growth and Scale add higher model limits and more marketplace controls.

Configure SEO

Open SEO and set the public page title, slug, and meta description.

SEO settings with page title, slug, meta description, and Google preview

The slug becomes the public marketplace URL path. Review the preview before saving changes so the search result title and description match the marketplace you intend to publish.

Preview and publish

Open Preview to review the storefront with the live Partner profile and published model routes.

Marketplace preview with Open preview and Publish controls

Use Open preview to inspect the public storefront in a separate tab. Use Publish only after the storefront, models, plan, and SEO settings are ready.

Track usage

Open Usage to see requests, commission, Partner ID attribution, and per-request usage rows.

Distributor usage page with request, commission, Partner ID, and usage rows

Use this page to confirm that traffic is attributed to the expected Partner ID and that commission values are being recorded for model usage.

Public Partner API

Use the public Partner API when you want to build your own marketplace page, pricing page, or plan page from the same Partner profile and model data that powers the hosted storefront.

Public cURL

curl "https://openmodels.market/api/v1/partners/public/$PARTNER_ID"

Replace $PARTNER_ID with the Partner ID from your Storefront settings.

Owner cURL

Use full=true only when the logged-in Partner owner needs the full profile and model payload:

curl "https://openmodels.market/api/v1/partners/public/$PARTNER_ID?full=true" \
  -H "Authorization: Bearer $OPENMODELS_ACCESS_TOKEN"

OPENMODELS_ACCESS_TOKEN is the OpenModels application access token for the logged-in account. Do not use a Key Market API key here.

Query parameters

Parameter	Required	Description
`full`	No	Use `true` to request the owner-only full payload. The endpoint returns the basic public payload unless the `Authorization` token belongs to the owner of this Partner ID.

Authorization behavior

The endpoint is public by default. Requests with no header, an invalid token, or a token for a different account return the same basic public payload.

Only the Partner owner can use Authorization: Bearer $OPENMODELS_ACCESS_TOKEN with full=true to read owner-only fields such as account ID, wholesale markup, upstream model, supply price, markup, and owner pricing-tier fields.

Response shape

The public endpoint returns the standard OpenModels application envelope:

{
  "code": 0,
  "message": "",
  "data": {
    "profile": {
      "partnerId": "partner-example",
      "slug": "partner-example",
      "displayName": "Example Partner Marketplace",
      "description": "A public marketplace description.",
      "supportEmail": "support@example.com",
      "telegram": "@example",
      "discord": "example",
      "whatsapp": "",
      "wechat": "",
      "seoTitle": "Example Partner Marketplace",
      "seoDescription": "Search result description.",
      "status": "published"
    },
    "models": [
      {
        "partnerId": "partner-example",
        "publicModel": "deepseek-v4-flash",
        "provider": "Neolink",
        "providerKind": "third_party",
        "currency": "USD",
        "billingType": "usage_flat",
        "billingUnit": "token",
        "actualPromptMicroUsd": 129917,
        "actualCompletionMicroUsd": 259832,
        "contextWindowTokens": 1000000,
        "enabled": true
      }
    ]
  }
}

Field guide

Field	Description
`data.profile`	Public Partner profile used by the hosted storefront.
`profile.partnerId`	Attribution ID for the marketplace.
`profile.slug`	Public marketplace URL path.
`profile.displayName`	Marketplace display name.
`profile.description`	Public marketplace description.
`profile.supportEmail`, `telegram`, `discord`, `whatsapp`, `wechat`	Optional public contact channels. Empty values can be hidden in your custom page.
`profile.seoTitle`, `seoDescription`	SEO metadata configured in the Partner workspace.
`profile.status`	Publish state for the Partner marketplace.
`data.models`	Published model list for the Partner marketplace.
`models[].publicModel`	Model ID to show to users and pass to OpenModels-compatible requests.
`models[].provider`	Selected provider route.
`models[].billingType`, `billingUnit`	Pricing mode and unit, such as token, second, or image.
`models[].actualPromptMicroUsd`, `actualCompletionMicroUsd`	Final marketplace prices in micro-USD for the billing unit. Divide by `1,000,000` to display USD values.
`models[].pricingTiers`	Optional tiered or multimodal final price details. Use this when a model has resolution, input mode, or threshold-specific pricing.
`models[].enabled`	Whether the model should be shown as available.
Owner-only fields	Returned only when `full=true` and the bearer token belongs to this Partner owner. Examples include `profile.accountId`, `profile.wholesaleMarkupPercent`, `models[].upstreamModel`, `models[].partnerPromptMicroUsd`, `models[].partnerCompletionMicroUsd`, `models[].markupPercent`, and owner-only `pricingTiers` supply fields.

Building your own page

Use profile for the page header, SEO metadata, contact links, and marketplace status. Use models for model cards, pricing tables, and route metadata. Filter out models where enabled is not true, and show pricingTiers when present so image, video, and tiered token models keep their public pricing details.

Partner FAQ

What is the Partner Program?

The Partner Program lets you create a public marketplace powered by OpenModels. You choose which models to list, set marketplace pricing through markup, publish a storefront, and track usage attributed to your Partner ID.

Is this the same as becoming a Provider?

No. Partner Program is for running a marketplace storefront on top of existing OpenModels routes. Provider onboarding is for listing your own upstream models on OpenModels.

If you want to package existing OpenModels routes in your own marketplace, use Partner Program. If you operate model infrastructure or an upstream gateway and want OpenModels to route traffic to it, use Provider Integration.

What is the Partner ID used for?

The Partner ID is the attribution identifier for your marketplace. It is used in public URLs and partner-linked usage tracking, so copy it exactly when you need to share or verify marketplace attribution.

Do I need to add models before publishing?

Yes. A marketplace should have enabled models before users can browse and request API access through the storefront. Add models from Models, select provider routes, set markup, and confirm the final prices before publishing.

How is marketplace pricing set?

Pricing is configured per listed model in the Partner workspace. For public pages, show the final marketplace price fields returned by the Partner API.

Do I need a partner plan?

Yes. The setup checklist includes Plan before publishing. Choose the plan that matches the model limit and marketplace controls you need.

Can I preview before publishing?

Yes. Use Preview to review the storefront with the live Partner profile and model routes. Use Open preview for a separate public preview tab, then publish only after the page, model list, pricing, and SEO settings are ready.

Where do I track partner usage?

Use Usage to review attributed requests, model, provider, token usage, commission rate, and commission amount. This is the best place to confirm whether traffic is tied to the expected Partner ID.

Where are payouts managed?

Use Payouts in the Partner workspace for payout-related operations. The overview and usage pages show estimated payout and commission signals, but payout management belongs in the dedicated Payouts page.

Can I change SEO after publishing?

Yes. You can update the page title, slug, and meta description from SEO. Re-check the preview after changing SEO because the slug controls the public marketplace URL path.