[vpfun]

Summary

Evidence-backed listing for Agentel under Identity & Comms (agent-identity-communication).

Agentel is a hosted network layer for AI agents providing durable identity, profiles, relationships, public work, and evidence across runtimes. Classification: agent-native. Interfaces: REST API, TypeScript/JavaScript SDK (@agentel/sdk), and a hosted read-only MCP surface for eligible public network context.

Evidence (first-party)

The MCP page was rechecked on 2026-10-22 and documents six read-only tools, including list_missions. The other three live Agentel pages were last rechecked on 2026-10-10; SDK repository, npm, and Skill metadata were checked on 2026-10-09.

• https://agentel.tech/docs
• https://agentel.tech/connect
• https://github.com/agentel-tech/agentel-connection-kit
• https://agentel.tech/pricing
• https://agentel.tech/lab/mcp

Current docs identify Connection Kit @agentel/sdk@2.0.0 stable, matching npm latest, repository package metadata, and the official Skill manifest. The previous 1.2.1 pin and obsolete channel comparison have been removed. Package name is @agentel/sdk (not the unrelated npm package agentel).

Pricing is free under the repository definition: the usable $0 Free baseline is established, while a currently available paid upgrade is not. Free includes identity, profiles, connections, ordinary public work, reactions, Skill discovery, and Trust reads, with finite API, publishing, media, connection, and reading allowances. Published Builder ($9.99/month) and Agentel Premium ($19.99/month) tiers describe optional higher quotas and features. Pricing labels them available, but docs describe gated checkout and Connect/MCP say paid plans are not open; actual paid checkout and activation remain unverified. Creator remains planned and approval-required.

The hosted MCP requires a registered identity and separate read-only information credential. Its six tools read eligible public context under quotas; client interoperability has not been tested for this listing.

Boundaries

• No model hosting, managed agent runtime, or orchestration
• No arbitrary MCP server hosting or external-tool execution
• MCP does not publish, join Missions, purchase, or install Skills
• Verification remains documentation-reviewed; no registration, credentials, billing, or live MCP operations were exercised

Disclosure

I am affiliated with Agentel.

Validation

The 2026-10-22 follow-up corrects only the MCP tool count and its evidence access date. Historical test results below apply to the cited earlier commit. Current upstream content validation still requires maintainer approval.

Commit 9664c565ea428ddc007fe8c87d7e8b667c9a664b changes only tools/agentel.md. Local validation of the submitted file and existing submitter metadata passed. The equivalent PR result on current main 21adcb7a09fad26aa707f061d341e509b270db4d passed npm run validate:content -- --require-submitters (59 tools, 16 categories) and npm test (90/90) with Node 26.4.0 and Bash 5.3.0.

• Existing Identity & Comms category
• Required frontmatter and claim-level first-party evidence
• Repo-managed submitter attribution preserved
• Content validation and applicable tests passed locally

[github-actions]

I found missing media metadata and/or repo-managed submitter metadata that should be written back to the PR branch. I can't push directly to forked PR branches, but you can generate the same changes locally with:

git fetch 'https://github.com/bradvin/agentfirst.directory.git' '755fb203681550170c5bb80014318322d80fe6b4'
git worktree add --detach '../agentfirst-base-84' FETCH_HEAD
npm run sync:tool-submitters -- --base-root-dir '../agentfirst-base-84' --submitted-by 'vpfun' --slug 'agentel'
npm run enrich:tool-assets -- --write --slug 'agentel'
git worktree remove '../agentfirst-base-84'

Then commit the updated files to this PR branch.

[foo-bender]

Outcome: evidence-requested

Policy assessment

@vpfun Agentel otherwise clears the inclusion test: agents are the core participants, and the documented machine-first registration, persistent identity, authenticated profiles and relationships, public work, and trust-evidence reads support the agent-native classification and Identity & Comms category. The REST/SDK interfaces, hosted deployment, boundary from the operator's runtime, and stated limitations are supportable. The GitHub URL is a substantive implementation repository for the official Connection Kit rather than a README-only stub.

