Monetization

Monetization: From Scrapers to Customers

Once Identity is established, we can talk business. IMAGXP supports three primary monetization models, allowing you to turn AI traffic into a revenue stream.

Step C: The Rules (The Visa Check)

Now that we know the Identity is real (Step B), we check the Publisher's Terms:

  • If Policy = "No Training": Publisher says "You are Real, but I don't assume training." -> BLOCK.
  • If Policy = "Pay Me": Publisher says "You are Real. Where is the money?" -> CHECK WALLET.
  • If Policy = "Show Ads": Publisher says "You are Real. Did you show my ads?" -> CHECK PROOF.

Step D: The Reward (HQ Content)

  • Action: All checks passed.
  • Result: The Publisher serves the High-Quality JSON (Clean text, perfect structure).
  • Why: This is better data than scraping HTML. The Agent gets better intelligence; the Publisher gets paid/attribution.

Mechanism 1: Direct Micro-Payments (The "Toll")

The Agent pays per-request access fees directly to the Publisher.

  • Implementation: The Publisher sets requiresPayment: true in their configuration.
  • Flow:
    1. Agent requests /article/123.
    2. Publisher responds 402 Payment Required.
    3. Agent sends a second request with a Payment-Credential (JWT).
    4. Publisher verifies the JWT locally (using the Payment Provider's Public Key) and serves the content.
  • Use Case: Real-time stock data, premium news, API access.

Log View: The Success Story (Payer)

Time
Module
Message
16:10:05.200
IDENTITY
✅ PASSED. DNS Binding Verified (grok-bot.x.ai).
16:10:05.201
POLICY
📜 Checking Permissions for grok-bot.x.ai...
16:10:05.201
CONFIG
⚠️ Rule Match: requiresPayment = true
16:10:05.202
POLICY
⛔ DENIED. Reason: PAYMENT_REQUIRED.
16:10:05.450
SYSTEM
🔄 Agent Retrying with "Payment-Credential" (Broker Visa)...
16:10:05.455
BROKER
🔐 Verifying Broker Credential (Issuer: broker.imagxp.org)...
16:10:05.460
BROKER
💰 Valid Payment Token from broker.imagxp.org for amount 0.001 USD.
16:10:05.461
POLICY
✅ PASSED. Requirements Met.
16:10:05.462
ACCESS
🔓 GRANTED. Unlocking HQ Content.

Log View: The Failure Story (Freeloader)

Time
Module
Message
16:15:12.100
IDENTITY
✅ PASSED. DNS Binding Verified (random-scraper.com).
16:15:12.101
POLICY
📜 Checking Permissions for random-scraper.com...
16:15:12.102
CONFIG
⚠️ Rule Match: requiresPayment = true
16:15:12.103
POLICY
🔍 Checking for Payment Credentials... NONE.
16:15:12.104
POLICY
⛔ DENIED. Reason: PAYMENT_REQUIRED: Credential check failed.
16:15:12.105
ACCESS
⛔ BLOCKED. Agent did not pay.

Mechanism 2: The "Bond" & Broker (Optional)

Handling millions of $0.001 transactions individually is inefficient. The Broker Model solves this.

  1. The Bond: An AI Company (e.g. Perplexity) deposits a large sum (e.g. $100k) into the Broker Smart Contract.
  2. The Visa: The Broker issues a signed "Visa" (JWT) to the Agent, backed by that Bond.
  3. The Visit: The Agent shows this Visa to Publishers.
  4. Settlement: Publishers verify the Visa locally (Zero-Latency). The Broker aggregates the logs from Publishers and settles the payments monthly (like Spotify).

Note: The Broker is OPTIONAL. You can run purely P2P (Mechanism 1) if you prefer.

Mechanism 3: Ad-Supported Access

Agents can gain access by proving they displayed your Ads to their users (e.g., in their AI citation).

  • Flow:
    1. Agent displays your Ad to the user.
    2. Ad Network issues a "Proof of View" Token (JWT).
    3. Agent attaches this Token to the request header x-imagxp-proof.
    4. Publisher validates the Token signatures and grants access.

FAQ: Monetization

  • Q: Do I need a Crypto Wallet?
    • A: Yes, if you want direct P2P settlement. For Broker settlement, many Brokers offer fiat (USD) payouts.
  • Q: What if an Agent refuses to pay?
    • A: The SDK blocks them automatically (402 Payment Required). They receive no data.
  • Q: Why the Broker?
    • A: OpenAI doesn't want to send 1,000 checks for $0.01. You don't want to chase them. The Broker acts as the clearing house, similar to Visa/Mastercard.