Product Requirements
API platform product scope
APIAny is a developer-facing AI API platform: one API key for chat, image, video, and audio models, prepaid credits, transparent usage logs, and admin-managed routing.
Collect payments
Users can buy credits through checkout, payment callbacks are idempotent, orders are auditable, and credits are granted through the ledger.
Serve model calls
Users can create API keys, call compatible model endpoints, spend credits on success, and receive refunds for failed async media work.
Reconcile usage
Users and operators can trace request ids, task ids, credit movements, channel attempts, upstream cost, and monthly finance summaries.
User console scope
- Dashboard shows balance, recent usage, failures, and shortcuts to create keys or add credits.
- API Keys support app name, purpose, budget, RPM, model scope, content logging, status, and last-used metadata.
- Model catalog shows active model ids, capabilities, pricing, parameters, and public status.
- Usage pages show request ids, API key, model, status, latency, credits, and error summaries.
- Credit ledger explains grants, purchases, API consumption, refunds, expirations, and admin adjustments.
- Playground remains optional; production API and docs are the first-class developer experience.
Admin scope
- Users, balances, roles, orders, subscriptions, and manual credit adjustments stay auditable.
- API Models define public ids, request type, pricing, capability labels, parameters, fallback policy, and channel groups.
- API Channels define provider, base URL, secret reference, health, priority, weight, and supported request types.
- API Costs track upstream cost rules independently from public credit pricing for gross margin reporting.
- Internal jobs process pending media, stale tasks, callbacks, channel health, and scheduled maintenance.
- Finance summaries combine credit revenue, upstream cost, gross margin, and monthly rollups.
Launch constraints
Business logic must run in the Next.js Node runtime and stay inside ShipAny module boundaries.
Stripe is the primary production payment path; additional providers stay optional framework capabilities.
Request and response bodies are retained for the configured API retention window, while finance summaries and ledgers remain long term.
New models and same-protocol channels should be added through configuration or seeds; new code is reserved for genuinely new provider protocols.