Talk to AgentMeter.
For product help, security reports, billing questions, or launch feedback, reach the team at support@pylva.com.
The fastest support requests include the SDK language, endpoint, affected workspace, approximate timestamp, and whether the issue involves event ingest, rule sync, pricing lookup, budget sync, or customer billing. Do not send prompts, completions, API keys, or raw customer messages in email.
Support
SDK setup, API keys, telemetry validation, event ingest, rules, pricing lookup, budget sync, and dashboard questions.
Security
Responsible disclosure, suspicious behavior reports, authentication concerns, and production safety issues.
Partnerships
AI agent platforms, observability products, billing providers, implementation partners, and developer tooling integrations.
For sales or product feedback, describe the agent workflow you are trying to meter, whether your cost comes only from LLM providers or also from tools such as search, speech, retrieval, payments, and workflow execution, and whether you need customer-facing billing or internal margin visibility first.
For security reports, include reproducible steps, the affected URL or endpoint, expected impact, and whether the issue affects public marketing pages, SDK telemetry, authentication, customer portal visibility, or billing data.
For launch feedback, include the product you are building, how you charge your customers today, which providers and tools create cost, and where margin visibility breaks down. That context helps the team distinguish SDK instrumentation questions from pricing, rules, billing, and customer portal questions.
For operational incidents, include whether the issue is isolated to one customer or workspace, whether retries are involved, and whether the failure blocks telemetry ingest or only delays cost calculation. This keeps support focused on the financial impact.
If you are comparing AgentMeter with observability, billing, or usage-metering tools, mention the alternative products in the note. That helps route the conversation toward cost attribution, non-LLM usage, pre-call rules, or customer-facing billing instead of repeating generic product discovery.