Cannabis Flower Per Ounce Jurisdiction Lookup
Exact independently verified cannabis flower excise rates reference registry lookup in explicit jurisdiction, product, mass basis, tax point and dated authority context, retaining source and as-of date. Caller supplies the actual applicable record, including qualifications, exceptions and uncertainty; illustrative examples are not authoritative records. No built-in complete/current data, eligibility, authenticity, legal/coverage determination or advice.
Description
Cannabis-flower excise references need product, mass basis, jurisdiction, and tax point.
Cannabis-flower excise references need product, mass basis, jurisdiction, and tax point.1
This lookup returns your verified record without inferring current rates or legal transaction status.
When to use Cannabis Flower Per Ounce Jurisdiction Lookup
Use this tool when you need to retrieve a verified reference with its source, context, and as-of date. Establish jurisdiction, tax year, applicable authority, and eligible amounts or evidence before entering values.
How to use Cannabis Flower Per Ounce Jurisdiction Lookup and understand its results
- Establish jurisdiction, tax year, applicable authority, and eligible amounts or evidence before entering values.
- Enter callerVerifiedSource, callerVerifiedContext, callerVerifiedAsOfDate, callerReferenceKeys, callerReferenceTexts, queryReferenceKey, following the field table and rules below, then run the tool.
- Read result. Use the output meanings below to interpret units, signs, flags, and any nested result fields.
- Correct reported input issues and run again. For a successful result, check the stated evidence coverage and assumptions before using it in your review.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerVerifiedSource | Caller verified source | string | Required |
| callerVerifiedContext | Caller verified context | string | Required |
| callerVerifiedAsOfDate | Caller verified as of date | string | Required |
| callerReferenceKeys | Caller reference keys | list of string | Required |
| callerReferenceTexts | Caller reference texts | list of string | Required |
| queryReferenceKey | Query reference key | string | Required |
Enter a nonblank independently verified source and context, each at most 256 characters, a real Gregorian YYYY-MM-DD as-of date with year 0001–9999, unique nonblank reference keys, aligned nonblank reference texts, and an exact query key. Return the matching text unchanged inside result together with source, context, and asOfDate. Keys are case-sensitive and are not trimmed or normalized for matching. A missing key is an input error; the tool neither downloads records nor verifies their authority or freshness.
result.matchedCallerReference=referenceTexts[indexOf(referenceKeys,queryKey)] Symbols follow the input and output meanings and the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Calculated observation or qualified reference | object |
| result.matchedCallerReference | Matched Caller Reference | string |
| result.source | Source | string |
| result.context | Context | string |
| result.asOfDate | As Of Date | string |
{
"input": {
"callerVerifiedSource": "independently-reviewed-source/edition",
"callerVerifiedContext": "jurisdiction, product, mass basis, tax point and dated authority",
"callerVerifiedAsOfDate": "2026-01-01",
"callerReferenceKeys": [
"record-a",
"record-b"
],
"callerReferenceTexts": [
"Caller independently verified cannabis flower excise rates record a",
"Caller independently verified cannabis flower excise rates record b"
],
"queryReferenceKey": "record-a"
},
"output": {
"result": {
"matchedCallerReference": "Caller independently verified cannabis flower excise rates record a",
"source": "independently-reviewed-source/edition",
"context": "jurisdiction, product, mass basis, tax point and dated authority",
"asOfDate": "2026-01-01"
}
}
}Limitations and assumptions
The supplied registry, source, context, and date are records, not independently authenticated evidence. There is no built-in complete or current tax database. Rates, deadlines, exemptions, qualifications, and exceptions must be verified for the actual case before supplying a record.
Missing required fields, unknown fields, wrong types, and violated calculation rules are input issues. Evidence arrays must be dense, with no missing cells. String lists allow at most 128 strings of at most 128 characters. Extremely large text is rejected. Extremely large composite outputs are rejected.
Alternative or Complementary methods
For a related review, use Excise Tobacco Per Pack Lookup: Tobacco excise rates need a jurisdiction, product, pack size, and tax point. This lookup returns a verified reference with those qualifications instead of assuming a universal per-pack charge. For a complementary step, use Carbon Price Per Tonne Jurisdiction Lookup: A carbon price reference needs the scheme, emissions basis, period, and jurisdiction. This lookup returns your verified record without equating different carbon-pricing mechanisms.
References
Similar or alternative tools
- Excise Tobacco Per Pack Lookup
Tobacco excise rates need a jurisdiction, product, pack size, and tax point. This lookup returns a verified reference with those qualifications instead of assuming a universal per-pack charge.
- Carbon Price Per Tonne Jurisdiction Lookup
A carbon price reference needs the scheme, emissions basis, period, and jurisdiction. This lookup returns your verified record without equating different carbon-pricing mechanisms.