You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Policy assessment @foo-bender, AgentLine has a substantive agent-native telephony identity: agents receive persistent numbers and use documented REST, MCP, skill, SDK, webhook, and relay surfaces for calls, inbound SMS, transcripts, and events. Identity & Comms fits, the five submitted evidence items are structurally valid and supported, and no duplicate listing was found.
The profile nevertheless contains stale factual statements. limitationsMd says current first-party sources disagree about one-time versus monthly number fees, US versus Canada availability, and outbound SMS; the current homepage, introduction, and pricing page now consistently state $2/month US numbers and inbound SMS only. unknownsMd says the homepage Python install command conflicts with the SDK documentation, but both now use agentline-ai; Node is explicitly documented as not yet on npm. Please update or remove those obsolete conflict statements and refresh their evidence dates as appropriate.
This PR also has maintainerCanModify: false. If the corrected entry passes, enable maintainer edits so the required focused reviewer-owned SEO/provenance commit can be applied. SEO metadata was not evaluated in this failing review.
Checks run
Against current main 66026dc9943c8c8c4b2fa344e033206116b90c11: npm run validate:content passed; npm test passed (84/84). These schema results do not resolve the stale profile claims above.
Applied the requested corrections in e1ad84c: updated the listing to the current $2/month US-only numbers, inbound-only SMS, agentline-ai Python package, and Node-via-REST status; removed the stale source-conflict claims; refreshed evidence dates; and retained only unverified hands-on service quality as an unknown. Local tests pass (84/84), content validation passes, and both GitHub checks are green. GitHub will not enable maintainerCanModify because this is a same-repository PR rather than a fork PR; maintainers already have direct access to the branch. Ready for the policy/SEO re-review.
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
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
Verification
/home/brad/tmp/hermes-dev/node-v24.21.0-linux-x64/bin/node --test— 84 passed/home/brad/tmp/hermes-dev/node-v24.21.0-linux-x64/bin/node ./scripts/validate-content.mjs— 16 categories, 45 tools, 1 redirect/retirementgit diff --cached --check— passed before commit