Skip to main content

​
What is the customer portal?

The customer portal is a hosted customer-facing view that lets a builder share approved usage, cost, invoice, trend, and budget visibility with an end-user. It is not dashboard access. End-users do not get project settings, API keys, rule configuration, pricing administration, or access to other customers.

​
Who can access it?

Only someone with a builder-issued portal link or valid portal access flow can open the portal. Portal links are scoped to one end-user/customer. Tokens are returned once and should be shared carefully. Links can expire, be revoked, or be single-use depending on the link type. If a link is invalid or expired, the end-user should ask the builder for a fresh link.

​
What end-users can see

The portal can show:
  • Current billing-period or month-to-date usage.
  • Total cost and event count.
  • Usage trend when enabled.
  • Model or step breakdown when enabled.
  • Invoice visibility when enabled.
  • Budget progress when enabled.
Visibility is builder-controlled. The portal should show only the usage and invoice information the builder chooses to share.

​
What builders control

Builders control:
  • Company name, logo, and primary color.
  • Allowed iframe origins.
  • Invoice visibility.
  • Usage trend visibility.
  • Budget progress visibility.
  • Portal links.
  • Link revocation.

​
Workflow

StepBuilder actionEnd-user result
Configure portalSet branding, visibility, and iframe origins.Portal reflects the builder-approved view.
Mint customer linkCreate a link for one end-user/customer.Link is scoped to that customer.
Share linkSend the link through the builder’s normal customer channel.End-user can open the portal.
Review usageKeep usage, pricing, and invoices current.End-user sees approved usage and invoice information.
Revoke or refreshRevoke old links or issue fresh links when needed.Access stays controlled by the builder.

​
What it never exposes

The portal does not expose:
  • Dashboard or admin access.
  • API keys.
  • Builder settings.
  • Rule configuration.
  • Prompts or completions.
  • Raw messages.
  • Raw tool arguments.
  • Private provider credentials.
  • Unrelated customers.
Portal visibility inherits the same privacy boundary as telemetry: send and share cost-shaped usage facts, not customer content.