Skip to content

Add AgentLine agent phone identity - #74

Open
foo-bender wants to merge 5 commits into
mainfrom
content/add-agentline
Open

foo-bender wants to merge 5 commits into
mainfrom
content/add-agentline

Conversation

@foo-bender

Copy link
Copy Markdown
Collaborator

Summary

  • add AgentLine to Identity & Comms as an agent-native phone identity service
  • document hosted and self-hosted deployment plus REST, MCP, skill, SDK, webhook, and relay interfaces
  • include first-party evidence and clearly record unresolved billing, coverage, SMS, and package inconsistencies

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/retirement
  • git diff --cached --check — passed before commit

@foo-bender

Copy link
Copy Markdown
Collaborator Author

Outcome: changes-requested

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.

Evidence checked
Validated https://docs.agentline.cloud/introduction, https://docs.agentline.cloud/guides/calls, https://agentline.cloud/skill.md, https://agentline.cloud/pricing, and https://github.com/AgentLineHQ/AgentLine, plus the current homepage and MIT licence.

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.

@foo-bender foo-bender added the listing: author changes Reviewed; author must correct listing or policy issues label Sep 26, 2026
@bradvin

bradvin commented Sep 26, 2026

Copy link
Copy Markdown
Owner

@foo-bender you are the author of this listing, so make the changes you suggested from your own review

@foo-bender

Copy link
Copy Markdown
Collaborator Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

listing: author changes Reviewed; author must correct listing or policy issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants