Obol Settlement command center
connecting

Arc Testnet settlement layer

Agent reads. Creator gets paid. Arc proves it.

Obol is a live settlement console for machine readers: the agent scores paid sources, Circle moves USDC, creators receive revenue, and Arc returns the txHash.

loading live creator payments...
Problem AI reads do not pay
Resolution Per-read USDC settlement
Proof Circle id + Arc txHash
01 Agent chooses source 02 Circle signs transfer 03 Arc returns proof
12h window usage runner synced

background buyers create real Arc receipts over time

market depth 100 paid sources

priced content for agent-side relevance scoring

creator side wallet payouts live

each receipt points to a creator revenue wallet

Live Arc proof

Waiting for a completed receipt

Run the paying agent to produce a Circle transaction and Arc Testnet tx hash.

checking
Intent Agent needs a paid source

Budgeted content request

Decision Best source selected

Low relevance skipped

Settlement $0.0000 USDC

Circle Wallets / Arc

Receipt waiting

txHash proves payment

01

Visible agency

The agent logs each buy, reuse, and skip with a reason, so spending is accountable instead of black-box automation.

02

Per-read creator revenue

Every paid read becomes a receipt tied to a creator, article, amount, Circle transaction id, and Arc testnet hash.

03

HTTP-native paywall

External agents can hit an x402 endpoint, get a 402 challenge, pay, and retry for the full content.

Autonomous paying researcher

Agent Console

Ask a question with a budget. Watch the agent buy only what it needs, preserve money when coverage is enough, and reuse cached reads for free.

O

Ready to authorize a paid read.

Run a query to see decision, settlement, and proof in one flow.

Paywalled source market

Marketplace

Public previews stay readable. Full content requires an Obol unlock, agent purchase, or x402 payment proof.

Creator revenue console

Creator Studio

List an article, price a read, then watch earnings update when agents pay to consume it.

Publish paywalled source

    Select a creator to see earnings.

    Machine-payable content

    x402 flow

    External agents can request a source, receive a 402 Payment Required challenge, then retry with a payment proof to unlock content.

    Step 1

    Request locked content

    {
  "status": "waiting",
  "next": "click Get 402 challenge",
  "expected": "402 Payment Required + accepted USDC rail"
}
    Step 2

    Retry with X-Payment

    {
  "status": "waiting",
  "next": "submit X-Payment proof",
  "result": "full article + creator receipt"
}

    Proof of use

    Traction ledger

    Confirmed reads, creator payments, and Arc tx hashes in one ledger.

    Settlement readiness

    Arc / Circle status

    checking
    0

    agent runs

    0

    live receipts

    $0.0000

    USDC paid

    $0.0000

    saved by reuse

    Creator economist tests per-read revenue

    demo persona

    Skeptical publisher checks locked previews

    demo persona

    Budget researcher runs paid queries

    demo persona

    API tool builder tries x402 unlocks

    demo persona

    Security auditor checks cache boundaries

    demo persona

    Evaluation activity

    Five demo personas exercised the product

    simulated, labeled
    Creator economist

    Finding: earnings ledger is the clearest creator-facing proof.

    Skeptical publisher

    Finding: locked previews plus receipts make AI access legible.

    Budget researcher

    Finding: buy/skip log proves the agent stopped spending.

    API tool builder

    Finding: x402 gives builders a copyable machine-payable surface.

    Security auditor

    Finding: cache boundaries protect creator revenue from replay.

    Recent agent runs
    Payment ledger Open any receipt proof