Glossary
The terms used throughout the PortModels docs, defined once.
App#
A product published in the PortModels gallery. Apps are built by third-party developers and reviewed before they go live.
PortModel#
A developer-defined AI application layer: instructions, tools, memory, model routing, safety rules, and monetization settings combined into one named, deployable AI product. "App" and "PortModel" are used interchangeably in these docs.
Credit#
The platform's unit of account. Users buy credits; apps spend them per run. See Credits.
Connect#
The OAuth 2.0 flow an app uses to get permission to act on a user's account. See Connect overview.
Scope#
A single named permission on a Connect token, such as models.run or
kv.write. See Scopes.
Access token#
The credential a connected app uses to call the API on a user's behalf.
Prefixed pmc_. Each login gets its own token, so several devices can stay
connected at once. Tokens currently have no expiry timer; disconnecting the app
revokes every token for that user, while connecting again leaves existing
active tokens alone.
API key#
A long-lived credential you use to call the API as yourself, prefixed pm_.
Shown once at creation and stored only as a hash.
Publisher namespace#
The unique handle that prefixes every app you publish, making your client ID
publisher/app-name.
Markup#
The margin a developer adds on top of provider cost. The user pays cost plus markup; the markup becomes developer earnings.
App Data Layer#
Per-user storage scoped to a single app: a key/value store and a file folder. See App data.
Call log#
The record PortModels writes for each metered request — model, usage, cost, and outcome. Visible to users on their balance page and to developers in the dashboard.