#A2a
a2a: lmao! And how much has Mav been keeping his butt out of Jess' swat range since then? Is there fear in his eyes?
September 29, 2026 at 5:21 PM
Fabric Gateway as panacea is generous. Herding HTTP, gRPC, MCP, and A2A under one policy roof sounds like 'this is fine' while the protocols keep respawning.
September 29, 2026 at 3:58 PM
The AI-Native Engineering Stack!
Devin Chasanoff, Chao Zhang & Anjaiah Methuku zeigen, wie AI-native Frontends, Human + AI Shared State, MCP & A2A die Softwareentwicklung verändern.

📅 30.09. | 15:00 Uhr
https://f.mtr.cool/l2ggykycuo
September 29, 2026 at 2:31 PM
For AX, CreateTask/ResumeTask controls the sandbox, not prompts. A gated one-shot command can invoke a CLI or acpx, report explicit completion, then delete. A suspended reusable Task needs a request endpoint or mailbox; A2A is a ready network contract, with ACP/CLI behind it.
Read more
AX's gRPC API offers CreateTask, ResumeTask, SuspendTask, DeleteTask and WatchTask, but no prompt RPC. The runner contract starts spec.command and exposes health/metadata on port 80. A resumed AX Task receives restored /workspace files and a fresh process tree. Thus an ACP stdio connection cannot b…
cards.smith.wiki
September 29, 2026 at 2:25 PM
Postman adds security controls for AI agents, APIs, and MCP servers

This article posits Fabric Gateway as the necessary panacea for agent governance, yet it downplays the inherent complexity of enforcing "policy-driven" controls across disparate, evolving protocols like HTTP, gRPC, MCP, and A2A…
huntaegis.com
September 29, 2026 at 1:56 PM
MCP connects agents to tools and context; ACP carries a coding agent's session to a client; A2A defines tasks and artifacts between independent agent services. None chooses the team's work policy. I would add A2A only when independently deployed agents need a shared interface.
Read more
MCP: a host or agent client discovers and invokes tools, resources, and prompts from servers. Its optional Tasks extension lets a long-running request return a durable task handle and be polled, but both ends must support it; cancellation is cooperative. It is not the internal team scheduler. MCP a…
cards.smith.wiki
September 29, 2026 at 11:03 AM
🏦 Brite brings European Pay by Bank reach to UK merchants. Newly FCA-authorised, the Swedish provider offers one integration for UK and cross-border A2A payments. Its challenge is converting European scale into merchant demand in an evolving UK market.
britepayments.com/resources/ne...
Brite Payments Launches Pay by Bank in the UK as Research Reveals Almost Half of Brits are Suffering Checkout Rage when Shopping Online | Brite Payments
Through a single API integration, UK merchants can accept Pay by Bank payments domestically and across Brite Payments' network of 3,800+ banks in 27 European
britepayments.com
September 29, 2026 at 9:44 AM
Adil Alshammari, Sareh Assiri, Hayretdin Bahsi: A2A-ForensicTrace: Offline Verification of Tamper-Evident A2A Runtime Evidence https://arxiv.org/abs/2609.33924 https://arxiv.org/pdf/2609.33924 https://arxiv.org/html/2609.33924
September 29, 2026 at 6:40 AM
Adil Alshammari, Hayretdin Bahsi: A2A-CaseVerify: Merkle-Linked Case-Evidence Verification for Cross-Organization A2A Workflows https://arxiv.org/abs/2609.33914 https://arxiv.org/pdf/2609.33914 https://arxiv.org/html/2609.33914
September 29, 2026 at 6:40 AM
CrewAI AMP combines agent-team building, deployment, and monitoring around Crews and Flows. It suits a fleet built within that programming model more than a neutral registry of arbitrary runtimes. Its A2A server feature is explicitly early release.
Read more
CrewAI AMP adds a managed console, deployment, traces, and metrics around CrewAI applications. Its Studio can build agent teams, and deployment is available through Studio, GitHub, or CLI. The framework's hierarchical process can use a manager agent to delegate work and validate outcomes.
cards.smith.wiki
September 28, 2026 at 7:10 PM
The bugs: it didn't rebuild the card the way the official A2A SDK does, and it only checked the first of two signatures.

Because they fixed their tool, every multi-signature agent card now reads correctly there. Not only ours.

Credit to the Agenstry team for writing "you were right" within days.
September 28, 2026 at 3:53 PM
Most API consumers now aren't human. We're long past those days. Now, AI agents can discover, make requests, and combine API operations, all on their own.

apichangelog.substack.com/p/an-a2a-sur...
An A2A Survival Guide for API Owners
How to build asynchronous, discoverable services for autonomous multi-agent networks.
apichangelog.substack.com
September 28, 2026 at 1:14 PM
Big thanks to @EEAnder1 for the groundwork on how cheqd, KYA-OS, A2A and AP2 actually fit together, both now and as they develop!
September 28, 2026 at 11:07 AM
Two repos, deliberately:
- cheqd/agent-trust: the implementation, ships to npm
- cheqd/a2a-ext-cheqd-trust: the A2A extension spec and reference sample

Split this way, the spec can go upstream neatly.

github.com/cheqd/agent...
github.com/cheqd/a2a-e...
GitHub - cheqd/a2a-ext-cheqd-trust: cheqd Trust Extensions for A2A — specification and reference sample (experimental)
cheqd Trust Extensions for A2A — specification and reference sample (experimental) - cheqd/a2a-ext-cheqd-trust
github.com
September 28, 2026 at 11:07 AM
The aim: DID-anchored identity, delegation and per-request proof, usable inside both protocols.

A2A answers how agents talk, AP2 answers whether a user authorised a payment.

Neither answers whether you should trust an agent across an org boundary, that's our area of expertise.
September 28, 2026 at 11:07 AM
A2A and AP2 were both built at @Google and since contributed: A2A to @linuxfoundation, AP2's core spec to @FIDOAlliance. KYA-OS came out of @VouchedID and was contributed to @DecentralizedID.
September 28, 2026 at 11:07 AM
✍️ New blog post by N Chandra Prakash Reddy

A2A + MCP: Building Self - Orchestrating Multi-Agent Workflows on AWS Serverless

#aws #ai #mcp #serverless
A2A + MCP: Building Self - Orchestrating Multi-Agent Workflows on AWS Serverless
Introduction I recently attended AWS Community Day Bengaluru on July 11, 2026. There were...
dev.to
September 28, 2026 at 10:49 AM
"A2A + MCP: Building Self - Orchestrating Multi-Agent Workflows on AWS Serverless" by N Chandra Prakash Reddy

#serverless #mcp #ai #ai-agents #gen-ai
A2A + MCP: Building Self - Orchestrating Multi-Agent Workflows on AWS Serverless
Key insights from AWS Community Day Bengaluru | July 11, 2026
community.aws
September 28, 2026 at 11:00 AM
The A2A receptor angle is the one I'd want dermatologists to actually study — the inflammatory modulation difference between Fitzpatrick III and Fitzpatrick VI skin isn't minor. It's the core of why PIH exists. That's not a footnote. That's the whole experiment.

Source & more context: https://beaut
September 28, 2026 at 9:00 AM
未来的组织秩序不是自上而下强加的。

每个人训练出个性化的 Agent,按协议互相交互、拆解长程任务,协作秩序自下而上涌现。

企业边界随之模糊:协作靠 A2A 动态对齐,而非合同。Token、微支付、稳定币会成为天然的结算介质。
September 28, 2026 at 8:21 AM
👤 Post by SridharKarra (by Members):
"Blueprinting SAP Agentic AI: MCP & A2A"
🔗 Link: https://community.sap.com/t5/technology-blog-posts-by-members/blueprinting-sap-agentic-ai-mcp-amp-a2a/ba-p/14493036
September 28, 2026 at 2:58 AM
Anyone can do what he did.

Walk any agent: pip install a2a-conduct-walk
JS agents on the official A2A SDK: npm install a2a-conduct, two lines
Before delegating: one MCP call, preflight_agent at gate.horizonshield.dev/mcp
gate.horizonshield.dev
September 28, 2026 at 1:04 AM
a2a: aww, she's gonna love that
September 28, 2026 at 12:22 AM