Billing & Pricing

MCP Gateway Pro uses simple, usage-based pricing with four dimensions: requests, server hours, media storage, and RAG storage.

Pricing Overview

API Requests

$0.005

per request

Every API call to the gateway counts as one request, regardless of how many servers are aggregated.

Server Hours

$0.10

per server per hour (~$73/month)

Charged for each enabled server. Disabled servers don't incur charges.

Media Storage

$0.50

per GB per month

Files uploaded through the console Storage page. Metered hourly based on total storage used.

RAG Storage

$1.00

per GB per month

Documents in the RAG Engine knowledge base. Includes parsing, chunking, embedding, and vector indexing.

How Requests Are Counted

One request = one charge

Each API call to the gateway counts as one billable request, regardless of:

  • How many servers are enabled (aggregation is included)
  • Which MCP method is called (initialize, tools/list, tools/call, etc.)
  • The size of the request or response

Aggregation example

If you have 10 servers enabled and call tools/list:

  • The gateway queries all 10 upstream servers
  • Aggregates their tools into one response
  • You're charged for 1 request (not 10)

This is part of the value of the gateway — you pay for your usage, not for the fan-out work it does.

How Server Hours Are Counted

Only enabled servers are billed

Server hours are counted only for enabled servers. Each hour, we count how many of your servers have the "Enabled" toggle turned on.

  • Enabled server = billed $0.10/hour
  • Disabled server = not billed, not accessible

Disabled servers

When you disable a server:

  • It stops being billed for server hours
  • It becomes inaccessible through the gateway
  • It won't appear in tools/list responses
  • Requests targeting it will return an error

Use the Enabled toggle to temporarily pause servers you're not using without deleting them.

Cost example

With 3 servers enabled for a full month:

3 servers × 720 hours × $0.10 = $216/month

Disable servers you're not actively using to reduce costs.

Subscription Channels

AppXen supports two ways to subscribe. Pricing and dimensions are the same for both.

Stripe (Direct)

Subscribe at console.appxen.ai/subscribe with a credit card. Usage is metered hourly and billed monthly through Stripe.

  • View usage breakdown in Settings → Billing & Usage
  • Manage payment method and invoices via Manage Billing
  • Cancel or resubscribe anytime from the console

AWS Marketplace (Coming soon)

Subscribe through the AWS Marketplace listing. Usage is metered hourly and appears on your AWS bill.

  • Consolidated billing through your AWS account
  • Manage subscription in the AWS Marketplace Console
  • Use existing AWS payment methods and purchasing workflows
  • Eligible for AWS Enterprise Discount Programs (EDPs)

Viewing Your Usage

Stripe customers

  1. Go to Settings in the console
  2. The Billing & Usage section shows your current period: requests, server hours, storage, and estimated total
  3. Click Manage Billing for invoices and payment history

AWS Marketplace customers (Coming soon)

Usage is metered automatically and appears on your AWS bill. To view details:

  1. Go to AWS Billing Console
  2. Navigate to BillsAWS Marketplace
  3. Find "AppXen for MCP" to see metered usage by dimension

The AppXen console Settings page shows your active server count and storage, but billing details are on your AWS bill.

Tips for Managing Costs

Disable unused servers

Toggle off servers you're not actively using. You can re-enable them anytime without losing configuration.

Use aggregation

One aggregated request is cheaper than multiple individual requests. Let the gateway do the fan-out.

Monitor usage

Check the Analytics page regularly to understand your usage patterns and identify optimization opportunities.

Cache when possible

For tools that return relatively static data, consider caching responses in your application to reduce requests.

Frequently Asked Questions

Do I get charged for failed requests?

Yes, all requests that reach the gateway are counted, including errors. This is standard API billing practice.

What happens if I exceed my usage?

There are no hard limits — you're billed for actual usage. Review your usage in Settings to avoid surprises.

How often am I billed?

Usage is metered hourly and billed at the end of each billing period (typically monthly). Stripe customers receive a monthly invoice. AWS Marketplace customers see charges on their AWS bill.

Can I switch between Stripe and AWS Marketplace?

Not directly. Cancel your current subscription first, then subscribe through the other channel. Your account data (servers, API keys, storage) is preserved.

Can I set spending limits?

Not currently. Monitor your usage in the console and disable servers if needed to control costs. AWS Marketplace customers can use AWS Budgets to set alerts.