Back to Home

Terms of Service

Effective Date: January 2026

1. An Open Standard, Not a Platform

The IMAGXP Protocol ("IMAGXP") is an open-source, decentralized communication standard (Application Layer 7) built on HTTP and ECDSA Cryptography.

  • No Central Authority: We do not operate a central "platform." You install the open-source SDK on your own servers.
  • Edge-to-Edge: Negotiations happen directly between an AI Agent and a Publisher. IMAGXP core developers cannot intervene, block, or force a transaction.
  • Open Source SDK: The `@imagxp/protocol` SDK is provided under the MIT License. It is your responsibility to test and implement it correctly within your architecture.

2. The "Broker" SaaS Layer

While the core Protocol is free and open-source, the optional "IMAGXP Broker" used for routing $0.01 micro-payments is a proprietary SaaS product. If you (Publisher or Agent) opt-in to use Broker monetization URLs, you agree that the Broker handles your payment pool (Bonds) and issues verifiable cryptographic Visas (JWTs). The Broker charges processing fees in exchange for aggregating these micro-transactions.

3. Legal Liability & Dispute Resolution (The Snapshot Defense)

By placing an imagxp-agent.json file on your domain, you publicly bind your Private Key to your corporate identity.

  • Non-Repudiation: You agree that any HTTP Request bearing a valid ECDSA signature matching your Public Key is legally equivalent to an action taken by you, subject to applicable contract or dispute laws.
  • Sovereign Disputes: If a Publisher accuses an Agent of violating access policies, or an Agent accuses a Publisher of serving "Spam" data, IMAGXP does not act as a judge. Publishers host their Signed Logs. Agents host their Signed Feedback. You use these cryptographic proofs to resolve disputes directly or in a court of law.

4. Key Management Responsibility

You are 100% responsible for the security of your Private Key.

If your Private Key is leaked because you committed your `.env` file to a public repository, anyone can impersonate your Agent and drain your available funds. The protocol cannot "freeze" an identity instantly across the global internet. You must rotate your keys and update your public `imagxp-agent.json` file immediately.

5. "As Is" Mathematical Proof

IMAGXP provides cryptographic certainty that a specific key requested a specific URL at a specific time. It does not provide physical force.The protocol relies on "The Threat of Proof." If an Agent signs an agreement not to train on data, and trains anyway, the Protocol cannot "delete the data" from their servers. It merely provides the irrefutable court proof that they stole it.