feat: warn merchants to add contact email in openapi.json#967
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Surface info.contact.email throughout registration flows to nudge merchants toward adding their contact email. This unlocks their free Poncho merchant dashboard (usage analytics, endpoint health, shareable onboarding link). - Yellow warning during discovery when info.contact.email is missing - Post-registration CTA: green if email detected, yellow nudge if not - API responses include contactEmail or warning string - Docs and agent prompts updated with recommended field + examples - Bump @agentcash/discovery to 1.7.4 (reads contactEmail natively)
The ProbeResult card and its sibling sections (warnings, skipped endpoints) were not hidden after registration, causing duplicate "endpoint skipped" collapsibles and a cluttered layout. Added !activeBulkResult guard to the discovery/probe IIFE block so only the DiscoveryPanel success section shows post-registration.
- Moved the info.contact.email warning inside the ProbeResult card (after favicon warning, before endpoint list) to match mppscan - Added "Have your agent add it with this prompt" copy button using DiscoveryActions with a custom contact-email-specific prompt - "Learn more" now links to /discovery#merchant-dashboard (added anchor) - Contact email fix also included in the consolidated DiscoveryFixHint prompt via missingContactEmail prop
…efront links Replace the verbose two-variant dialog with clean action links. With contact email: API page + dashboard + share link. Without: API page + share link + nudge to add email.
onchainlu
force-pushed
the
merchant-contact-info
branch
from
3880e6b to
9c3ffaf
Compare
…tract feature list Replace "usage analytics, endpoint health, shareable onboarding link" with concrete tryponcho.com/m/ and /p/ URLs across discovery hub, integration spec, agent prompts, registration warnings, and API responses.
…ecommended not required Pages exist for every registered origin regardless of contact email. Reframe all messaging: /m is the API storefront, /p is health metrics. Remove "log in with same email" and conditional /p link logic.
…name consultation
- Redesign post-registration dialog as numbered 3-step checklist with completion tracking - Step 1: Review API page (checkmark on click) - Step 2: Test endpoints (checkmark on click) - Step 3: Email input or "Schedule a call" (if email already in openapi.json) - Add email column to ResourceOrigin (Prisma migration) - Persist contact email during registration from OpenAPI info.contact.email - Add updateEmail tRPC mutation for manual email submission from dialog
…izing, client-side email validation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
emailcolumn onResourceOrigin(Prisma migration). Populated during registration frominfo.contact.email, or manually via the dialog.updateEmailtRPC mutation — public endpoint for the dialog to save merchant email (with NOT_FOUND guard)contactEmailFields()helper — DRYs the conditional spread in both registration handlersinfo.contact.emailis missing, with copy-prompt CTA/m/and/p/pagesWhy
Merchants register and disappear — 80% are pseudonymous. The checklist guides them through setup, captures their email for follow-up, and offers a free consultation. Email is persisted to the origin for future contact and page customization.