OOMPF

Models and providers

OOMPF presents models friendly-first: a readable name, then the exact selector, then a verified link where one is curated.

Kimi K2.7 Code
opencode-go/kimi-k2.7-code
Open provider page ↗

The exact selector stays visible as secondary, copyable reference text so nothing is hidden behind an abstraction.

Aliases are not models

Values beginning with @ — such as @tiny — are OMP aliases: runtime role shortcuts that resolve to a concrete model when omp runs. OOMPF excludes them from the concrete Models list. When an alias appears in a behavior mapping, OOMPF labels it as a role (for example, tiny role) and preserves the exact @tiny selector as supporting detail. Aliases are never classified as models or providers, and OOMPF does not repeat a profile-wide alias inventory on every profile page.

OMP catalog data supplies provider IDs, display labels, bundled model IDs, defaults, and capabilities. It does not reliably supply canonical public documentation URLs, and provider API/base URLs are not public documentation.

OOMPF therefore maintains a small, explicit, curated registry keyed by provider and optional model pattern. Entries contain verified public destinations. When an identifier is not in the registry it stays valid data with no link — OOMPF never fabricates a URL.

Machine-readable mappings

The curated registry is available to agents:

  • GET /api/v1/mappings/providers — provider identities and canonical links.
  • GET /api/v1/mappings/models/:provider — curated model patterns, friendly names, and canonical links for one provider.

Response shapes are published as JSON Schema at /schemas/profile-mappings.json. Unknown providers return a not_found error envelope; curated models with no verified destination carry url: null.