Commercial Licensing Terms

One rights boundary across human and machine access.

These terms describe the standard commercial license scope for The PostOpz Framework, PostOpz Guide, Framework Agent API, and autonomous x402 retrieval. A separately executed written agreement controls where it expressly differs.

Effective September 8, 2026. Purchasing, accessing, or using a PostOpz licensed product or paid retrieval service constitutes acceptance of the applicable license scope described here and any transaction-specific terms presented at checkout or with the paid resource. These terms are a commercial license agreement, not legal advice.

Framework Vol. 1 · $197Individual human-use license. Normal professional reference use is permitted; persistent AI ingestion is not.

Developer / Studio Agent LicensesPersistent authenticated retrieval rights for the licensed application or internal post team.

x402 Pay Per CallOne task-scoped retrieval response per successful machine payment. No corpus ownership or accumulation right.

Enterprise / Model / OEMSeparate written rights for training, fine-tuning, corpus ingestion, embedded products, redistribution, or broader deployment.

1. Framework Vol. 1 individual license

A standard purchase of The PostOpz Framework Vol. 1 and its included materials is licensed to one individual for that purchaser's own professional reference, education, and workflow implementation.

Permitted individual use

Read, reference, and apply the Framework in the purchaser's own editorial work.
Use supplied structures, checklists, and implementation guidance in the purchaser's own professional workflow, subject to any asset-specific instructions.
Quote or paste limited excerpts into an AI assistant for transient, user-directed clarification of the purchaser's own work, provided the excerpts are not retained or accumulated to create a persistent knowledge base.
Make reasonable personal working notes derived from the Framework.

Not included in the individual license

No training, fine-tuning, distillation, synthetic-data generation, benchmark creation, or evaluation-dataset construction using the Framework or substantial portions of it.
No creation of embeddings, vector stores, persistent RAG indexes, reusable knowledge bases, system-prompt corpora, or other machine-readable repositories containing the Framework or substantial derivative content.
No use of the Framework as a persistent knowledge layer for an internal or external AI agent, API, plugin, SaaS product, automated assistant, or other software system.
No systematic extraction, transformation, mirroring, or reconstruction intended to reproduce the Framework as a substitute dataset, product, training resource, or competing knowledge service.
No redistribution, resale, sublicensing, public posting, shared-drive distribution, team-wide use, or inclusion in paid or unpaid training materials without written permission.

Teams, developers, schools, facilities, and software products should use the appropriate Team, Agent, or Enterprise license rather than sharing or ingesting a single individual copy.

2. Developer and Studio Agent licenses

Developer and Studio plans license authenticated retrieval from the PostOpz Framework Agent API. They do not transfer ownership of the Framework corpus and do not grant model-training or corpus-ingestion rights.

Developer · $799/yearOne internal agent or application, up to the published monthly retrieval allowance, internal development/testing, and commercial prototyping for the licensed application.

Studio · $3,500/yearInternal post-team deployment, multiple internal workflows, and use up to the published monthly retrieval allowance by the licensed studio or organization.

Standard API outputTask-scoped answers, diagnostics, checklists, and workflow guidance may be shown to authorized users within the licensed scope.

Model training, fine-tuning, distillation, bulk embedding, systematic extraction, redistribution, resale, publishing, dataset creation, or OEM incorporation require separate written Enterprise rights.

3. Autonomous x402 retrieval

Each successful x402 payment authorizes one task-scoped response from the specific paid endpoint and for the immediate workflow task that triggered the request.

Payment does not create ownership of the Framework source knowledge or a perpetual license to the corpus.
Repeated paid calls may not be used to reconstruct, mirror, distill, benchmark, or accumulate a substitute PostOpz knowledge base.
Current per-call pricing is presented with the paid resource and may change prospectively. The machine-readable payment requirement presented at request time controls the price for that transaction.
Training, fine-tuning, bulk embedding, redistribution, resale, and OEM incorporation remain excluded unless separately licensed in writing.

4. Enterprise, model-training, and OEM rights

A separate written Enterprise agreement is required when PostOpz knowledge becomes a persistent part of a model, product, dataset, or distribution layer. Enterprise rights may include, when expressly granted in writing:

model training, fine-tuning, evaluation, or distillation;
bulk corpus ingestion or persistent embedding;
OEM, white-label, plugin, or embedded-product use;
high-volume deployment outside published Developer or Studio scope;
redistribution, sublicensing, or downstream commercial rights;
custom knowledge access, support, or commercial partnership terms.

Contact hello@postopz.com to scope Enterprise rights.

5. Anti-extraction and service safeguards

PostOpz may apply technical and operational controls to protect licensed knowledge and service availability. These controls may include usage limits, burst-rate limits, credential controls, automated abuse detection, extraction-pattern monitoring, output or account attribution, and suspension or review of activity that materially exceeds permitted retrieval use.

PostOpz does not publish detailed detection thresholds or anti-abuse implementation logic. Attempting to evade safeguards, rotate credentials to defeat limits, or distribute extraction across accounts does not expand the licensed scope.

6. Ownership and restrictions

PostOpz retains ownership of the Framework, underlying methodology, source corpus, product documentation, API knowledge layer, and other PostOpz intellectual property. Licenses grant only the limited usage rights expressly described for the purchased product or written agreement.

No license grants the right to claim PostOpz materials or substantially reproduced workflow knowledge as original proprietary material of the licensee.

7. Credentials, access, and suspension

API credentials must remain within the licensed organization and application scope and should be stored server-side.
Credential sharing outside the licensed scope is prohibited.
PostOpz may limit, suspend, or terminate access for material abuse, nonpayment, credential compromise, extraction activity, or use outside the licensed scope.
Suspension or termination does not create rights to retain or redistribute the underlying corpus.

8. Production information and professional judgment

Do not submit source media, confidential production information, personal data, or third-party material unless you have authority to process it through the service.
PostOpz workflow guidance is a professional reference and must be reconciled with project-specific requirements, vendor specifications, network delivery rules, security policies, and professional judgment.
No workflow answer guarantees technical acceptance by a network, platform, finishing vendor, or other third party.

9. Transaction-specific terms

Pricing, billing period, included usage, renewal behavior, payment method, and other transaction details may also be presented at checkout, in machine-readable x402 payment requirements, or in a separately executed order form or Enterprise agreement. Where a separately executed written agreement expressly conflicts with this standard license scope, that signed agreement controls for that customer and use case.

10. Licensing questions

If a proposed use sits between normal individual reference and persistent software/model use, contact PostOpz before ingestion or deployment. Email hello@postopz.com.