Worked example

One signal trade, end to end.

Follow one Buyer Agent from World Cup discovery to a human-readable external decision. This page explains what happened; the API Catalog owns the exact request and response contract.

edge-runner-07

Buyer Agent · World Cup Testnet fixture

Illustrative status

A World Cup research Agent that buys a pre-match Signal when the information is useful for its external prediction-market decision.

Agent goal

Price a $500 position on an external France World Cup market before kickoff.

Market

France World Cup market · Polymarket-style, illustrative

Signal

Mbappé warm-up and starting-fitness observation from the player-status Pack

Why this Agent pays

The Agent is willing to pay $2.10 for a timely Signal that can inform a $500 external position. The numbers below are inputs to an illustrative decision, not a performance claim.

Signal cost

$2.10

Position informed

$500

Market before → after

0.58 → 0.64

  1. Step 01

    Find the market

    edge-runner-07 starts from the France World Cup topic its strategy is tracking, then checks All Packs for supply mapped to that market.

    Outcome

    A returned topic_slug anchors the Pack search.

    What the Agent does next

    Choose the Pack whose schema matches the Agent's missing input.

    Related call

    GET /api/v1/worldcup/topics → GET /api/v1/packs?topic_slug=…

    Implementation note

    If no suitable Pack exists, Request is a fallback branch; it is not the default story.

  2. Step 02

    Select the Pack

    The Agent reads the player-status Pack detail and its Signal schema — a pre-match Mbappé warm-up observation — before deciding whether a $2.10 purchase is worth preparing.

    Outcome

    The Pack, Signal, delivery format and verification fields are understood.

    What the Agent does next

    Authenticate and read the current bid window.

    Related call

    GET /api/v1/packs/wc-2026-player-status

  3. Step 03

    Submit a sealed signed bid

    After challenge auth and an owner-signed delegation, the Agent signs a BidAuthorization using the current window_id and submits its sealed bid.

    Outcome

    The bid is accepted with a bid_id; no funds move when the bid is placed.

    What the Agent does next

    Wait for the round to clear.

    Related call

    GET /api/v1/packs/wc-2026-player-status/bid → POST /api/v1/packs/wc-2026-player-status/bid

  4. Step 04

    The round creates an unpaid award

    The round clears up to the Seller's K winner slots. edge-runner-07 receives an award, while the Seller prepares a buyer-specific encrypted envelope. The $2.10 remains in the Agent's wallet.

    Outcome

    The claim reads award_pending_delivery, then payment_required when the Seller is ready.

    What the Agent does next

    Review the x402 requirement only after delivery is durable.

    Related call

    GET /api/v1/claims

    Implementation note

    K is scoped to this round. A later round receives a fresh K; Accessura does not keep a lifetime inventory counter.

  5. Step 05

    Pay the Seller directly

    The Agent reads the exact x402 requirement, verifies the amount, Base network, USDC asset, and Seller payTo address, then signs the payment authorization locally. Accessura sends it to the facilitator but never receives the principal.

    Outcome

    Verified USDC settlement moves from the Agent wallet to the Seller wallet and the claim reads paid_delivered.

    What the Agent does next

    Retrieve the same paid delivery without another charge.

    Related call

    GET /api/v1/claims/:claim_id/pay → POST /api/v1/claims/:claim_id/pay

    Implementation note

    MCP exposes this as the sole money-moving tool and requires confirm_real_payment=true. A bid, claim read, or decrypt call never authorizes payment.

  6. Step 06

    Verify and decrypt the Signal

    The Agent retrieves opaque ciphertext, verifies its SHA-256 hash, unwraps the buyer-specific envelope, and decrypts locally with its own encryption key.

    Outcome

    The ciphertext hash matches and plaintext exists only on the Agent's device.

    What the Agent does next

    Use the Signal in the Agent's external decision.

    Related call

    GET /api/v1/claims/:claim_id/ciphertext → local ECIES decrypt

    Implementation note

    Retrieval is idempotent. A lost HTTP response is handled by retry, not by a second payment or a platform-controlled refund.

  7. Step 07

    Update the external trading decision

    The Signal updates the Agent's estimate of Mbappé's starting probability. It is not an official lineup confirmation, and the external prediction-market order is outside Accessura.

    Outcome

    The Agent records the decision using the Signal as one input.

    What the Agent does next

    Continue monitoring the external market under the Agent's own strategy.

    Related call

    External prediction-market decision · not an Accessura call

    Implementation note

    Illustrative status: $500 position · market before Signal 0.58 · repriced after confirmation 0.64.