Skip to main content
The app marketplace (/marketplace/apps) lists external applications built by third-party developers. They plug into Profy’s open API and serve you using your Profy identity and credits.

​
An app is not an expert

This is the easiest thing to conflate:
Clicking “Start” opens the application’s own homepage in a new tab — it does not open an embedded app inside Profy. If the app has no homepage URL on file, the button reports that it can’t navigate.There is no install step in the marketplace, and no “installed apps” list or revoke-authorization screen. Authorization happens when you sign in with your Profy account on that application’s site.

​
Browsing

Detail pages show the description, developer info, and usage counters (calls, users). Those counters increment asynchronously, so brief lag is normal.

​
How credits are charged

App billing is neither a purchase nor a subscription — it’s per-event, priced by the developer:
1

The developer defines events

Each app declares billable events (say “one translation” or “one export”), each with a fixed credit price.
2

You trigger an action in the app

The application calls Profy’s event reporting endpoint with the event name and an idempotency key.
3

Credits are deducted at that price

The price is deducted from your personal credit account. Re-reporting the same idempotency key does not double-charge — it replays the previous result.

​
Daily spending cap

Each app × user pair has its own daily credit cap, 500 credits per day by default. Past that, the app’s billing calls return daily_cap_exceeded (HTTP 429) with today’s spend and the limit in the response. The cap resets daily.
This is protective by design: a misbehaving third-party app can burn at most 500 credits, not your whole balance. The cap can be adjusted per user.

​
Common billing errors

These surface on the application’s side, usually as a generic “operation failed.” None of the first three indicate a problem with your account.

​
Publishing and review (creator view)

Apps publish through the same double-row review mechanism as experts:
  • Submitting requires an approved creator identity, otherwise 403
  • When a live app submits a new version, the old version stays live while the new content queues for review
  • Editing or resubmitting while a submission is pending returns 409
  • On approval the new content is written back and a version snapshot is created; on rejection a live app stays live while a first-time submission becomes rejected
  • Creators can withdraw a pending submission, or edit and resubmit from rejected

​
Failures and fixes

​
Developer view

Platform console

Manage apps, API keys, and call logs

Events API

Event reporting and per-event billing

Expert marketplace

AI experts you chat with inside Profy

Skill marketplace

Installable method documents