OpenMeter
Official@openmeterio · United States of America
Metering and Billing for AI, API and DevOps
Agent Skills by OpenMeter
Showing 10 vetted skills indexed across 1 GitHub repositories.
ent
Guides Ent ORM schema changes, code regeneration, and Postgres type mappings in Go.
iterative-engineering-design
Guides planning and implementation of complex engineering changes through shared system models.
api-filters
Implements Kong AIP-style query-parameter filters on OpenMeter v3 list endpoints.
rebase
Rebase OpenMeter branches while resolving migration, atlas.sum, and Ent generated-code conflicts.
domain-docs
Locate and maintain package-level domain documentation in the OpenMeter repository.
test
Create and run unit, integration, and service tests for OpenMeter.
db-migration
Generate SQL migrations for ent framework schema changes on PostgreSQL.
api
Define API endpoints in TypeSpec and generate OpenAPI specs and SDKs.
refactoring
Refactor Go packages into standardized service and adapter layers.
service
Create and modify OpenMeter service packages with interfaces and implementation patterns.
Frequently Asked Questions About OpenMeter
FAQPage SchemaWhat specific billing tasks does OpenMeter enable?▼
OpenMeter enables the tracking and calculation of usage-based metrics for services. It supports defining granular consumption events, managing schema changes for billing data, and structuring service layers to ensure accurate metering and financial reporting across distributed environments.
Which engineering personas benefit from OpenMeter?▼
Backend engineers and platform architects focused on monetization and usage tracking benefit from OpenMeter. It is designed for teams building usage-based products who require standardized service patterns, robust database migration management, and clear interface definitions for their billing infrastructure.
What are the core technical prerequisites for implementation?▼
Implementation requires familiarity with the Go programming language and the ent framework for database modeling. Users must define endpoints using TypeSpec to generate specifications and maintain service packages structured into standardized adapter layers for integration with existing infrastructure.