Last updated: October 24, 2026
AgentMeter is a prototype developed by EIEI / Eisuke. Its public pages are hosted on Dotfield. The interactive sandbox is hosted separately on Render and offers personal buyer workspaces; operator screens require a maintainer-provided token. These information pages do not themselves run account registration, checkout, or tool execution.
Public website
These pages do not include an AgentMeter signup form, advertising, or application analytics. Cloudflare hosts the website and may process request information, including IP addresses, browser information, timestamps, and requested URLs, to deliver and protect it. See Cloudflare's privacy policy.
Hosted sandbox
Render hosts the Node application and its persistent SQLite ledger. Personal buyer workspaces store a chosen nickname, balance, funding records, tool usage and budget settings. The personal console queries only the signed-in workspace. The maintainer can access the prototype ledger for operation and testing; operator demo records remain a separate shared demonstration. Test records may be reset during development. See Render's privacy policy.
Workspace access
Registration needs a nickname, not an email address. A recovery code is shown once and signs you into that workspace. New recovery codes, browser-session tokens and client API keys are stored as hashes. Client keys are shown once, with only their label, suffix and timestamps visible later. Keys can be revoked. Legacy operator demo keys retain their existing storage format and are not personal customer keys.
The personal console uses an HttpOnly browser cookie for a seven-day session; sessions survive service restart. Signing out invalidates that session. There is no email recovery: keep the recovery code privately and never send it to support. Client keys authorize tool calls, not console administration. Registration and request limits apply to this experimental service.
Provider tools and upstream services
A provider profile adds a public display name and a private sandbox payout email. Published tool names, descriptions, prices, input schemas and upstream host/type are visible to buyers. The provider console shows only that provider’s earnings and payout records. Recipient email ownership is not verified in this prototype.
Registered API/MCP calls send the buyer’s arguments to the selected provider service and store its result preview for the receipt. Use only trusted providers and synthetic inputs. Optional upstream Bearer/X-API-Key secrets are encrypted at rest with a private key stored beside the ledger on the persistent disk; they are not returned by the console. Providers can replace credentials, pausing the tool until it passes another connection test. Service operators can access the runtime and disk.
Sandbox test data
The prototype is designed to store test account names, sandbox recipient email addresses, tool definitions, tool-call inputs and output previews, budget policies, and ledger records. PayPal integration records may include sandbox order, capture, payout, transaction, and webhook identifiers, amounts, statuses, fees, and API responses. These records support metering, troubleshooting, payout tracking, and reconciliation.
Use synthetic inputs and PayPal sandbox accounts for testing. Do not submit real customer information, financial details, passwords, API secrets, or other sensitive information as tool inputs. The hosted demo displays its sandbox operating mode.
PayPal and optional AI services
Sandbox payments use PayPal's test environment. PayPal processes information entered on its own checkout and login pages under its own policies. AgentMeter does not request or store your PayPal login password or full card details. See PayPal's privacy statement.
The built-in metered tools run without a model or network call. When configured, optional AI features use Google's Gemini API through the AgentMeter backend. Widget interpretation sends the usage question and tool names. Budget interpretation sends the instruction and tool names/descriptions; narration sends settled-call counts and aggregate micro-USD amounts. Semantic labeling sends only built-in tool descriptions and synthetic historical examples. These features do not send payment credentials, account API keys, PayPal identifiers, or the complete ledger.
Model output is checked before a view or budget is applied. Model failures fall back to deterministic interpretation where supported. Use synthetic questions and avoid sensitive, confidential, or personal information. Google's unpaid Gemini services may use submitted content and responses to improve products and may involve human review. See the Gemini API terms and Google privacy policy.
Support, retention, and requests
If you email support, your email address and message are used to respond to your inquiry. Prototype test data may be reset during development and is not intended as permanent storage. For access, correction, deletion, or other privacy questions, contact ekawano114@gmail.com. Do not include credentials in your message.
This page will be updated when the prototype's data handling changes.