agent-protocols

band: warmmomentum: stable score: 0.252

temperature history

Episodes (7)

Independent deployments will determine whether AgentBridge’s x402 payment loop lets autonomous agents purchase machine-provided data and services with workable security, reliability, and operational overhead.

expiredconvergesscott: medium

Independent implementations will determine whether OJCP provides a practical interoperable alternative to career-page scraping and browser automation for job-search agents.

expiredknownscott: low

Independent implementations will determine whether OpenOx enables agents to modify and evaluate their workflows across runtimes with reproducible and interoperable behavior.

expiredknownscott: low

AC2 Protocol’s maintainers claim their protocol supplies a practical security and authorization layer for tool-using AI agents, potentially standardizing least-privilege agent interactions.

resolvedconvergesscott: high

Aether Protocol’s maintainers claim their open protocol lets AI agents discover services, negotiate terms, and make payments to one another, potentially providing an interoperability layer for machine-to-machine commerce.

resolvedknownscott: none

Jido SDK author mikehostetler claims A2A, ACP, and Microsoft's chat-centred AHP all leave durable non-chat actor sessions uncovered and his draft DASP protocol fills that gap; adoption beyond its experimental Elixir/TypeScript clients would establish durable actor sessions as a standard agent-communication layer, while stagnation would confine it to a Jido-ecosystem extension.

seedconvergesscott: medium

Sierra (Bret Taylor, Clay Bavor), Meta, and partners including Genesys, Rocket, Shopify, Stripe, and Walmart propose the Personal Agent Protocol — an OAuth-based open standard for how personal agents authenticate and transact with businesses — and third-party implementations beyond the founding partners resolve whether it becomes the standard agent-business interop layer rather than another vendor protocol draft.

watchingconvergesscott: high

Trajectory notes

2026-10-09T02:37:07Z: aether-agent-commerce-protocol closed (window-closed) — Scott’s Agent Addressability page already carries the core position that external agents need explicit cross-boundary discovery and delegation surfaces; Aether is another claimed implementation, not a new argument or conse
2026-09-24T19:23:22Z: ac2-agent-security-protocol closed (superseded) — AC2 independently converges on Scott’s architecture of separating agent proposals from user-held authority and issuing bounded, signed authorization for consequential actions. Its standardization bid creates a strong dated-recei
2026-08-26T21:25:11Z: openox-self-evolving-agent-protocol closed (faded) — Scott already holds the substantive position across Self-Improving Loops, Evaluation-Driven Development, and the 12-Factor Agents Framework: evolving agent workflows need stable interfaces, repeatable evaluation, and governed
2026-08-22T17:27:39Z: ojcp-agent-job-data-protocol closed (faded) — Agent Addressability already argues for machine-readable delegation surfaces instead of scraping or UI impersonation, while Scott’s browser-automation work treats agentic scraping as a costly fallback. OJCP v0.1 is another instance
2026-08-20T08:34:50Z: agentbridge-x402-agent-payments closed (faded) — AgentBridge independently implements Scott’s V4 premise that an external agent can become the customer of a machine-operable service, while directly testing his claims that spending must be bounded and each transaction explicitly