# PhotoMatchFun

PhotoMatchFun creates personalized physical photo matching card games. This file describes the supported programmatic ordering surface for software agents.

## Integration documentation

- Overview: https://photomatchfun.com/integrations
- MCP guide: https://photomatchfun.com/integrations/mcp
- x402 guide: https://photomatchfun.com/integrations/x402
- Live commerce manifest: https://photomatchfun.com/api/agent/commerce
- Remote MCP endpoint: https://photomatchfun.com/api/mcp
- MCP transport: Streamable HTTP

## MCP ordering tools

Use the tools in this exact order:

1. list_products
2. get_product_configuration
3. create_asset_uploads
4. Upload one complete print-ready image to every returned upload URL.
5. create_order_intent
6. Pay the returned paymentUrl with an x402 v2 client.
7. get_order_status until the order is fulfilled or requires operator review.

The MCP resource photomatchfun://commerce/guide is the authoritative detailed workflow. The resource photomatchfun://commerce/x402 contains the current public payment configuration.

## Required buyer behavior

- Re-read the product configuration for every order. Price, dimensions, artwork count, and availability are server-issued.
- Show the customer the product, total, terms, privacy notice, delivery details, and artwork before creating the order intent.
- Upload only the exact count of complete print-ready card-front canvases requested by the product configuration.
- Keep upload, claim, and status capabilities private and scoped to the active order.
- Keep wallet private keys and seed phrases inside a trusted wallet runtime. PhotoMatchFun never requests or accepts them.
- On an unknown payment outcome, retry the same signed x402 payment instead of creating a second authorization.
- Use a stable opaque idempotency key only for an unchanged order payload.