Public evidence index / Open Permit Fees AWS delivery pilot
Open Permit Fees: AWS Data Exchange Delivery Pilot
Citation-grade building-permit fee schedules, one jurisdiction at a time. Commission one US jurisdiction for $249 once and receive a purpose-built extractor plus the fee schedule as a public GitHub pull request within 10 business days under CC BY 4.0.
This page takes no payment and creates no order. It documents the working GitHub delivery path and the exact boundary of an AWS Data Exchange pilot. Source suitability is reviewed before a payment path is offered.
Request one-jurisdiction scope
AWS CLI readback on 2026-08-09 found a finalized five-asset revision, but the Marketplace product shell remained Draft with no dataset attached. AWS Marketplace delivery is not offered on this page.
Why a “typical permit fee” is the wrong data product
Most permit-fee data fails when a source schedule is flattened into one representative number. Every fact that made the number usable—that it was a valuation tier, one choice among several, a percentage of construction value, a rate per unit, or a pointer to another table—is destroyed at extraction. The resulting value may look convenient, but a cost estimator cannot defend it to a client or trace it to an adopting authority.
Open Permit Fees produces the opposite artifact: every published number travels with the public source URL, the digest of the exact retrieved bytes, the retrieval time, the adopting instrument, the source-stated effective date, and the page, line, and matched text. Distinct fee structures stay distinct. Things not found are labeled as not found rather than rounded to zero or inherited from a neighboring row.
A published fee schedule is usually a PDF or code page containing at least six different structures:
- Flat: an amount for a precisely defined action.
- Option: several amounts whose applicability depends on a stated choice.
- Valuation-tiered: a base and marginal structure across construction-value bands.
- Per-unit: a rate applied to fixtures, square footage, or another counted quantity.
- Percent-of: a calculation against another stated amount.
- Reference: a direction to a separate table, code section, or authority.
No flattening: the schema has deliberately never carried a “typical fee” column. Applying a schedule to a specific project remains the buyer’s or expediter’s work; this offer publishes the schedule the jurisdiction published.
Who buys this
Permit expediters use cited schedule data when they need to show a client where a budget figure originated before an application is filed. Construction cost-estimation leads need valuation tiers to remain tiers and percentages to remain percentages when the data enters a workbook or estimating system.
Construction-software product managers need a number’s source to travel through the product because “where did this come from?” is otherwise a support ticket. Civic-tech and proptech data procurement leads need a stable schema, a redistributable dataset license, explicit coverage states, and a provenance trail that can survive internal review.
If AWS Marketplace is a mandatory transaction vehicle, this pilot is not a fit today. The public GitHub pull request is the delivery path offered by the $249 contract. The AWS readiness ladder below distinguishes what the platform can read now from what a buyer can procure now.
Counted sample evidence
The staged AWS Data Exchange package was counted from its actual CSV and five files on 2026-08-09. These are sample coverage facts, not a claim of broad market coverage.
- Jurisdictions: 1.
- Rows: 10 across 20 CSV columns.
- Published: 8 rows.
- Not found in the document: 2 rows, kept distinct from zero and from missing output.
- Citation completeness: 8 of 8 published rows carry all eight required citation fields.
- Delivery assets: CSV, JSONL,
coverage.json, dataset card, and JSON-LD.
The two not_found_in_document rows are part of the evidence. They name lines the extractor was expected to seek but did not locate in the retrieved source. They are counted in coverage and never filled with an estimate.
Inspect the five-file v0.1.0 release or download the sample CSV directly. No government fee amount or copied source excerpt appears on this page; those facts stay inside the downloadable artifact beside their citations.
What a commissioned jurisdiction delivers
- Purpose-built extractor. Code written against the selected jurisdiction’s actual document structure, with fixtures and checks that pin its interpretation.
- CSV. The extracted fee schedule in schema 1.0.0, including coverage, structure, and source fields.
- JSONL. The same records as one JSON object per line for pipelines that prefer nested provenance.
- Coverage and dataset card. Machine-readable counts plus the human-readable source, method, retrieval, schema, and limitation record.
- JSON-LD. Dataset metadata suitable for catalogs and discovery systems without hand-keying the description.
The extractor and all five delivery assets arrive in a public GitHub pull request within 10 business days after written scope acceptance and payment. The dataset output is CC BY 4.0. The work becomes public; buyers requiring private output should not purchase this offer.
Field-level contract
| Contract | What it binds | How a buyer checks it |
|---|---|---|
| No typical-fee field | No blended or representative fee column exists. | Read the CSV header; the field is absent rather than blank. |
| Structure preserved | Flat, option, valuation-tiered, per-unit, percent-of, and reference rows remain distinguishable. | Inspect structure-bearing fields instead of trusting a summary. |
| Published-number citation | Every published amount requires source_url, document_sha256, retrieved_at, adopting_instrument, effective_date, page, line, and matched_text. | Filter published rows and assert all eight are non-empty. |
| Exact-byte identity | The document digest identifies the bytes the extractor read. | Hash a retained download and compare it with the row. |
| Unknown states | not_fetched, not_found_in_document, and not_published_by_jurisdiction never collapse into one another. | Count each status in coverage.json. |
| First observation | The initial ingest is not falsely labeled as a fee change. | Review change events and confirm the first event is first_observed. |
| Schema stability | Schema 1.0.0 does not rename or remove fields inside the major version. | Pin the version and diff headers across releases. |
| Retrieval, not currency | retrieved_at says when bytes were observed; it is not a claim the source remains current. | Refetch the official source before relying on it. |
AWS readiness ladder
PROVEN
- An owned AWS Data Exchange dataset exists.
- Its named revision is finalized.
- A direct AWS API count returns five assets with the same five names as the public package.
- The public release and CSV are independently downloadable.
PENDING
- The Marketplace DataProduct shell remains Draft.
- Its
DataSetscollection is empty. - No buyer-facing AWS catalog URL has been fetched.
- No AWS subscription can be observed.
NOT OFFERED
- AWS-native procurement or delivery today.
- A date for AWS availability.
- AWS approval, endorsement, partnership, or co-selling.
- A paid subscription represented as active.
Publication boundary: The AWS catalog listing is not represented as available until a buyer-facing AWS URL is fetched.
AWS documents its data model as assets inside revisions inside datasets. A finalized revision can be attached to a product for subscriber access, which is why “a dataset exists” and “a buyer can subscribe” are separate facts. See AWS’s primary documentation for datasets, revisions, and assets, provider qualification and registration, and publishing eligibility and restrictions.
This page is not affiliated with or endorsed by AWS. The AWS names describe a potential delivery channel and direct API observations, not a partnership.
Browser-local scope checker
Use this free checker to test whether a one-jurisdiction request has the five fields needed for source review. It makes no network call, uploads nothing, stores nothing, and cannot establish that a source is available, current, lawful to retrieve, or in scope. A green shape result is not acceptance.
Enter one jurisdiction to preview the scope rule.
Acceptance and decline
| Accepted for source review | Declined before payment |
|---|---|
| One US jurisdiction with an official public fee schedule. | A source behind login, paywall, access agreement, or retrieval prohibition. |
| A document that can be retained, hashed, and cited by page and line. | A private document supplied by the buyer or licensed from a third party. |
| PDF, HTML, or a comparable published official format. | A request to interpret which fee applies to a particular property or project. |
| A jurisdiction not covered in the current public repository, or a separately scoped refresh. | A credential, account, private API, permit application, property address, or personal record. |
| A public result under CC BY 4.0 delivered through GitHub. | Private work product or mandatory AWS Marketplace delivery today. |
If no official public fee schedule can be lawfully and reliably retrieved, the scope is declined before payment. The source review is the gate; a buyer is not charged for a jurisdiction the product cannot source under the published contract.
Exact workflow
- Request scope. Submit jurisdiction and state, official source URL if known, intended workflow, required formats, and deadline. The request takes no payment.
- Source suitability. We locate the official fee schedule, confirm it is public and retrievable, and decide whether its structures can be represented faithfully. The result is accept or decline.
- Written scope. On acceptance, the jurisdiction, source, five files, extractor, license, public delivery method, price, and 10-business-day clock are frozen in writing.
- Payment. The buyer receives a $249 one-time payment path only after scope acceptance. This page contains no checkout.
- Extraction. A purpose-built extractor runs against the retained source bytes. Published rows must pass the citation invariant; missing evidence remains an explicit unknown.
- Public delivery. A GitHub pull request carries the extractor, files, coverage, and tests. Buyers can inspect the same artifact they receive.
Nothing in this flow files a permit, estimates a project-specific fee, represents a buyer before an agency, or guarantees that a schedule remains current after its stated retrieval time.
Custody, licensing, and request boundary
The dataset output is public under CC BY 4.0. A buyer can redistribute it and build on it with attribution. That also means commissioned work becomes public. The code remains available in the Open Permit Fees repository, and the selected official source remains attributed in every published record.
The request form accepts only a jurisdiction and state, an official public URL if known, intended workflow, required formats, and deadline. It rejects credentials, private documents, pasted dataset rows, personal data, permit applications, property addresses, applicant or owner information, payment data, and anything behind a login.
Method limit: the dataset records what the cited public artifact states at the observed time. It does not give legal advice, certify compliance, determine a project’s fee, certify a source’s continuing availability, or establish that the source is the only controlling authority.
Alternatives and fit
Do it yourself when one jurisdiction is familiar and a one-time manual read is sufficient. Use a general cost aggregator when early-stage feasibility matters more than a line-level adopting source. Hire a consultant when the desired output is an interpretive memo instead of a reusable extractor and schema. Wait for AWS delivery when AWS Marketplace is an absolute procurement requirement.
Good fit
- You need one named jurisdiction.
- You need each published number traceable to exact source bytes and a page and line.
- Fee structures matter to your calculation.
- CC BY 4.0 and public GitHub delivery fit your workflow.
Not a fit
- You need national coverage in one purchase.
- You want a single typical-fee field.
- The output must remain private.
- You require AWS Marketplace procurement today.
- You need a project-specific fee determination or a permit filing.
Frequently asked questions
Is $249 a government fee?
No. It is the one-time service fee for extracting and publicly publishing one jurisdiction. It buys no permit, filing, or agency relationship.
What arrives?
A public pull request containing the purpose-built extractor, CSV, JSONL, coverage file, dataset card, JSON-LD, and tests for the accepted jurisdiction.
Can a buyer subscribe through AWS Data Exchange?
No. A finalized five-asset revision exists, but the Marketplace product is still Draft and has no dataset attached. No AWS subscription or procurement path is represented as active.
Why is there no typical fee?
A blended number discards the applicability rule that makes the schedule usable. This dataset preserves the jurisdiction’s stated structure.
What happens to a fee the extractor cannot find?
It receives an explicit unavailable status and appears in coverage. It never becomes zero, an estimate, or a copied neighbor.
Is the schedule guaranteed current?
No. Retrieval time, source digest, adopting instrument, and effective date let a buyer assess the cited artifact. The offer makes no claim about a later source state.
Does the page take payment?
No. It accepts a bounded scope question. Payment is possible only after source suitability and written scope acceptance.
Request one-jurisdiction scope
Commission one new US jurisdiction for $249 once. Receive the purpose-built extractor and citation-grade dataset as a public GitHub pull request within 10 business days under CC BY 4.0.
Request source and scope review
Send only jurisdiction, state, official public source URL if known, intended workflow, required formats, and deadline. No payment is collected at request time.