Alex Horsey

Alex Horsey | Knowledge & AI Portfolio

For Pinterest

Resume

Open PDF ↗
← All work

Coinbase Wallet

Buy and trade on Base

You can buy and trade assets on Base using your linked payment methods, Apple Pay, or the assets you hold in your wallet.

Review your Coinbase Wallet activity history on the Wallet tab.

Buy assets on Base

If you have a Coinbase account connected to Base, you can use a debit card or bank account linked to that account to buy crypto in the Coinbase Wallet app. If you don’t have a connected Coinbase account, you can buy with a debit card or Apple Pay.

To buy assets on Base:

  1. Select the Wallet tab and choose Buy.
  2. Select a payment method.
  3. Select an asset and enter an amount.
  4. Review the transaction and associated fees, if any.
  5. Swipe to confirm.

To connect your Coinbase account:

  1. Open the Home tab.
  2. Select your profile photo to open the sidebar menu.
  3. Select Settings and choose Connect to Coinbase.
  4. Select Buy or transfer with Coinbase.
  5. Review the permissions and select Authorize.

Trade assets on Base

Swap an asset for another in one transaction by trading on Base.

To trade assets on Base:

  1. Select the Wallet tab and choose Trade.
  2. Select the asset you’d like to trade out and enter an amount.
  3. Select the asset you’d like to receive.
  4. Review the transaction and associated fees, if any.
  5. If you’d like to change the slippage tolerance, select Fees and choose the gear icon.
  6. Swipe to confirm.

Slippage tolerance

Slippage tolerance is the maximum price difference you’re willing to accept between the expected price of a trade and the actual price at which the trade is executed. This can happen due to market volatility or liquidity.

← All work

Base

Creator Coins on Base

A Creator Coin is an ERC-20 token linked to your Base app profile and Zora, allowing you to earn from trading volume.

Activate your Creator Coin

If you don’t already have a Creator Coin on Base or Zora, you can create one on Base.

To create a new Creator Coin:

  1. Select your profile photo to open the sidebar menu and choose View profile.
  2. Select Activate your creator coin now and choose Activate creator coin.
  3. Enter your coin’s permanent ticker name, edit image, and select Create creator coin.
  4. If you’d like, select Share coin to share it in the social feed.

You can also link your Zora account and existing Creator Coin. Claims and earnings will take place on Zora.

To link your Zora account and Creator Coin:

  1. Select your profile photo to open the sidebar menu and choose View profile.
  2. Select Activate your creator coin now and choose Link with Zora.
  3. Follow the prompts to link your Zora account and existing Creator Coin to Base.

Showcase another token

You can link any token (not just your Creator Coin) to your profile, to drive trading volume to it as other users trade your coined content.

To showcase another token on your profile:

  1. Select your profile photo to open the sidebar menu and choose View profile.
  2. Select Edit profile.
  3. Under Linked coin, select the coin you’d like to showcase.
← All work

Bandcamp · Selling merch

A fan opened a dispute against a merch order. What should I do?

Since most payments for physical orders are processed by PayPal, any merch sales made from your Bandcamp page are covered under their Buyer Protection policy. Fans have the ability to dispute any purchases they don’t receive within 180 days of purchase directly via PayPal. Once a dispute or claim has been filed against an order, it will not be possible to issue a refund through Bandcamp until the dispute or claim has been resolved.

In the event of a dispute, you’ll need to provide valid proof of shipment for that order within a few days, or PayPal may refund the order in full. Valid proof of shipment can be in the form of:

  • A photo of the processed package showing the buyer’s address and courier’s stamp (recommended)
  • A tracking number
  • A photo or screenshot of a detailed receipt from the courier
  • All of the above

Since Bandcamp is the seller of record for physical sales after June 2024, we will handle disputes and claims on your behalf. Any proof you send us for those orders will be passed on to PayPal, but ultimately, it’s up to them to review the case and issue a refund if there isn’t sufficient proof that the order has been fulfilled.

For any merch sales made under Standard Payments (prior to June 2024), disputes opened against payments that went directly to you will appear in your PayPal account’s Resolution Center.

