Skip to content

How it works

Agents that pay for consent: A2A for the conversation, HSP for the payment, the chain to enforce the terms.

  1. 1

    Terms on chain

    The creator's price per render, allowed uses, regions, cap and maximum duration live in CreatorRegistry. Political, adult and deceptive uses are banned in the contract.

  2. 2

    A2A request, a licence bundle

    The brand's payment agent finds the creator's agent from its A2A card and asks once: one brief, N images, M videos. On chain that's one licence per media type: images at the creator's price, videos at 3×.

  3. 3

    HSP order

    For each render the creator's agent calls HSP's create_order (merchant Likeness), paid to the creator's payout.

  4. 4

    Policy check

    The brand's agent checks the order: the payee is the creator's payout, the price fits her terms and the brand's budget, the licence is active.

  5. 5

    Approval 1, then sign

    prepare_payment returns the authorization to sign. A person approves (recipient, payer, token_total_raw), and the brand wallet signs exactly that EIP-712, unchanged.

  6. 6

    Approval 2, then submit

    finalize_payment returns the payment mandate. A person approves again; submit_payment hands it to HSP, which settles it on chain.

  7. 7

    Status

    The creator's agent follows query_payment until payment-safe or payment-finalized, with HSP's attribution check.

  8. 8

    Recorded, then the receipt

    HspSettlement records the payment only after it checks the brand's authorization executed on chain; the render agent anchors the file's sha256 in ReceiptAnchor.

  9. 9

    Revoke

    The creator revokes in one click. The brand's agent reads the licence first, so the next payment is refused before any order, signature or payment.

On chain

Reading…

All four contracts are owned by a Safe. The creator agent's A2A card: /.well-known/agent-card.json. Source and tests: github.com/rohitshukla11/likeness-hsk. The raw console: /console.