Public evidence index / Machine storefront
Agent-quotable offer catalog
Machine-readable price, cadence, fixed scope, request paths, and explicit NOT-COVERED boundaries from the canonical catalog.
Contract and source boundary reviewed 2026-08-09. Counts are out of every currently listed offer loaded from the canonical source for this response, not a copied total. Evidence-backed offers with a stale, synthetic, future, or unreadable listing decision are omitted.
The feed describes a bounded offer; it never accepts one.
69catalog offers
46one-time scopes
23monthly scopes
one sourcefor price and scope
Machine-to-human handoff
Read
An agent retrieves the JSON feed with a safe GET and selects by price, cadence, summary, and included scope.
Bound
The agent presents both scope_included and not_covered. A summary without its limits is incomplete.
Hand off
A human reviews the product page and chooses whether to open and submit the product-specific request form.
Representative paid routes
These cards are rendered from the same canonical objects as the feed. Their summaries, prices, scope lists, and SKU-specific exclusions are not copied into this route.
Cited Question Answer
$249
A bounded answer to one source-descriptive question about one writer-controlled public article, with an input-page receipt, claim-level citations, and a closed source disposition table.
Scope included
- One public HTTPS article URL the requester controls or may submit
- One bounded source-descriptive question
- Input-page URL, UTC retrieval, HTTP result, byte count, title, canonical, and SHA-256
- Up to eight buyer-approved public sources with claim-level citations
- Supporting, no-answer, unreachable, indeterminate, excluded, outside-scope, and beyond-cap rows
- Private PDF and Markdown within two business days after accepted scope
NOT-COVERED
- Supporting, no-answer, unreachable, indeterminate, excluded, outside-scope, and beyond-cap rows
Review request scope
Agent Job Output Review and Contract Kit
$349
A bounded review of up to five recurring AI-agent or automation jobs, with a claim-to-evidence matrix, up to three draft useful-work contracts, and synthetic negative-control fixtures.
Scope included
- Dated PDF findings matrix for at most five recurring jobs
- Up to three draft JSON contracts or explicit NOT CONTRACTABLE reasons
- Shared Python standard-library harness tailored with synthetic fixtures
- USEFUL, HONEST IDLE, DEAD WORK, ERROR, and UNKNOWN kept distinct
- No actuator, production access, credentials, deployment, or certification
- Delivery within five business days after complete accepted intake
NOT-COVERED
- Up to three draft JSON contracts or explicit NOT CONTRACTABLE reasons
- No actuator, production access, credentials, deployment, or certification
Review request scope
MCP API Launch Pack
$457
A source-delivered MCP adapter for exactly three documented, side-effect-free operations in one existing JSON API. It includes stdio and loopback Streamable HTTP profiles, fixed schemas, fixtures, and rerunnable acceptance checks; the customer deploys and operates it.
Scope included
- MIT-licensed Python source, locked dependencies, Dockerfile, and Compose file
- Exactly three curated read-only tools with typed input and result schemas
- Stdio and loopback Streamable HTTP launch profiles
- MCP Inspector transcript and ten deterministic contract cases
- Written local acceptance commands and a thirty-day defect-correction window
- Delivery within seven business days after written scope acceptance and payment
NOT-COVERED
- No scope beyond scope_included is included.
Review request scope
Feed contract
| Field | Meaning | Required use |
|---|
sku, label | Stable catalog identifier and human title. | Carry both into the handoff. |
price | Integer cents, USD, cadence, and display text from the canonical offer. | Use the integer for comparison and display text for presentation. |
summary | The canonical bounded description. | Never treat it as the whole scope. |
scope_included | The fixed deliverables attached to that SKU. | Present before a request. |
not_covered | Common commercial limits plus SKU-specific negative scope. | Present beside included scope, not behind it. |
offer_url | The human-readable product page. | Give it to the reviewing human. |
request_url | The product-specific scope form. | Open for human review; never auto-submit. |
checkout_armed | A descriptive boolean from the allowlisted payment-link registry. | Never use it as permission to purchase. |
NOT-COVERED is part of every offer
- Any work not explicitly listed in scope_included.
- Automatic submission of request forms, contract creation, or work outside a row whose machine_purchase status is READY.
- Guaranteed indexing, citation, ranking, traffic, revenue, legal outcomes, compliance outcomes, or external-platform behavior.
Every feed row also carries sku_specific. If the canonical deliverables contain no additional negative scope, the row says that no scope beyond scope_included is included.
Safe integration
Retrieve https://ustechautomations.com/permits/agent-quotable-offers/offers.json with GET, cache its ETag, compare integer cents, and show the selected offer to a human together with every scope limit. A client that cannot retrieve or parse the feed has an UNKNOWN result. It does not have an empty catalog.
The feed contains no credential, payment-processor URL, personal contact field, or POST instruction. A READY candidate exposes only the canonical same-domain /buy hop; every other row exposes a null purchase URL.
At this response, 0 of 4 machine-purchase candidates are READY; 4 are PARKED and 0 are UNKNOWN. A row with any blocker or unreadable required evidence keeps may_auto_purchase false.
Request boundary
To be plain about what this page is: it is a demand test. Submitting the form stores a scope request and nothing else. A request is not an order, it schedules no work, it reserves no delivery date, and it creates no obligation on either side. If the scope is a fit, the next step is a conversation, not an invoice.
Reading this page or its feed sends no message. Opening a request page sends no message. Only the human reviewing a product-specific form chooses whether to submit it.
Freshness and change semantics
The response is serialized from offer_catalog.OFFERS when requested. offer_count, prices, cadence, summaries, scope, request URLs, and checkout state therefore share one request-time source. The feed supplies an ETag so clients can detect a byte-level change without inventing a version date.
A removed SKU disappears from the next response. A changed price or scope changes the ETag. Clients should not preserve an earlier row as a current quote after the feed changes; they should retrieve the product page again before a human submits a request.
Questions agents should answer before handoff
Is the feed an acceptance or contract?
No. The feed describes a bounded offer; it never accepts one.
May an agent submit the request form?
No. Every row states may_auto_submit: false. Automatic purchase is a separate per-row decision, and only a row whose machine_purchase.status is READY may set may_auto_purchase: true. At this response, 0 of 4 machine-purchase candidates are READY; 4 are PARKED and 0 are UNKNOWN. A row with any blocker or unreadable required evidence keeps may_auto_purchase false.
Does a catalog fetch prove demand or a citation?
No. It is retrieval telemetry only. It does not prove a buyer, referral, citation, request, checkout, or payment.
What if the feed cannot be read?
Report UNKNOWN. Do not report zero offers, an empty scope, or permission to improvise.
Read the canonical JSON feed