The evidence record is not yet materially complete for pricing. The profile sets pricing: "free", links a pricing page, and states that the free baseline is active while paid checkout is activation-gated, but no evidenceSources item makes that claim. Please add a claim-level first-party evidence item for the exact pricing URL, with sourceType: "official-pricing", covering the currently available free tier and the current availability state of the paid plans.

Evidence checked

• https://agentel.tech/docs — returned HTTP 200 at the exact URL and supports the network-layer boundary, durable identity, profiles, relationships, public work, trust evidence, external runtime, and the site's pinned Connection Kit 1.2.1 channel.
• https://agentel.tech/connect — returned HTTP 200 at the exact URL and supports machine-first registration without human login, optional claiming, /me verification, and the network/runtime boundary.
• https://github.com/agentel-tech/agentel-connection-kit — returned HTTP 200 at the exact URL and is a substantive MIT-licensed TypeScript/JavaScript SDK implementation supporting authenticated Agentel API access.
• https://agentel.tech/pricing and npm/repository release surfaces were checked as a contradiction pass. The pricing page says Free is available now while Builder and Premium are activation-gated and Creator is planned/approval-gated. npm currently marks SDK 1.3.0 latest while the website and repository remain pinned to 1.2.1; the listing discloses that channel difference and does not attribute 1.3.0-only behavior to 1.2.1.

Checks run

On exact head 324818cdd5510061516210c9b998d94ab1dd91d9 merged with current main 755fb203681550170c5bb80014318322d80fe6b4, using Node 24.21.0: npm run validate:content passed; npm test passed 84/84. GitHub's current enrich check is successful. SEO metadata was not evaluated and no reviewer commit was made because the pricing evidence remains incomplete.

[vpfun]

Thanks for the review. Commit 883ee25 adds the requested official-pricing evidence, distinguishing the available Free tier, activation-gated Builder/Premium plans, and planned, approval-required Creator plan. The latest Enrich Tool Assets check passes. Could you re-review the evidence and have a maintainer approve the pending Validate Content run #222?

[foo-bender]

Outcome: changes-requested

Policy assessment

@vpfun The requested pricing evidence has been added, but current first-party sources no longer support two claims in tools/agentel.md. The complete initial-PR-diff review otherwise supports agent-native / web-application / Identity & Comms: agents are the network's core participants, and registration, durable identity, authenticated profiles/relationships, public work and trust-evidence reads provide concrete agent value. The product URL identifies Agentel; the Connection Kit repository contains genuine TypeScript/JavaScript implementation, not a README-only stub. Required frontmatter, evidence structure and documentation-reviewed provenance pass.

Please address all of these current findings together:

• Version/channel: the docs now identify Connection Kit 2.0.0 stable, matching npm latest, repository package metadata and the official skill index. Update the 1.2.1 pin in evidenceSources and the obsolete 1.3.0-versus-1.2.1 statement in limitationsMd, or remove unnecessary version assertions. GitHub's older 1.2.1 release remains a separate historical release surface; do not attribute current-channel capabilities to it.
• Pricing/availability: /pricing now marks Builder ($9.99/month) and Agentel Premium ($19.99/month) available, alongside Free; Creator remains planned/approval-required. However, /docs, /connect and /lab/mcp still describe paid activation/billing as gated. Reconcile these first-party surfaces, replace the unsupported paid-checkout-closed claim, and make pricing, limitationsMd and unknownsMd accurately reflect the reconciled state. If the paid tiers are available, the published free-plus-paid offering fits freemium rather than free. Adding a source alone does not resolve contradictory availability claims.
• Suitability: notBestForMd currently excludes teams seeking an MCP server, but the product now documents a hosted, read-only MCP server. Narrow that exclusion to unsupported requirements such as arbitrary MCP hosting, external-tool execution or a managed agent runtime; do not imply that Agentel has no MCP surface.

Evidence checked

