← Back to docs

My Profile payments and AI Credits

My Profile payments and AI Credits

/me is the canonical signed-in personal workspace. Membership, payment and AI Credit information is shown at the top of the account surface, with a direct link to /me/ai-usage for detailed AI balance and usage information.

The default Account view is intentionally lightweight. DNSBL statistics, the Fact Verify archive, family links, vBulletin linkage and Google-linked-account data are loaded only when their corresponding profile tab is opened. This keeps the account/payment/AI Credit surface responsive while preserving the same profile tools on demand. The Services tab keeps the existing profile service and pin-management surface available without making every normal /me request render it.

That AI usage shortcut is personal by design. When an administrator reviews another user's support account under /admin/support/users/{user}, the shared support card does not show the /me/ai-usage shortcut, because that route always belongs to the signed-in administrator rather than the selected target user.

Tools, not Ko-fi, is authoritative for the internal allocation of a verified payment. Ko-fi handles the external payment and supplies the payment, tier and product information used by Tools.

There are three supported funding modes:

  • Membership + AI Credits: a Ko-fi membership tier grants its configured fixed AI Credit amount and records the remainder as membership/project support. Paying more than the tier minimum remains additional support by default and does not silently scale the AI Credit grant.
  • AI Credits only: an explicitly mapped Ko-fi Shop direct_link_code grants the fixed configured AI Credit amount without creating membership support accounting.
  • Membership only: a membership tier with an AI Credit grant of zero records the payment as membership/project support only.

Ordinary Ko-fi donations and tips remain project support and do not become AI Credits.

Existing /users/profile and /profile URLs remain compatible. Legacy profile-view requests resolve to /me; existing profile-update POST requests remain accepted so older forms and clients do not break.

See Support Tools and AI usage, costing and prepaid credit for the underlying support-accounting and AI billing rules.