QuotaMesh{{ 'ISOLATED DEMO' if demo_mode else 'LOCAL GATEWAY' }}
YOUR LOCAL AI CAPACITY WALLET

Your access.
Ready for each project.

Know what you own, understand what your project can use, and connect through qm/<profile> with explicit spend rules.

{{ error or '' }}
{% if demo_mode %}
NO API KEY NEEDED

Try a failure. See what happens.

This demo uses temporary data, fake credentials, and simulated dollars. Loading a scenario resets only this demo's rules and history.

{% else %}

Want a safe first look? Run .venv/bin/quotamesh demo for a separate, temporary demo with scripted failures. No provider credentials required.

{% endif %}
API credentials{{ routing.credentials|length }}Authorized access you configure
Eligible right now{{ decisions|selectattr('eligible')|list|length }}Policy eligibility, not verified quota
Observed paid spend today${{ '%.4f'|format(routing.usage.daily) }}UTC · through QuotaMesh only
01 / MY AI CAPACITY

What you own. What we've observed.

LOCAL OBSERVATIONS

Sources: MANUAL = your metadata; PROVIDER = upstream usage; LOCAL = gateway count or estimate; UNKNOWN = no evidence. Shared keys represent one capacity source. Outside-gateway usage is invisible; remaining provider quota is unknown.

02 / CREDENTIALS

Your credentials

WRITE-ONLY SECRETS
Add API access
OR
Account, credit, expiry, and priority

Manual dollar value only. Do not enter abstract provider credits. Shared keys must use the same starting amount; this is not a live balance.

Keys for the same provider project should share a group. A label does not create more quota. Blank groups share the provider default; Groq defaults to one group per credential.

Lower priority number comes first. Ties keep credential creation order.

Secrets are plaintext in local SQLite, with best-effort file restrictions. Environment references avoid saving the key. No arbitrary .env file is loaded.

An explicit listing check contacts the provider. It never automatically sends a generation request.

03 / PROJECT PROFILES

One policy for each app.

qm/default

Each target is a provider + model + key choice. “Provider pool” tries matching enabled credentials by priority. QuotaMesh keeps your saved order; it never ranks or invents equivalent models.

Templates change the form only. Mixed-plan pools become explicit key targets to preserve free-first order. Inspect and save the result; runtime always uses your saved order.

Skipped keys do not consume attempts. The gateway does not sleep through cooldowns or retry the same key/model. Changes take effect when you save.

04 / AVAILABLE NOW

Understand your saved route.

A dry run makes no upstream call. Eligibility uses the exact live selector; quota and generation access are not guaranteed.

Explain paid caps and recovery
EXPLICIT REQUEST / USES YOUR ROUTE

Test a real request.

This sends your message to the selected provider. With real credentials it can use quota or money when your policy permits. Response text is shown here only, never saved in history.

No test sent yet.
Your response will appear here.
05 / CONNECT YOUR PROJECT

One endpoint. Your project's rules.

qm/default

Select a saved profile to load connection instructions.

06 / ON-DEMAND DOCTOR

Check access deliberately.

Listing checks validate listing access only. Generation checks test one saved target under this project's policy, with no fallback. No background provider checks run.

No check running.
07 / ACTIVITY

Follow each request.

Metadata only · 30 days / 50,000 attempts

Attempts sharing a request ID belong to the same request. Skips and failures contain no prompt, response body, or provider secret. Connecting to local activity…

Latest ten upstream attempts across all profiles
Time (UTC) / requestAttempt / targetResult / reasonLatency / cost
08 / ACCESS CATALOG

A small starting point.

Official access and documentation links, with verification dates. Programs change; these notes never determine routing or promise a free quota.