Paid

What is Paid?

Paid is a billing and monetization platform built for companies selling AI agents, LLM features, or AI-powered services. It connects agent activity, delivery cost, customer pricing, value measurement, invoicing, and payment so operators can see whether each product and account is profitable.

Products represent billable AI offerings, while Signals record actions or outcomes such as messages, analyses, meetings, or resolved tickets. Teams can combine setup, platform, seat, activity, outcome, credit, and hybrid pricing. Paid also attributes costs from AI providers, creates itemized invoices, enforces balances and entitlements, and can show customers usage and delivered value through embeddable Blocks and value receipts.

How to Use Paid

1. Define each AI product, its customer, billable events, outcomes, entitlements, and cost drivers.
2. Choose a pricing model that matches delivered value and set clear units, tiers, credits, and overage rules.
3. Integrate an SDK, API, OpenTelemetry, or supported telemetry source to send Signals.
4. Connect provider costs and verify that every event is attributed to the correct product and customer.
5. Test checkout, credit grants, balance enforcement, invoice calculations, taxes, refunds, and failed payments in a sandbox.
6. Expose understandable usage and value records to customers before charging production accounts.
7. Reconcile invoices with source events, monitor margins, and require approval for pricing changes.

Core Features

• Flexible pricing: Supports setup fees, subscriptions, seats, usage, outcomes, credits, and hybrid models.
• Signal metering: Records agent actions, tool calls, tasks, and business outcomes.
• AI cost tracking: Attributes model and provider costs to products, customers, agents, and actions.
• Margin analytics: Compares revenue, delivery cost, and margin by account or product.
• Billing and invoicing: Aggregates usage into itemized invoices and payment workflows.
• Credits and entitlements: Grants allowances, tracks balances, and enforces access.
• Value receipts: Shows time saved, cost avoided, risk reduced, or revenue generated.
• Developer integrations: Provides Node.js, Python, Go, and Ruby SDKs plus OpenTelemetry support.

Use Cases

• Bill an AI support product per resolved ticket plus a monthly platform fee.
• Sell an AI sales agent using seats, credits, and outcome-based charges.
• Track model and voice-provider cost for each customer workflow.
• Test whether a new price covers variable inference and tool expenses.
• Give customers a live view of usage, remaining credits, and delivered value.
• Replace separate telemetry spreadsheets and manual invoice calculations.

Pricing

Paid currently offers a free starting path, but its public page does not display a complete numeric plan table. Commercial limits can depend on billing volume, cost-tracking volume, customer records, API requests, storage, and service tier. Confirm current allowances, transaction fees, payment processing, and support terms before production use.

Frequently Asked Questions

Does Paid decide what an AI outcome is worth?

No. The vendor must define auditable Signals, value formulas, and pricing. Avoid charging for outcomes that cannot be verified or attributed fairly.

Can it replace financial reconciliation?

No. Billing automation still needs accounting controls, tax review, refunds, dispute handling, event reconciliation, and separation of duties.

What data should be sent with a Signal?

Send only the metadata needed for metering, attribution, and value calculation. Avoid prompts, personal data, credentials, and sensitive outputs unless required and covered by approved controls.