Skip to content

Latest commit

 

History

History
85 lines (52 loc) · 2.7 KB

File metadata and controls

85 lines (52 loc) · 2.7 KB

Licensing

AgentAssert Type-C is released under the MIT License. Commercial support and enterprise licensing are available.


MIT License Summary

  • Free for any use — personal, academic, commercial, internal tools
  • Modify and distribute — fork, customize, embed in your projects
  • Private use — run the proxy in your infrastructure
  • No copyleft — your agent code that communicates with Type-C is not affected

The full license text is in the repository root: LICENSE.


What You Can Do

Use Case Allowed?
Run the proxy locally for personal coding ✅ Yes
Run the proxy in your company's infrastructure ✅ Yes
Embed the SDK in your Python application ✅ Yes
Modify the source and use internally ✅ Yes
Distribute modified versions ✅ Yes (include MIT notice)
Sell a SaaS product that includes Type-C ✅ Yes
Use the contract DSL for your own contracts ✅ Yes

Commercial Support

For organizations that need:

  • Priority bug fixes and security patches
  • SLA-backed support with response time guarantees
  • Custom contract development for your specific agent workflows
  • Enterprise deployment consulting (multi-tenant proxy, Kubernetes, monitoring)
  • Integration assistance with your existing agent infrastructure

Contact: varun.pratap.bhardwaj@gmail.com


Dual Licensing (Enterprise)

For organizations that need terms beyond the MIT License:

  • Custom licensing for closed-source distribution without MIT attribution
  • Indemnification and warranty provisions
  • Enterprise-wide deployment agreements
  • Custom SLAs and support tiers

FAQ

Can I use Type-C in my closed-source commercial product?

Yes. MIT allows this without restriction. You don't need to open-source your product.

Do I need to include the MIT license notice?

If you redistribute Type-C source or binaries, include the MIT notice. If you're just running the proxy internally, no attribution needed.

Does MIT infect my agent code?

No. Your agent communicates with Type-C over HTTP or via the Python SDK wrapper — this is normal API usage, not a derivative work. MIT has no copyleft provisions.

Can I fork and rebrand Type-C?

Yes, under MIT terms. Include the original copyright notice.

What if I need different terms?

Contact varun.pratap.bhardwaj@gmail.com for custom enterprise licensing.


Contributing

Contributions are welcome under the MIT License. See GitHub: qualixar/agentassert-typec.

By contributing, you agree that your contributions will be licensed under MIT.