Add Agent Commerce Desk Open Frame

[chico10117]

Open Frames Bounty Submission

Adds Agent Commerce Desk to the compatible Example Frames list.

Frame Details

• Frame URL: https://x402-wallet-readiness-service.vercel.app/open-frame
• Source: https://github.com/chico10117/basepay-readiness-service
• Open Frames metadata: of:accepts:xmtp -> vNext
• Protocols: XMTP, Farcaster, anonymous fallback
• Description: Base USDC wallet-readiness and x402 service discovery frame.
• Bounty contact / payout wallet: 0x820a7bf90d944bb26bfD9b62Ab172Fc3A0829cB9

Verification

• Live frame returns of:version, of:accepts:xmtp, of:image, of:post_url, and fc:frame tags.
• POST refresh returns a valid frame response.
• Frame image renders at https://x402-wallet-readiness-service.vercel.app/open-frame.svg.
• Source commit with the frame endpoint is published: chico10117/basepay-readiness-service@2d5f376

Bounty Checklist

• Make Frame interoperable with Open Frames standard
• Add Frame to Example Frames section in this repo via PR
• Send Frame via DM to hi.xmtp.eth through a compatible XMTP app

[vercel]

@chico10117 is attempting to deploy a commit to the open-frames Team on Vercel.

A member of the Team first needs to authorize it.

[chico10117]

Validation note: the Vercel check on this PR is blocked by open-frames team deployment authorization, not by this README-only change.

Live frame validation is passing now:

• Frame URL: https://x402-wallet-readiness-service.vercel.app/open-frame
• Image: https://x402-wallet-readiness-service.vercel.app/open-frame.svg
• Required tags present: of:version, of:accepts:xmtp, of:image, of:post_url, fc:frame
• POST refresh endpoint returns a frame response
• Source commit: chico10117/basepay-readiness-service@2d5f376

I will complete the hi.xmtp.eth DM step from a compatible XMTP app as the remaining bounty requirement.

[chico10117]

XMTP DM step is now complete.

I sent the frame link to hi.xmtp.eth via XMTP from the connected target-wallet identity using the local XMTP browser helper.

Sent message:

Open Frames bounty submission: https://x402-wallet-readiness-service.vercel.app/open-frame

PR: https://github.com/open-frames/awesome-open-frames/pull/89

Payout/contact wallet: 0x820a7bf90d944bb26bfD9b62Ab172Fc3A0829cB9

The helper reported Sent. Message id: (no id returned) at 2026-05-24T20:09:55Z.

[chico10117]

Follow-up for bounty review: the frame and DM requirements appear complete from my side, and the only failing check is the Vercel team authorization gate for the open-frames org deployment.

Evidence:

• Live frame: https://x402-wallet-readiness-service.vercel.app/open-frame
• Required Open Frames/XMTP metadata is present: of:version, of:accepts:xmtp, of:image, of:post_url, plus Farcaster compatibility tags.
• XMTP DM proof was posted here: Add Agent Commerce Desk Open Frame #89 (comment)
• Current Vercel check says: Authorization required to deploy for the open-frames team, so this looks maintainer-side rather than a frame/rendering failure.

Can a maintainer authorize/re-run the Vercel check or confirm that the org deployment check can be ignored for this README/frame-listing bounty review?

Base USDC payout/contact wallet if accepted:
0x820a7bf90d944bb26bfD9b62Ab172Fc3A0829cB9