## Monetization infrastructure that replaces your billing complexity.

AI products don't fail at billing because of payments. They fail because monetization logic gets scattered across the codebase.

Every team eventually builds their own version of usage tracking, feature gating, credit systems, pricing logic, entitlement rules, and billing edge cases. Over time, it becomes fragile, inconsistent, and expensive to maintain.

### Before · scattered logic

- drift
- usage tracking
- feature gating
- credit systems
- pricing logic
- entitlement rules
- billing edge cases

### After · single runtime

**Metrifox Runtime**  
- usage  
- entitlements  
- credits  
- pricing  
- enforcement

One source of truth for who can do what, how much it costs, and how it gets billed.

- sub-50ms checks
- idempotent ingestion
- deterministic pricing
- sandbox isolated

### Integrate in minutes. Same runtime, any stack.

**TypeScript, Python, REST API**

01 · Check  
Gate features before execution

02 · Track  
Record usage where value is created

03 · Credits  
Plans, top-ups, overrides, one runtime

**Language**  
- JavaScript
- Python
- Ruby
- PHP
- cURL

```javascript
const access = await metrifox.usages.checkAccess({
  customerKey: "cust_123",
  featureKey: "generate_response",
});

if (!access.can_access) {
  throw new Error("Limit reached");
}
```

Real-time. No cached permissions.

### The core loop

01  
Check

02  
Track

03  
Enforce

04  
Bill

### Runtime guarantees

- production-grade
- <50ms entitlement checks
- Idempotent usage ingestion
- Deterministic pricing evaluation
- Real-time enforcement
- Isolated sandbox → prod

### One integration. A permanent control layer.

Once connected, Metrifox becomes the runtime that governs how your product turns usage into revenue, across every customer, feature, and pricing model.

Monetization becomes a system, not a codebase.

## Used by teams who refuse to let billing slow them down.

"We went from 3-week pricing changes to 5-minute experiments. Our product team now runs A/B tests on pricing like they run A/B tests on features. ACV is up 22% in 6 months."  
**CTO, AI Inference Platform**  
**Outcome**  
+22% ACV

## Your stack, unchanged. Your billing, transformed.

Metrifox fits seamlessly into your existing workflow. No migration. No disruption. Just better billing.

### Payment
- Stripe
- Adyen
- Braintree

### Cloud
- AWS
- GCP
- Azure

### Data
- Snowflake
- BigQuery
- Redshift

### Observability
- Datadog
- New Relic
- Prometheus

### CRM
- Salesforce
- HubSpot
- Pipedrive

### Analytics
- Segment
- Amplitude
- Mixpanel

### Collaboration
- Slack
- Teams
- Discord

### Dev Tools
- GitHub
- GitLab
- Linear

### AI
- OpenAI
- Anthropic
- Cohere
- LangChain

### Workflow
- Zapier
- Make
- Pipedream

### Quick start

### Three steps. Live in minutes.

Drop in the SDK, send events, gate features. Your existing infra keeps working. Metrifox becomes the runtime that governs every priced surface.

01 Install SDK

```bash
npm install @metrifox/sdk
```

02 Send usage events

```typescript
await metrifox.ingest({
  customer: "cust_123",
  metric: "api_calls",
  value: 1
})
```

03 Check entitlements

```typescript
const access = await metrifox.check({
  customer: "cust_123",
  feature: "generate_response"
})
```

## Start protecting your margins today.

No engineering overhead. No migration headaches. Just a runtime that makes billing disappear.

## Questions, answered.

How fast can we go live with Metrifox?  
Most teams ship their first metered, gated, and billed feature in under a day. Drop in the SDK, send events, and gate access with one call. No data migration required.

#### Additional FAQs
- Does Metrifox replace Stripe?
- Can we change pricing without a deployment?
- How accurate is usage tracking?
- What stacks do you support?
- Is Metrifox secure and compliant?