For more information, you can read PayPal’s guide.

H&R Block · Knowledge base rewrite

Knowledge rewrite automation

A multi-agent pipeline powering a 500-article knowledge audit rewrite.

500 support articles needed to be rewritten to new structure and style standards, then migrated, ahead of tax season.

500articles rewritten and migrated
~12 a daydown from a few hours each
3 monthscut from the timeline, finishing ahead of tax season

How it works

An orchestration agent in Microsoft Copilot Studio moves each article through four specialist agents and tracks where every article is.

  1. 1

    Retrieve

    Agent

    Pulls the source article and the related content it depends on.

  2. 2

    Categorize

    Agent

    Assigns the article its place in the new taxonomy and fills in its metadata.

  3. 3

    Redraft

    Agent

    Rewrites the article against the team's structure, style, and formatting standards.

  4. 4

    Agentic review

    Agent · fix loop

    Checks the draft against the same standards. A draft that fails goes back to Redraft with a specific list of fixes, and loops until it passes.

    ↺ Fail → back to stage 3 with the fix list

  5. 5

    Ready for migration

    Output

    Articles that pass review move to the new knowledge base.

The standards the agents write and review against are the same taxonomy, metadata, and article-structure rules that make the content retrievable by search and AI tools.

TicketPill · Help center automation

Self-healing help center

A pipeline that flags articles the moment a release makes them stale, then drafts the edit.

TicketPill is an event ticketing platform for independent producers. I built it and run it alone, from product and code to payments and support. Documentation is a small part of that job, so it has to keep up with the product without me re-reading every article after every release.

The problem

I ship several times a day. Nobody re-reads 19 help articles after each merge, so buyers and producers end up following steps that no longer match the screen.

How it works

Each stage runs only if the one before it passes, cheapest first. Most pushes stop at stage 2 and cost nothing.

  1. 1

    Capture the release

    GitHub Action

    On push to main, send the commit message, PR title, changed file paths, and a capped diff to a webhook. No model call.

  2. 2

    Path filter

    Deterministic · $0

    If every changed file is a lockfile, test, stylesheet, image, doc, or CI config, skip it.

  3. 3

    Relevance gate

    Haiku

    Does a buyer or producer see or do anything differently? Returns yes or no, plus a one-line summary in user terms.

  4. 4

    Recommend

    Sonnet · hybrid retrieval

    Names the article, the section, and what changed, using vector and keyword search over the help center. No copy.

  5. 5

    Review queue

    Human

    One item per article and section. A second release touching the same section adds evidence to the open item instead of a new row.

  6. 6

    Draft this for me

    Opus · on click

    Revises the live article and saves a CMS draft. The published page stays up until I publish.

After “Draft this for me”

Facts the code can't confirm become placeholders instead of guesses, and a style linter attaches its findings to the draft.

CMS draftsaved as draft, live page untouched
## Paying for your order
Pick a card, Apple Pay or Google Pay. If you pick a wallet, the
button changes to **Continue with Apple Pay** (or Google Pay) and
your phone or browser asks you to confirm.

If the wallet option is missing, [NEEDS: which browsers/devices
hide the wallet option].

Every review decision feeds the next run:

Reviewer doesSystem storesUsed next time by
Dismisses an itemThe reason (not user-facing, already covered, wrong article, not worth it)Recommender, as “don't repeat this” examples
Overrides a skipped release“Changes like this should be documented”Gate, as past mistakes to avoid
Corrects a draftThe correction, embeddedDrafting, retrieved by topic similarity

Every learned change is logged and can be reverted with one click.

What I learned

The first version drafted a new article on every relevant merge. Most drafts got rewritten or thrown away, and reviewing AI prose took longer than writing it myself. So v2 only says which article and section changed and why, and saves the stronger model for when I ask for a draft.

v1 · Draft on every merge

  • Most drafts rewritten or discarded
  • Review took longer than writing

v2 · Recommend, draft on request

  • Short queue: article, section, what changed
  • Duplicates collapse into one item