How it works · Platform

Tier-gated model catalogue

Plans unlock text and image models from Basic through Elite so each tool runs on models your tier allows.

Platform

Overview

CasperWasp routes AI work through a catalogue of text and image models delivered via providers. You do not wire API keys for everyday marketplace use — you pick a plan tier, see which models unlock, and run tools in Document Studio or Design Studio against that catalogue.

Tier-gating keeps commercial intent clear. Basic plans cover capable defaults for everyday drafting and design. Higher tiers open stronger models for harder writing, richer analysis, or higher-end image generation. The product surfaces stay the same; the router’s allowed set expands.

This pairs with shared usage. Tokens consumed still meter successful calls; failed calls use zero tokens; editing stays free. The catalogue answers “which models can we call,” while the audit trail answers “which models did we call and how many tokens they used.” There is no pre-run cost estimate and no token calculator layered on top.

For buyers comparing the marketplace to stitched tools, the catalogue is the honesty layer: see /ai/models for what each tier unlocks, then use pricing to choose capacity. Writers and designers keep one organisation and one workflow even as model power scales.

In depth

Understanding Tier-gated model catalogue

How the feature works in practice inside the CasperWasp marketplace — and how it connects to the rest of your work.

How tier unlocks show up in daily work

When you run an AI writing tool, PDF intelligence feature, or logo generation flow, the platform selects from models your plan allows. If a tool requires a higher minimum tier, upgrade paths are explicit rather than mysterious failures.

Teams often mix light and heavy work. Grammar and small rewrites may be fine on lower tiers; long strategic narratives or premium image exploration may justify Elite access. Shared usage means those heavier runs still draw from the same pool — they simply use unlocked catalogue entries.

Because editing is free, humans can always finish the job even when they choose not to spend tokens on another generation. Models assist; they do not become a gate on exporting a deliverable.

Admins should teach “right model for the job.” Unlocking a powerful model does not mean every comment reply needs it. The audit trail will reveal whether the team treats Elite as a default or as a scalpel.

Catalogue, providers, and transparency

The live catalogue on /ai/models is the reference for what is available. It may include well-known text and image model families delivered through providers. Exact listings change as the marketplace evolves — treat the page as source of truth.

Prompts for AI tools may reach third-party model providers. That is part of how modern AI products work. Read the security page for posture; CasperWasp does not claim SOC 2, ISO 27001, or HIPAA attestation as of the company facts reference.

Transparency also means not inventing fake precision. The catalogue does not pretend to estimate tokens before a run. Afterward, the audit trail records tokens consumed for successful calls.

Design and document tools can expose different model needs. Image generation and long-context analysis are not the same workload as a short tone shift. Tier gating acknowledges that diversity without splitting you into multiple vendors.

Choosing a tier without overbuying

Start from workflows, not from brand names alone. If your month is mostly proposal rewriting and simple stamps, a mid tier may suffice. If you constantly need top-end image models and deep document reasoning, price the higher tier honestly.

Use packs when you are allowance-constrained but model-unlocked. Use upgrades when the catalogue blocks the model quality you need. Those are different problems; the platform gives both levers to owners and admins.

Editors should not silently work around tier limits by pasting into consumer AI chat tools — that breaks organisation libraries, audit trails, and shared usage. If the catalogue is insufficient, escalate to an admin for a tier decision.

Revisit tier choice after a real month of audit data. Patterns beat speculation. That is why CasperWasp skips token calculators that invent comfort without your workload.

How it works

Step by step

A practical walkthrough of tier-gated model catalogue in the CasperWasp marketplace.

  1. 01

    Open the AI models catalogue

    Visit /ai/models to see text and image models and how they map to plan tiers.

  2. 02

    Map your critical workflows

    List must-have jobs: contract drafting, PDF chat, logo generation, brochure imagery, and so on.

  3. 03

    Pick the minimum tier that unlocks those models

    Choose capacity on pricing with catalogue requirements in mind — not seats alone.

  4. 04

    Run tools inside the studios

    Document Studio and Design Studio call allowed models through the marketplace router.

  5. 05

    Inspect tokens consumed afterward

    Use the audit trail to see which models ran and how many tokens successful calls used.

  6. 06

    Coach for right-sized model use

    Keep powerful models for hard tasks; use lighter tools for small edits when enough.

  7. 07

    Upgrade when quality is blocked by tier

    Owners/admins raise the plan if required models sit above your current unlock.

  8. 08

    Add token packs when allowance — not catalogue — is the constraint

    Keep the same models; extend capacity for busy months without changing products.

When

When to use this

  • Selecting a plan based on model access, not guesswork
  • Explaining to finance why a higher tier is required for image or writing quality
  • Onboarding editors so they know which tools their tier supports
  • Comparing CasperWasp to bringing-your-own multi-vendor API stack
  • Diagnosing a tool that requires a higher minimum tier
  • Revisiting tier choice after a month of audit trail evidence
  • Aligning design and document AI quality under one subscription
  • Setting norms so Elite models are not the default for trivial edits
Who

Who it is for

  • Owners choosing marketplace plan tiers
  • Admins translating catalogue needs into upgrades or packs
  • Editors who want clarity on which AI tools they can run
  • Design leads who care about image model quality
  • Writing leads who care about text model strength
  • Finance partners evaluating why model access differs by plan
  • Technical evaluators comparing provider-routed catalogues
Examples

Real workflows

Concrete jobs teams run with this feature — not abstract capability lists.

A design pod upgrades after the catalogue shows their preferred image models unlock at a higher tier; shared usage continues in the same org.
A legal ops team stays on a mid tier for everyday rewrite tools but escalates selectively when deep PDF analysis needs stronger models.
An agency explains to a client that deliverable quality tracks plan tier model access — not a separate design AI subscription.
An admin denies “we need more tokens” when the real issue is a blocked model; they upgrade tier instead of buying packs blindly.
A founder starts Basic for drafts, reviews /ai/models, then moves up before a brand launch that needs better logo generation.
A PMM uses lighter models for tone tweaks and reserves higher-tier models for first-draft strategy narratives.
Included

What you get

  • A live catalogue of text and image models by tier
  • Tool-level minimum tier clarity
  • Upgrade paths without changing studios or products
  • Provider-routed access without self-managed key sprawl for everyday use
  • Alignment with shared usage metering in tokens
  • Audit trail visibility into which models actually ran
  • Failed calls at zero tokens even when models error
  • Free editing regardless of which model last ran
  • No pre-run cost estimate theatre
  • No token calculator replacing real workload data
  • One marketplace for documents + design model access
  • Clear separation between allowance packs and model unlock upgrades
Tips

Do it well

Check /ai/models before you argue about plan value.
Upgrade for model access; pack for allowance overflow.
Match model strength to task difficulty.
Use audit trails to validate whether Elite is being overused.
Keep editors inside CasperWasp instead of shadow AI tools.
Re-read the catalogue when new tools launch.
Pair catalogue choice with organisation role gates for spending.
Remember editing can finish the job without another generation.
Pitfalls

Common mistakes to avoid

The shortcuts that waste time or produce weak deliverables.

  • Buying packs when the real blocker is tier-locked models
  • Upgrading tiers when the real issue is raw allowance
  • Using the strongest model for every tiny rewrite
  • Ignoring the live /ai/models page and relying on memory
  • Expecting pre-run token estimates per model call
  • Leaving the marketplace to use consumer AI chats that break auditability
  • Assuming model unlocks change the fact that editing is free
FAQ

Common questions

View AI models

Part of the CasperWasp marketplace — documents and design under one subscription.

Try the CasperWasp marketplace

Create an account and use Document Studio and Design Studio from one subscription — write documents, analyse PDFs, and generate brand assets with transparent AI usage.

Plans from ₹300/month · Cancel anytime