feat(sell): add OpenAPI contact email for x402scan discovery - #695
Merged
Conversation
HananINouman
marked this pull request as ready for review
July 3, 2026 13:46
OisinKyne
approved these changes
Jul 3, 2026
Let operators set contactEmail on the storefront profile and publish it as info.contact.email in /openapi.json while keeping the services catalog envelope unchanged. Co-authored-by: Cursor <cursoragent@cursor.com>
OisinKyne
force-pushed
the
feat/sell-openapi-contact-email
branch
from
July 3, 2026 14:10
a71dd8e to
9c20459
Compare
OisinKyne
enabled auto-merge (rebase)
July 3, 2026 14:11
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
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.
Let operators set contactEmail on the storefront profile and publish it as info.contact.email in /openapi.json while keeping the services catalog envelope unchanged.
Summary
What changed:
Why it matters:
Risk level:
Commit under test:
Base branch:
Scope
Validation
CI checks:
Unit tests:
Integration tests:
Flow tests:
Release smoke:
Live Chain Evidence
Do not include private keys, seed phrases, passwords, hostnames, personal paths, or raw bearer tokens.
Network:
RPC/provider:
Facilitator:
Contracts and tokens:
Wallet roles:
Balances:
Transaction receipts:
Runtime Evidence
QA environment:
Images:
Kubernetes / stack:
Model and routing:
Artifacts and logs:
Demo readiness:
Review Notes
Known gaps:
Follow-ups:
Reviewer focus: