Meta Muse submission checklist
Field-by-field preparation for the Muse Connector Platform form. Values in italics are decisions for Snappy to confirm.
Step 1 — Overview
| Form field | Value |
|---|---|
| Connector name | Snappy Marketplace |
| Company | Snappy (snappy.com) |
| Product website | https://www.snappy.com |
| Example prompts | "Find me a coffee tumbler under $50 on Snappy" · "Add the black 30oz tumbler and the noise-cancelling headphones to a Snappy order and ship them to my office in New York" · "Where is my Snappy order?" · "Text me the receipt for my last Snappy purchase" · "My Snappy order arrived damaged, what can I do?" |
| Connector icon | 512×512 PNG from Snappy brand assets (marketing to supply) |
| Accepts payments | Yes (hosted Stripe Checkout) |
| Your name / work email | Dvir Cohen, dvir@snappy.com |
| Support email or URL | support@snappy.com · https://www.snappy.com/contact |
| Privacy policy URL | https://www.snappy.com/privacy |
| Terms of service URL | https://www.snappy.com/terms |
Step 2 — Technical specs
| Form field | Value |
|---|---|
| Connection type | Either. Raw API: https://agents.snappy.com with OpenAPI https://agents.snappy.com/openapi.json. Existing MCP: https://agents.snappy.com/mcp. |
| Documentation | https://agents.snappy.com/docs |
| Authentication | OAuth 2.0 with PKCE (dynamic client registration supported). Discovery: /.well-known/oauth-authorization-server. |
| Access requirements | Any user with an email address; purchases require orders:write; shipping to the United States only (/v1/countries). |
| Test vs production | Sandbox https://sandbox.agents.snappy.com (Stripe test mode, Snappy testing company, OTP shown on page) |
Step 3 — Business verification & data processing
- Organization: Snappy App Inc. — legal entity and evidence to be attached by finance.
- Designated developer contact: Dvir Cohen.
- Data processing questionnaire: answers in Security & data.
Tool annotation (5.6)
Provided in documentation form on Tool classification and machine-readably via x-tool-class in the OpenAPI document and MCP annotations.
Test account (5.5)
- Sandbox sign-in email: to be created on the sandbox and shared in the form.
- How to test checkout without real charges: Testing & sandbox.
- Representative data: the Snappy testing company catalog.
Transaction requirements (4.7)
Every quote and order response returns seller (Snappy), full price with currency and breakdown, non-recurring nature, receipts on request, and support routes on errors. States are distinguished: quoted → pending_payment → paid → confirmed, plus failed/refunded/expired/cancelled.
Task completion (1.1)
Search, availability, pricing, authorization (OAuth), cart checkout (Stripe), confirmation (SSE/poll/callback), status checks (/v1/orders/{id}), cancellation and refunds (/cancel), and post-fulfilment support (returns, damaged, not received via /support-requests, resolved with refunds by operators) are all supported.