Customer access and billing for APIs
Add API keys, rate limits and billing to your API
MicroAuth gives you a branded customer portal and an SDK for your backend. Customers sign up, create keys and pay while your API handles access and usage without sending traffic through MicroAuth.
No gateway. No proxy. No revenue share.
Your customers
call your API with their key
Your API
auth, limits & metering in‑process
MicroAuth SDK inside
MicroAuth
portal · billing · control plane
How it works
Go from API to paid product in three steps
Launch a customer portal
Add your brand, choose a domain and set your prices. Customers get a portal where they can sign up, create API keys, view usage and pay.
Your API key
map_9f3k…tqQ1
Plan
Starter · $9/mo
Credits
$24.10
Protect and meter your API
Add the SDK to authenticate keys, enforce customer limits and record usage inside your service. Cached data keeps MicroAuth out of your request path.
FastAPI has a ready-made SDK. Other stacks can use the same three HTTP endpoints directly.
from fastapi import FastAPI, Security
from microauth_fastapi import MicroAuth, Customer
app = FastAPI()
auth = MicroAuth(app) # the whole integration
@app.get("/forecast")
async def forecast(customer: Customer = Security(auth)):
return {"hello": customer.id}The Express SDK is on the way. Until then, any language can integrate today through the same three-endpoint HTTP contract every SDK is built on.
Read the integration guideThe Go SDK is on the way. Until then, any language can integrate today through the same three-endpoint HTTP contract every SDK is built on.
Read the integration guide- GET
/sdk/v1/snapshotCache your customers, keys and limits locally - GET
/sdk/v1/keys/verifyResolve a key created seconds ago - POST
/sdk/v1/usageReport usage in idempotent batches
Three endpoints are the entire integration surface. Build the same contract in Node, Go, Rails or anything else, with thecustom integration guide.
Let customers sign up and pay
Customers manage their own keys, credits and subscriptions. You track usage, balances and revenue without building the account and billing system yourself.
Usage this month
live
128,407 requests
On every request
Request checks stay inside your API
- 1
Key checked
The SDK checks a local cache. No call to MicroAuth.
- 2
Limits enforced
Rate limits, quotas and balance rules run in your process.
- 3
Response returned
Your handler runs without a round trip to MicroAuth.
- 4
Usage reported
Batched and idempotent, in the background.
If MicroAuth is unavailable, your API can keep serving from its cached snapshot and send buffered usage when the connection returns.
Features
Everything you need to run a paid API
Branded customer portal
Give customers one place to sign up, create keys, view usage and pay. Use a MicroAuth subdomain or your own domain.
Managed API keys
Customers create and revoke keys in the portal. Your API verifies them from a local cache.
Per-customer rate limits
Set limits by default, plan or customer. Enforce them inside your API and share them across workers with Redis.
Usage-based billing
Count authenticated responses and charge customers only for the status codes you choose.
Stripe or your own billing
Use Stripe for checkout and subscriptions, or keep your billing system and manage credits through the API.
Teams and access controls
Manage workspaces, roles, audit logs and two-factor authentication for your team and your customers.
Flat monthly pricing. No revenue share.
Your customers pay you directly through your own Stripe account. We never touch your revenue.
FAQ
Questions developers ask us
Does my API traffic go through MicroAuth?
No. MicroAuth is not a gateway or a proxy. The SDK inside your API caches customer limits and reports usage metadata in batches. Request bodies, headers, query parameters and response bodies never leave your infrastructure.
What happens to my API if MicroAuth goes down?
Your API keeps serving. The SDK works from its cached snapshot and buffers usage reports until we are reachable again. You choose the failure mode: keep serving with the last known data, or reject requests once the data is older than a threshold you set.
How do my customers pay me?
Customers top up credits or subscribe to plans through your own Stripe account. MicroAuth handles the checkout and webhook flow. If you bill outside Stripe, grant credits from your own system with one API call.
Do you take a cut of my revenue?
No. Payments go straight to your Stripe account. You pay a flat monthly price and nothing per transaction.
I don’t use Python. Can I still use MicroAuth?
Yes. FastAPI has a ready-made SDK. For other stacks, the integration uses three HTTP endpoints to fetch a snapshot, verify a key and report usage.
Give your API keys, limits and billing today
Create your account, add the SDK, and share your portal link. Your first paying customer is a signup away.