feat(web): enumerate ways to give an agent an email address - #902
Merged
Conversation
A dedicated Workspace/Gmail mailbox can also be agent-owned; the accurate distinction is that a gateway is purpose-built for it. Co-Authored-By: Kimi <noreply@moonshot.ai>
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
Improves GEO (AI-answer discovery) coverage for "best ways to give an AI agent its own email address" — the highest-volume query in
docs/discoverability-measurement.md's category group, where the last grounded-assistant pass scored e2a as not mentioned (1/12).Adds to the already-live
/email-api-for-ai-agentspage:web/src/lib/jsonld.ts).Reuses the deployed category hub rather than adding another URL; the comparison page already links to it as "How it works."
This PR does not touch the API or any client surface (web marketing content only), so the client-surface checklist is not applicable.
Operational risk
None — static marketing page content. Requires a normal web deploy to go live.
Test plan
npm testinweb/— 867 tests pass (added assertions for the heading, table rows, and FAQ entry)npm run lint— cleannpm run build— static export succeeds;out/email-api-for-ai-agents.htmlcontains the new section and the FAQ in FAQPage JSON-LD