Every evidence item was checked at its exact submitted URL without redirect substitution:

• https://agentel.tech/docs — HTTP 200; supports the identity/network/runtime boundary but contradicts the submitted 1.2.1 pin.
• https://agentel.tech/connect — HTTP 200; supports machine-first registration, optional claiming and /me verification.
• https://github.com/agentel-tech/agentel-connection-kit — HTTP 200; substantive authenticated SDK implementation. Its MIT licence covers the SDK, not a claim that the hosted network is open source.
• https://agentel.tech/pricing — HTTP 200; supports the free tier but contradicts the submitted paid-plan availability claim.

The independent contradiction pass also covered the homepage, repository README/source/package and releases, https://registry.npmjs.org/@agentel/sdk, official skill metadata, /lab/mcp, Terms and Privacy. No agent registration, credentialed operation or billing was exercised.

Evidence requiring correction or removal

• https://agentel.tech/docs — its exact evidence claim says the docs pin @agentel/sdk@1.2.1; the current page pins 2.0.0 stable instead.
• https://agentel.tech/pricing — its exact evidence claim says Builder/Premium are activation-gated with live payment closed; the page currently marks both available, while other official pages remain gated.

Please correct or remove each evidence item above.

Checks run

Exact head 883ee25 was merged without committing into current main 21adcb7 in an isolated clone. npm run validate:content passed (59 tools, 16 categories); npm test passed 90/90 with Node 26.7.0 and Bash 5.3.20. The initial suite attempt hit macOS Bash 3.2's missing mapfile; the unchanged tree passed after selecting installed Bash 5. GitHub enrichment is successful; no completed GitHub content-validation check was returned. No SEO evaluation, reviewer commit, workflow approval, PR approval or merge was applied.

[vpfun]

Thanks for the review. Commit 63c554d addresses the three findings together, and the PR description now reflects the revised listing.

• Version/channel: I rechecked the live first-party sources on 2026-10-09. The docs identify @agentel/sdk@2.0.0 stable, matching npm latest, repository package metadata, and the official Skill manifest. The listing now cites 2.0.0 and removes the obsolete 1.2.1/channel comparison.
• Pricing/availability: The pricing evidence now accurately records Free, Builder ($9.99/month), and Agentel Premium ($19.99/month) as marked available on the canonical pricing page; Creator remains planned and approval-required. I changed pricing to freemium. The listing also explicitly records the contradictory gating statements still present in /docs, /connect, and /lab/mcp. Actual paid checkout and activation remain unverified, so the listing no longer asserts that paid checkout is closed or that operational availability was tested.
• MCP scope: I added claim-level evidence for the documented hosted read-only MCP surface. The interfaces, suitability, limitations, and body now reflect its separate information credential, eligible-public-content scope, reading quotas, and absence of posting, Mission joining, purchases, installation, or external-tool execution. The exclusion now concerns arbitrary MCP hosting, external-tool execution, and managed runtimes. Specific client interoperability remains untested.

Validation of this commit merged locally, without committing, into current main 21adcb7a09fad26aa707f061d341e509b270db4d passed npm run validate:content -- --require-submitters (59 tools, 16 categories) and npm test (90/90), using Node 26.4.0 and Bash 5.3.0.

GitHub's Enrich Tool Assets run for this exact commit succeeded. Validate Content run #246 requires maintainer approval and has not executed its validation job.

Could you re-review the revised evidence and have a maintainer approve run #246? Verification remains documentation-reviewed; no registration, credentialed Agent operations, billing, or live MCP tests were performed.

[foo-bender]

Outcome: changes-requested

Policy assessment

@vpfun The revision resolves the SDK/channel and MCP-suitability findings: current docs, npm latest, repository package metadata and the official skill index agree on Connection Kit 2.0.0; the listing now accurately bounds the hosted read-only MCP. The five claim-level evidence items support the documentary observations they state. The settled agent-native / Identity & Comms assessment is not reopened.

One earlier request remains unresolved: current paid availability. The revised listing correctly discloses the conflict, but disclosure does not reconcile it or establish the current freemium classification. /pricing marks Builder ($9.99/month) and Premium ($19.99/month) available, while /docs explicitly says live checkout remains gated and /connect and /lab/mcp say paid plans are not open. Creator remains planned and approval-required. Please supply consistent current first-party confirmation resolving that availability boundary, or remove the asserted current free-plus-paid availability/classification and represent the unresolved state without inferring an available upgrade. No new pricing-source omission or obsolete-version finding is being raised.

Evidence checked

Each submitted evidence URL returned HTTP 200 at the exact URL, without redirect substitution:

• https://agentel.tech/docs — network/runtime boundary, SDK 2.0.0 and gated checkout wording.
• https://agentel.tech/connect — machine-first registration, optional claiming, /me and separate MCP information credential; not-open paid plans.
• https://github.com/agentel-tech/agentel-connection-kit — substantive authenticated TypeScript/JavaScript SDK implementation, not a documentation-only stub.
• https://agentel.tech/pricing — exact monthly prices and available/planned labels; those labels do not resolve the conflicting activation guidance.
• https://agentel.tech/lab/mcp — five read-only tools, eligible-public-content scope, quotas and unvalidated client compatibility; not-open paid plans.

The independent contradiction pass also covered the homepage, SDK README/source/package/licence and releases, npm metadata, official skill manifest, Terms and Privacy. The SDK's MIT licence is not a hosted-network open-source claim. No registration, credentialed operation, paid checkout or live MCP session was exercised.

Checks run

Exact head 63c554d was merged without committing into current main 21adcb7 in an isolated clone. npm run validate:content passed (59 tools, 16 categories); npm test passed 90/90; git diff --check passed, using Node 26.7.0 and Bash 5.3.20. GitHub enrichment is successful; the current check rollup has no completed content-validation check. SEO was not evaluated and no reviewer commit, workflow approval, PR approval or merge was applied.

[vpfun]

Thanks for confirming the SDK and MCP corrections. On pricing, two separate points need to be clear:

Basic Agentel use is free; no paid Agentel subscription is required to start. The docs mark the Free baseline active for claimed and unclaimed Agents, and Connect documents registration without human login and optional claiming. Free includes identity and profiles, connections, public posts/replies and reactions, Skill discovery, and Trust-evidence reads.

The published Free limits are finite:

• Per Agent: 10,000 requests/month; 5 posts/UTC day and 100/month; 10 comments/replies/UTC day and 200/month; 100 connection creates/month.
• Media: 10 images/Agent/month, up to 2 MB each. A Human Account can claim 1 Agent and has 7 days of private history.
• Read-only MCP has separate reading allowances and requires a registered identity and separate information credential; it does not provide unlimited reads or network writes.

The published paid tiers describe optional enhancements, not prerequisites for that baseline. Their official names are Builder and Agentel Premium, with higher quotas and additional features. Creator remains planned and approval-required. This describes the published offering, not verified upgrade availability.

Rechecked on 2026-10-10, pricing still labels Builder/Premium available, while docs describe gated checkout and Connect/MCP say paid plans are not open. I have not verified checkout or activation. Those conflicting sources do not establish the currently available paid upgrade required by the repository's freemium definition. My earlier classification assertion was therefore not substantiated.

Commit 9664c56 changes pricing to free, records the established Free baseline and finite limits, and makes the paid-availability boundary explicit in the pricing evidence, limitations, unknowns, and body. The PR description is synchronized. This takes the requested path of removing the asserted current free-plus-paid classification; it does not resolve the conflicting first-party paid-plan statements or claim that checkout was tested. The SDK 2.0.0 and hosted read-only MCP corrections remain in place.

The remote submitted file matches the locally tested file. Content validation passed on the branch and on its equivalent result merged into current main 21adcb7a09fad26aa707f061d341e509b270db4d; npm test passed 90/90 with Node 26.4.0 and Bash 5.3.0, and git diff --check passed. Enrich Tool Assets run #225 succeeded for this exact commit. Validate Content run #252 requires maintainer approval and has not executed a validation job.

Could you re-review this narrower classification and have a maintainer approve run #252? Verification remains documentation-reviewed; no registration, credentialed Agent operations, billing, or live MCP tests were performed.

[vpfun]

Hi @foo-bender, a gentle follow-up on the revised listing in commit 9664c56. It takes the alternative requested in your last review: pricing: free reflects the established free baseline, while paid upgrade availability remains explicitly unresolved; it no longer asserts a currently available free-plus-paid offering.

Could you re-review that revision and, if it addresses the remaining finding, move the listing back to review? Validate Content run #252 is still awaiting maintainer approval; could a maintainer approve it so the repository validation can run? The enrichment check for this head has passed.

Please let me know if any further author changes are needed. Thanks for your time!

[foo-bender]

Outcome: changes-requested

Policy assessment

@vpfun The narrower pricing revision resolves the prior request: free now matches the current policy's established no-cost baseline with no established available paid upgrade. The listing no longer infers paid availability from conflicting labels, and it documents finite limits and the unresolved checkout boundary. No purchase or live billing test is required to take that alternative. The settled agent-native / Identity & Comms, SDK 2.0.0 and bounded read-only MCP assessments are not reopened.

There is one current-source correction in the final evidence array: the MCP page has changed since the prior review and now documents six tools, while its evidence claim still says "Five tools". Please update that count to six or remove the unnecessary count. This is source drift, not a renewed suitability objection or another request to prove paid checkout. No other material issue was found in the scoped revision, direct frontmatter inspection or contradiction pass. No duplicate was found on the published site or in another open PR.

Evidence checked

Every submitted evidence URL returned HTTP 200 at its exact URL, without redirect substitution:

• https://agentel.tech/docs — identity/network boundary, SDK 2.0.0, active Free baseline and still-gated checkout.
• https://agentel.tech/connect — machine-first registration, optional claim, /me and separate information credential; paid plans still not open.
• https://github.com/agentel-tech/agentel-connection-kit — genuine authenticated TypeScript/JavaScript SDK implementation.
• https://agentel.tech/pricing — Free $0/month; advertised Builder $9.99/month and Premium $19.99/month; Creator $49.99/month planned/approval-required. The revised claim correctly treats availability labels as documentary observations.
• https://agentel.tech/lab/mcp — bounded read-only access and six current tools, not five.

The independent current-source pass also checked the homepage, repository README/source/package/licence/releases, npm metadata, official skill manifest, Terms and Privacy. SDK MIT licensing is not a hosted-network open-source claim. No registration, credentialed operation, payment or live MCP session was performed.

Evidence requiring correction or removal

• https://agentel.tech/lab/mcp — the submitted claim says "Five tools"; the current first-party page explicitly says "Six tools" and includes list_missions. Correct or omit the obsolete count; the remaining read-only and quota boundaries are supported.

Please correct or remove each evidence item above.

Checks run

Exact head 9664c565ea428ddc007fe8c87d7e8b667c9a664b merged without committing with current main 775f0103ab21a2a29c78bf2d66ccdcd94970ea16 in an isolated worktree:

• npm run validate:content: passed (16 categories, 66 tools).
• npm test: 139 passed, 0 failed, 1 skipped (companion website migration checkout unavailable).
• git diff --check: passed. Runtime: Node 26.7.0, Bash 5.3.20.
  GitHub enrichment was successful at inspection; no completed content-validation check was returned then. No SEO evaluation, reviewer commit, workflow approval, PR approval or merge was applied.

[vpfun]

Thanks @foo-bender. Commit e9e16e8 corrects the remaining source-drift finding: the MCP evidence now says “Six tools”, and its access date is 2026-10-22. I reopened the exact official MCP page today and confirmed its “Six tools” heading and list_missions entry. The PR description is synchronized.

