Meter Kinds
Meter Kinds
Every sign operation increments one billing meter. Meters are recorded in the audit log and reported in GET /v1/usage. The billing.meter field in a recipe specifies which meter to use.
Meter reference
| Meter | Description | Plans |
|---|---|---|
image_sign | Sign one image (JPEG, PNG, WebP) | All |
audio_sign | Sign one audio file (WAV, MP3, FLAC, OGG) | Developer+ |
video_sign | Sign one video file (MP4, WebM) | Developer+ |
text_sign | Sign one text generation event (SynthID-Text hook) | Developer+ |
image_verify | Verify one image (authenticated, counted) | All |
audio_verify | Verify one audio file | Developer+ |
video_verify | Verify one video file | Developer+ |
lookup | One soft-binding lookup call | All |
byok_sign | Sign using BYOK KMS key (additional meter on top of modality meter) | Enterprise BYOK |
anchor_batch | One anchor batch submission (all batch members share one submission credit) | Growth+ |
Notes
image_verify,audio_verify,video_verify: public verify (POST /v1/verifywithout authentication) does not count toward metered usage. Only authenticated verify calls are metered.byok_signis charged in addition to the baseimage_sign/audio_sign/video_signmeter. Both meters increment for a BYOK sign call.anchor_batch: a batch may contain hundreds of manifest digests. Each batch counts as one submission, regardless of how many manifests it contains.- Verify calls that return an error due to an internal failure (
verbitas.internal_error) are not metered. - Lookup calls that return zero matches are still metered.
Plan quotas
| Meter | Free | Developer | Growth | Enterprise |
|---|---|---|---|---|
image_sign | 50/mo | 1,000/mo | 20,000/mo | Custom |
audio_sign | — | 500/mo | 10,000/mo | Custom |
video_sign | — | 200/mo | 5,000/mo | Custom |
image_verify (authenticated) | 100/mo | 5,000/mo | 50,000/mo | Custom |
lookup | 100/mo | 5,000/mo | 50,000/mo | Custom |
Exceeding a quota returns 402 verbitas.billing.quota_exceeded. On the Growth and Enterprise plans, usage above the included quota is charged per-unit at rates listed in your plan agreement.
Checking current usage
curl -H "Authorization: Bearer $VERBITAS_API_KEY" \ https://api.verbitas.io/v1/usage | jq .Response:
{ "period_start": "2026-05-01T00:00:00Z", "period_end": "2026-06-01T00:00:00Z", "meters": { "image_sign": { "used": 423, "limit": 1000 }, "image_verify": { "used": 101, "limit": 5000 }, "lookup": { "used": 55, "limit": 5000 } }}Usage in the audit log
Every metered event is recorded in the audit log as asset.signed, asset.verified, or asset.lookup. The billing.meter field is included in the event data. Export the audit log to your billing system for cost allocation:
curl "https://api.verbitas.io/v1/audit?event_type=asset.signed&format=ndjson" \ -H "Authorization: Bearer $VERBITAS_API_KEY"