Dashboard
Enter your API key to view usage, manage keys, and access billing.
Common failure mode
A stale local USPS_ADMIN_SECRET copy in Keychain or .dev.vars.
What this opens
Internal USPS operator metrics from the live Queue + D1 rollups. Secret stays in memory for this tab only.
Billing fallback: support@revaddress.com
Don't have a key? Get a Free API Key
Your key is stored locally in your browser — never sent to our servers beyond API calls.
Dashboard
Rate Limit
Per-key burst limit
Credits
How credits workChecking whether purchased credits have posted. Returning from Stripe does not confirm payment.
USPS license (BYOK)
Checking…Connect your own USPS Developer Portal app and every USPS call — DPV verification, rates, service standards, shipping options, city/state, tracking, pickups — runs on your license through our infrastructure. Any tier can connect, Free included.
Last verified
—
OAuth token
—
Labels & payments
—
API Keys
Rotate all secret keys?
This will revoke every existing secret key and create a new one. All integrations using current keys will stop working immediately. Publishable keys are not affected.
New API key generated. Copy it now — it won't be shown again.
Publishable key created. Copy it now — it won't be shown again.
Use this key in your Checkout Guard widget <script> tag. It can only access widget endpoints.
Recent API Calls
| Endpoint | Date | Calls |
|---|---|---|
| Loading... | ||
Usage by Endpoint
Loading...
Quickstart
Copy a snippet and make your first API call.
Subscription
Try It
Validate an address directly from the dashboard.
Internal USPS Operator Metrics
Rolling 24hInternal readout sourced from Queue + D1 rollups behind /api/admin/metrics. This view is operator-only and uses an in-memory admin secret.
Waiting for live metrics…
What counts here
Each row is a validation outcome from the public validator. Free validation requests and guided follow-up rechecks both feed this rollup.
What good looks like
A healthy front door trends toward more exact-deliverable results, controlled missing-secondary follow-up, and low extract-first share unless intake quality slips.
Expected surfaces
You should mainly see docs-api-reference and validate. Homepage is a future surface; unknown buckets usually mean telemetry drift worth checking.
Total requests
—
Exact deliverable
—
Missing unit
—
Extract-first share
Last seen
—
By surface
| Surface | Count |
|---|---|
| Loading... | |
By classification
| Classification | Count |
|---|---|
| Loading... | |
Rollup rows
| Surface | Classification | Flow | Count | Cached | With secondary | Errors |
|---|---|---|---|---|---|---|
| Loading... | ||||||