Skip to main content
TWTeamWicked AI

Code with AI —one gateway

OpenAI-compatible. Multi-provider. Managed through Blesta.

TeamWicked AI routes customer API keys to coding models like Kimi, GLM, MiMo, DeepSeek V4 Flash, and fast workflow models through one stable endpoint.

One OpenAI-compatible endpoint for coding models, usage tracking, and Blesta-managed access.

Simple gateway plans

AI 150 Daily

All public models with a 150-request daily allowance

₩45,000/27 days
  • OpenAI-compatible endpoint
  • sk- API key management
  • 150 requests per UTC day
  • Other models: 20 RPM · 3 standard / 5 burst concurrency
  • Kimi K3, MiMo, and DeepSeek V4 Flash aliases
  • Kimi K3: 55 calls per rolling 30 minutes
Order access
Most popular

AI Unlimited Kimi K3

Unlimited daily requests for Kimi K3, MiMo, and DeepSeek workflows

₩90,000/27 daysBlesta-managed renewal
  • Unlimited daily request allowance
  • Kimi K3, MiMo, and DeepSeek V4 Flash aliases
  • Kimi K3: 55 calls per rolling 30 minutes
  • Streaming usage capture
  • Model-level request totals
  • Input/output/cache token reports
  • Six-key Kimi K3 priority failover
Order access

Scale

For high-volume resellers and apps

Custom
  • Everything in Builder
  • Custom quota rules
  • Provider expansion planning
  • Dedicated gateway support
  • Usage export assistance
  • SLA options
Contact sales

Blesta remains the source of truth for purchases, renewals, and service status.

Answers for API customers

Is the API OpenAI-compatible?

Yes. Customers use https://api.teamwicked.me as the base URL and call /v1/chat/completions with a Bearer sk- key.

Where are API keys managed?

Keys are created, renamed, and disabled from the Blesta client area. Plaintext keys are shown once and only hashes are stored.

Which models are available?

The current public aliases are teamwicked-kimi-k3, teamwicked-deepseek-v4-flash, and Xiaomi MiMo aliases such as teamwicked-mimo, teamwicked-mimo-v2.5, and teamwicked-mimo-pro.

Can customers see usage?

Yes. The gateway stores request counts and input, output, and cached token usage per Blesta service.

Are upstream provider keys exposed?

No. WE64, MiMo, and DeepSeek credentials stay server-side on TeamWicked infrastructure and customer keys only authenticate against our gateway.

Start selling AI access

Order through Blesta, create an sk- key, and point your OpenAI client at TeamWicked.

API keys are tied to active Blesta services and can be disabled at any time from the client area.