What is MNNR and how does it help with AI agent billing?

MNNR is payments infrastructure for the machine economy, specifically designed for AI agent billing. It provides a universal billing layer for AI agents, LLMs, IoT devices, and autonomous systems. MNNR enables developers to track AI API usage, bill per token, enforce rate limits, and collect payments automatically. Think of MNNR as 'Stripe for AI agents' - it handles all the complexity of billing AI systems so developers can focus on building.

How does MNNR handle per-token billing for LLMs like GPT and Claude?

MNNR provides real-time per-token billing for any LLM including GPT-4, Claude, Llama, and custom models. Simply call mnnr.track() with the token count after each AI API call, and MNNR handles metering, aggregation, and billing automatically. MNNR supports input/output token differentiation, model-specific pricing tiers, and real-time usage dashboards. Integration takes under 5 minutes with our SDK.

Can MNNR bill autonomous AI agents that make their own API calls?

Yes, MNNR is specifically designed for autonomous AI agent billing. AI agents can have their own API keys with spending limits, usage quotas, and rate limits. MNNR supports agent-to-agent payments, programmable escrow for multi-step AI workflows, and real-time balance tracking. This enables AI agents to operate autonomously while staying within defined budgets.

How is MNNR different from Stripe for AI billing?

While Stripe was built for human-initiated transactions, MNNR is designed specifically for AI and machine-to-machine commerce. Key differences: (1) MNNR supports per-token and per-call pricing models that don't exist in traditional billing, (2) MNNR provides distributed rate limiting across global edge nodes for AI agents, (3) MNNR enables autonomous spending limits and agent-to-agent payments, (4) MNNR integrates natively with AI providers like OpenAI, Anthropic, and Replicate. MNNR actually uses Stripe under the hood for payment processing, combining Stripe's reliability with AI-native billing features.

What AI models and providers does MNNR support?

MNNR supports billing for any AI model or provider including: OpenAI (GPT-4, GPT-3.5, DALL-E, Whisper), Anthropic (Claude 3, Claude 2), Meta (Llama 2, Llama 3), Google (Gemini, PaLM), Hugging Face models, Replicate hosted models, AWS Bedrock, Azure OpenAI, and custom self-hosted models. MNNR's universal SDK works with any AI provider - just track the usage metrics you care about (tokens, API calls, compute time, etc.).

Does MNNR support cryptocurrency payments for AI agents?

Yes, MNNR is Web3 native with first-class support for crypto payments. AI agents can pay and receive payments in USDC, ETH, SOL, and other cryptocurrencies. MNNR supports smart contract integration for programmable payments, streaming payments for real-time AI usage, and decentralized identity verification. This enables truly autonomous AI agents that can transact without human intervention.

How much does MNNR cost for AI agent billing?

MNNR offers a free tier with 10,000 API calls per month - enough to test AI agent billing without any cost. The Pro plan at $49/month includes 1M API calls, advanced analytics, custom rate limits, and Stripe integration. Enterprise plans offer unlimited API calls with dedicated infrastructure and custom SLAs. During the public beta, there are zero platform fees on transactions - you only pay Stripe's standard processing fees.

How fast can I integrate MNNR for AI billing?

Most developers integrate MNNR in under 5 minutes. Install the SDK (npm install @mnnr/sdk or pip install mnnr), initialize with your API key, and add a single mnnr.track() call after each AI API request. MNNR provides SDKs for JavaScript/TypeScript, Python, Go, and Rust. The SDK handles batching, retries, and offline support automatically.

← Back to Documentation

🚀 Deployment

Production Deployment

Deploy your agent infrastructure to production with Vercel, Supabase, and enterprise-grade monitoring.

Infrastructure Stack

▲

Vercel

Edge Runtime

⚡

Supabase

PostgreSQL

🔴

Redis

Rate Limiting

💳

Stripe

Payments

⚙️

Step 1

Environment Setup

Database URL (Supabase PostgreSQL)
Stripe API keys (publishable + secret)
Redis connection string for rate limiting
Sentry DSN for error monitoring
MNNR API keys for agent services

Configuration

# .env.production
DATABASE_URL="postgresql://..."
STRIPE_SECRET_KEY="sk_test_..."
STRIPE_PUBLISHABLE_KEY="pk_test_..."
REDIS_URL="redis://..."
SENTRY_DSN="https://..."
MNNR_API_KEY="mnnr_test_..."

🗄️

Step 2

Database Migration

Create Supabase project
Run schema migrations
Configure Row Level Security (RLS)
Set up agent_identities table
Create transaction indexes

Configuration

# Run migrations
npx prisma migrate deploy

# Seed agent economy tables
npx prisma db seed

# Verify RLS policies
supabase db diff --linked

🚀

Step 3

Vercel Deployment

Connect GitHub repository
Configure build settings (Next.js)
Set environment variables
Configure custom domain (mnnr.app)
Enable Edge Functions for APIs

Configuration

# vercel.json
{
  "framework": "nextjs",
  "regions": ["iad1", "sfo1", "fra1"],
  "functions": {
    "api/**/*.ts": {
      "maxDuration": 30
    }
  }
}

📊

Step 4

Monitoring Setup

Sentry error monitoring
Performance monitoring (Web Vitals)
Database health checks
Agent transaction monitoring
Alert configuration (PagerDuty/Slack)

Configuration

// sentry.config.ts
Sentry.init({
  dsn: process.env.SENTRY_DSN,
  tracesSampleRate: 0.1,
  profilesSampleRate: 0.1,
  integrations: [
    new Sentry.BrowserTracing(),
  ],
});

🔐

Step 5

Security Hardening

Enable Redis rate limiting
Configure CORS policies
Set up SSL certificates (auto via Vercel)
Review API access controls
Enable audit logging

Configuration

// Rate limiting config
const rateLimiter = new RateLimiter({
  redis: redisClient,
  max: 100,
  windowMs: 60 * 1000,
  keyPrefix: 'rl:',
});

Pre-Deployment Checklist

Setup

✓

Environment variables configured

✓

Database schema deployed

✓

Stripe webhooks configured

✓

Domain SSL certificate active

Operations

✓

Monitoring tools configured

✓

Backup strategy in place

✓

Load testing completed

✓

Rollback plan documented

Post-Deployment Verification

🏥

Health Check

GET /api/health

⚡

Performance

Run Lighthouse audit

🔐

Security

Verify SSL & headers

Need Deployment Help?

Our DevOps team can assist with custom deployment configurations.

📧 Contact DevOps