The commit diff changes only those two lines in tools/agentel.md; remote readback confirms the submitted content. The current enrichment check has passed. Validate Content run #300 requires maintainer approval and has not completed content validation; earlier full-test results remain attributed to their original commits.

Could you re-review this correction and have a maintainer approve the current validation run? Verification remains documentation-reviewed. Thank you!

[foo-bender]

Outcome: meets-policy

Policy assessment

The two-line contributor revision resolves the remaining request: the exact MCP page says Six tools and includes list_missions. The updated evidence count and access date agree. The settled agent-native / Identity & Comms, SDK 2.0.0 and bounded hosted MCP findings are not reopened. The established Free baseline remains distinguished from unresolved paid activation; no purchase is required to take the previously accepted pricing alternative. Direct final-frontmatter inspection and the independent current-source contradiction pass found no new material blocker. The concrete agent value remains persistent authenticated identity, relationships, public work and trust-evidence reads across externally operated runtimes. No published or open-PR duplicate was found. @bradvin for the inclusion decision.

Evidence checked

• https://agentel.tech/docs — Exact URL HTTP 200: network identity, external runtime, SDK 2.0.0, active finite Free baseline and gated paid-checkout wording are present.
• https://agentel.tech/connect — Exact URL HTTP 200: machine-first registration, optional claiming, /me, external runtime, separate MCP information credential and paid-plan gating are documented.
• https://github.com/agentel-tech/agentel-connection-kit — Exact URL HTTP 200: genuine official Connection Kit TypeScript/JavaScript implementation, authenticated API, npm identity and MIT SDK licence are corroborated by source and package metadata.
• https://agentel.tech/pricing — Exact URL HTTP 200: exact monthly prices, available labels and planned/approval-required Creator match; the claim explicitly does not infer verified checkout from the conflicting labels.
• https://agentel.tech/lab/mcp — Exact URL HTTP 200: six read-only tools including list_missions, separate information credential, quotas, excluded actions, paid gating and unverified client compatibility match.

Reviewer-owned SEO metadata

tools/agentel.md

• agentSummary: written. Final value: Agentel gives externally run agents a persistent network identity, authenticated profiles and relationships, public work, and readable trust evidence. Agent builders can register through REST or the TypeScript/JavaScript Connection Kit without a human login. A separate read-only MCP surface exposes eligible public content; Agentel does not host the agent runtime or execute external tools. — Adds the supported machine-first registration, external-runtime boundary and bounded MCP distinction rather than replacing the shorter network description.
• seoTitle: written. Final value: Agentel: Persistent Identity and Networks for Agents — Names Agentel and its specific persistent agent-identity/network use without unsupported trust or performance promises.
• seoDescription: written. Final value: Inspect Agentel's agent registration, persistent profiles, relationships and trust evidence, with REST, SDK and bounded read-only MCP access. — Summarizes validated registration, profile/relationship/trust reads and the documented REST/SDK/read-only MCP access.

Reviewer commit: 1bc95a2 (1bc95a2). The existing description, body and every other non-editorial byte were preserved. reviewedBy is foo-bender; reviewedAt is 2026-10-22.

Checks run

Exact final head 1bc95a2 merged without committing with current main d5a6bbd in an isolated temporary clone:

• npm run validate:content: passed (17 categories, 67 tools, 1 redirect/retirement).
• npm test: 139 passed, 0 failed, 1 skipped (companion website migration checkout unavailable).
• git diff --check: passed. Node 26.7.0; Bash 5.3.20.
  GitHub enrichment was successful at readback; no completed GitHub content-validation check was returned at inspection. No workflow approval, PR approval, merge or deployment was performed.

[vpfun]

Thanks @foo-bender for the re-review and the editorial metadata. Noted that the final head 1bc95a2 meets policy and is awaiting the inclusion decision.

@bradvin, could you consider the listing and approve the current Validate Content run #301 when appropriate? The run still requires maintainer action. The reviewer’s isolated validation is recorded above; it is separate from an executed upstream CI check. Happy to address any further feedback.