Owner: Engineering Team | Last Updated: 2026-01-30 | Status: Planned
Draft: This section is a placeholder. Content will be added when the Developer Portal is built.
The WWAI Developer Portal is a planned application that will serve as an API marketplace for the platform's proprietary AI models. It will provide external developers and enterprise customers with programmatic access to the WWAI Humanizer and Detector APIs, complete with API key management, usage dashboards, billing, and comprehensive documentation. The Dev Portal is envisioned as a separate application with its own frontend and backend, while leveraging the existing AI model infrastructure.
Repository: Not yet created
Status: Planned / Pre-development
Target Launch: To be determined
The Developer Portal will transform WWAI from a consumer-facing SaaS product into a platform with a B2B/developer-facing API offering. Key strategic goals:
| Feature | Description | Priority |
|---|---|---|
| API Key Management | Generate, rotate, and revoke API keys | High |
| Usage Dashboard | Real-time and historical API usage analytics | High |
| Billing & Invoicing | Usage-based billing with Stripe integration | High |
| Interactive Documentation | OpenAPI/Swagger docs with "Try It" functionality | High |
| Rate Limiting Dashboard | View current limits and request throttling status | Medium |
| SDKs & Code Examples | Client libraries for Python, JavaScript, Go, etc. | Medium |
| Webhook Management | Configure webhooks for async processing and events | Medium |
| Team Management | Multi-user access with role-based permissions | Low |
| API Versioning | Version management for API endpoints | Low |
| Sandbox Environment | Test environment with mock data for development | Low |
Draft: Feature prioritization and detailed specifications will be defined during the planning phase.
Developer / Enterprise Customer
|
v
Dev Portal Frontend (React / Next.js - TBD)
|-- Dashboard (usage, billing, keys)
|-- Documentation (interactive API docs)
|-- Account Management
|
v
Dev Portal Backend (Framework TBD)
|-- API Key Generation & Validation
|-- Usage Metering & Rate Limiting
|-- Billing Integration (Stripe)
|-- Developer Account Management
|
+---> WWAI AI Models
| |-- Humanizer API
| |-- Detector API
|
+---> Shared Infrastructure
|-- PostgreSQL (developer accounts, API keys, usage logs)
|-- Redis (rate limiting, caching)
|-- AWS (hosting, monitoring)
The Dev Portal is designed as a separate application to allow:
Public API (for developers)
POST /v1/humanize - Humanize text
POST /v1/detect - Detect AI content
GET /v1/usage - Usage statistics
GET /v1/status - API health and status
Management API (for Dev Portal frontend)
POST /api/keys/ - Create API key
GET /api/keys/ - List API keys
DELETE /api/keys/{id}/ - Revoke API key
GET /api/usage/ - Usage dashboard data
GET /api/billing/ - Billing information
POST /api/billing/checkout/ - Upgrade plan
Draft: This architecture is a proposed design. Final architecture decisions will be made during the technical planning phase.
| Option | Pros | Cons |
|---|---|---|
| Next.js | Consistent with web app, SSR, team expertise | May share too much with consumer app |
| Docusaurus | Built for documentation sites, MDX support | Limited dashboard capabilities |
| Custom React + Vite | Lightweight, fast builds | No SSR out of the box |
| Option | Pros | Cons |
|---|---|---|
| Django (extend existing) | Shared models, team expertise | Coupling with consumer backend |
| FastAPI | Modern Python, async, auto-docs | Separate codebase, new patterns |
| Dedicated Django service | Familiar stack, independent scaling | Code duplication |
| Option | Pros | Cons |
|---|---|---|
| Swagger/OpenAPI | Industry standard, auto-generation | Limited customization |
| Redoc | Clean UI, OpenAPI-based | Read-only experience |
| Custom (MDX-based) | Full control, rich content | More development effort |
Draft: Technology decisions will be finalized during the technical design phase.
| System | Integration | Purpose |
|---|---|---|
| WWAI AI Models | Direct model invocation | Humanization and detection processing |
| Stripe | Payment API | Developer billing and invoicing |
| WWAI Main Backend | Shared database or API | User account linking (if applicable) |
| AWS | Infrastructure | Hosting, monitoring, logging |
| GitHub | CI/CD | Build and deployment pipelines |
Draft: This roadmap is a preliminary outline. Detailed planning will occur when the project is greenlit.
| Date | Author | Change |
|---|---|---|
| 2026-01-30 | Admin | Initial creation (planning phase) |
Up: Home