1) How to add new TSC members
---------
Signed-off-by: Sam Betts <1769706+Tehsmash@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Sam Betts <1769706+Tehsmash@users.noreply.github.com>
- Change table header to include repository instead of stability (all
are currently stable)
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Sampath Kumar <sam1990kumar@gmail.com>
## Summary
- Adds `docs/topics/custom-protocol-bindings.md`, a dedicated page
documenting custom protocol bindings as a concept distinct from
extensions; covers declaration in the Agent Card, specification
requirements, key areas to address (data type mappings, service
parameters, error mapping, streaming, authentication), and
interoperability testing
- Adds `docs/topics/extension-and-binding-governance.md`, merging the
governance content previously in `extensions.md` with the equivalent
custom protocol binding governance; deduplicates the tiers section into
a single section with a naming table; notes that SDKs SHOULD implement
official custom protocol bindings vs MAY for extensions
- Adds spec section 5.8 defining URI-based custom binding identification
as a SHOULD requirement and updates the section 12.7 Agent Card example
accordingly
- Replaces the verbose inline governance sections in `extensions.md` and
`custom-protocol-bindings.md` with short summaries linking to the new
governance page
- Adds Custom Protocol Bindings and Extension & Binding Governance to
the mkdocs.yml nav
---------
Signed-off-by: Sam Betts <1769706+Tehsmash@users.noreply.github.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
# Description
- [ ] Follow the [`CONTRIBUTING`
Guide](https://github.com/a2aproject/A2A/blob/main/CONTRIBUTING.md).
- [ ] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- [ ] Ensure the tests and linter pass (Run `nox -s format` from the
repository root to format)
- [ ] Appropriate docs were updated (if necessary)
Pins the `check-spelling/check-spelling` action to `v0.0.26` to resolve
the unsafe workflow configuration error (exit code 5) that was blocking
all PRs from passing the Check Spelling CI gate.
Fixes#1710🦕
Signed-off-by: Sam Betts <1769706+Tehsmash@users.noreply.github.com>
Updates GitHub Actions workflow references from the legacy `github/` org
path to the canonical `github-community-projects/` path.
The following OSPO actions have been transferred to the
`github-community-projects` organization:
| Legacy path | Canonical path |
|---|---|
| `github/issue-metrics` | `github-community-projects/issue-metrics` |
While GitHub's repo redirect ensures the old paths still work today,
updating to the canonical path avoids depending on the redirect and
ensures long-term stability.
**No functional changes** - the same action versions are referenced.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
## Summary
Add a Community SDKs section to the Community Hub page listing
community-maintained A2A SDK implementations for languages not covered
by official SDKs.
Fixes#1602
## Changes
- **Updated: `docs/community.md`** — inline SDK directory section with
listings and submission requirements
- **Updated: `mkdocs.yml`** — cleaned up nav
- **Updated: `.github/actions/spelling/allow.txt`** — added GitHub
usernames
## Initial Listings
| Language | Repository | Package | Spec Version |
|----------|-----------|---------|-------------|
| 🦀 Rust | [tomtom215/a2a-rust](https://github.com/tomtom215/a2a-rust) |
[crates.io](https://crates.io/crates/a2a-protocol-sdk) | 1.0.0 |
| 🦀 Rust | [EmilLindfors/a2a-rs](https://github.com/EmilLindfors/a2a-rs)
| [crates.io](https://crates.io/crates/a2a-rs) | 0.3.0 |
| 🍎 Swift |
[tolgaki/a2a-client-swift](https://github.com/tolgaki/a2a-client-swift)
| SPM | 1.0.0 |
| 💧 Elixir |
[actioncard/a2a-elixir](https://github.com/actioncard/a2a-elixir) |
[hex.pm](https://hex.pm/packages/a2a) | 0.2.0 |
## Context
Community SDKs are emerging (see
[#1638](https://github.com/a2aproject/A2A/issues/1638) for the Rust
SDK), but there was no place in the docs for users to discover them.
Rather than a standalone page, these are inlined as a section on the
Community Hub for better discoverability.
---------
Co-authored-by: Zaf (AI Assistant) <zaf@0-a.org>
Adds [Strale](https://strale.dev) to the A2A partners list.
Strale is an API capability marketplace for AI agents with a live A2A
implementation:
- **Agent Card**: https://api.strale.io/.well-known/agent-card.json
- **A2A endpoint**: `POST https://api.strale.io/a2a` (JSON-RPC:
`message/send`, `tasks/get`)
- **273 skills** across compliance, company data (27 countries),
financial validation, Web3/DeFi, and developer tools
- **Link header** on all responses: `Link:
</.well-known/agent-card.json>; rel="agent-card"`
Also accessible via MCP (Streamable HTTP), REST API, and x402 (USDC
micropayments on Base).
## Summary
[OIXA Protocol](https://oixa.io) is a live open protocol where AI agents
hire and pay other AI agents autonomously — built on A2A for agent
communication, with economic guarantees on Base Mainnet.
## How OIXA uses A2A
OIXA builds directly on A2A as the communication layer for agent
discovery and task coordination. It publishes a standard A2A agent card:
```
http://64.23.235.34:8000/.well-known/agent.json
```
**Protocol stack:**
- **COMMS:** A2A + MCP — agent discovery and task protocol
- **PAYMENT:** x402 Protocol — autonomous HTTP payments
- **FUNDS:** Base Mainnet + USDC — trustless on-chain escrow
- **REGISTRY:** ERC-8004 — on-chain agent identity
## What OIXA adds on top of A2A
A2A defines *how* agents communicate. OIXA defines *how they transact*
when that communication leads to work that should exchange value:
- Reverse auction discovery: agents bid to complete tasks (lowest bid
wins)
- On-chain USDC escrow: funds lock at bid acceptance, release
automatically on verified delivery
- Cryptographic output verification: not just delivery confirmation but
quality verification
- Stake-based anti-Sybil: 20% stake per bid makes economic attacks
impossible
- On-chain reputation: every completed A2A transaction builds a
verifiable score
## Links
- Site: https://oixa.io
- GitHub: https://github.com/ivoshemi-sys/oixa-protocol
- SDK: `pip install oixa-protocol` (LangChain, CrewAI, AutoGen,
Haystack, MCP)
- Live API: http://64.23.235.34:8000/docs
- A2A agent card: http://64.23.235.34:8000/.well-known/agent.json
Co-authored-by: Openclaw <Openclaw@Mac-mini-de-Ivan.local>
Issue: #1679
# Description
[a2a-samples/python](https://github.com/a2aproject/a2a-samples/tree/main/samples/python)
is being updated to use the new `v1.0`:
[samples-#462](https://github.com/a2aproject/a2a-samples/issues/462). We
are looking to merge [update helloworld sample to
v1.0-alpha](https://github.com/a2aproject/a2a-samples/pull/474) and
consequently need to update python tutorial in A2A as it references the
`helloworld sample`.
# Key Changes
- **Agent Skills & Card** (3-agent-skills-and-card.md): Updated the docs
to match the new AgentCard schema. Replaced the legacy `url` property
with `icon_url`, documented the new `supported_interfaces` field for
protocol bindings, and added mentions of the extended_agent_card
capability.
- **HelloWorldAgentExecutor logic** (4-agent-executor.md): Rewrote the
walkthrough for the execute method to reflect the modern event-driven
approach and to make the difference between non-streaming and streaming
more clear. It now explicitly describes enqueueing Task,
TaskStatusUpdateEvent (with `TASK_STATE_WORKING`),
TaskArtifactUpdateEvent, and TaskStatusUpdateEvent (with
`TASK_STATE_COMPLETED`) instead of single string messages.
- **Server Setup** (5-start-server.md): Replaced `0.0.0.0` with
`127.0.0.1` in the host binding tutorial and log examples to enforce
safer local testing defaults.
- **Client Interaction** (6-interact-with-server.md):
- Replaced MessageSendParams dictionaries with native protobuf
`Message/Part/Role` construction.
- Replaced direct A2ACardResolver instantiation with the new
`ClientFactory` approach.
- Unified the documentation around `send_message` (which now handles
streams dynamically based on `config` and agent capabilities) and
updated expected log outputs.
Closes#1636
Adds [WritBase](https://github.com/Writbase/writbase) to the A2A
partners list.
WritBase is an MCP-native task management control plane for AI agent
fleets — Postgres-backed, multi-tenant, with full provenance tracking.
It includes bidirectional A2A↔WritBase status mapping alignment and
supports inter-agent task delegation with assignment tracking and
delegation safety.
Fixes#1612
Section 6.5 examples used `POST /tasks/list` with a JSON body,
contradicting section 11.3.2 which correctly defines list tasks as `GET
/tasks` with query parameters.
## Changes
- **`docs/specification.md` — Section 6.5 (Task Listing and
Management):** Updated all four HTTP examples to use `GET /tasks` with
query parameters instead of `POST /tasks/list` with a request body:
| Example | Before | After |
|---|---|---|
| All tasks from a specific context | `POST /tasks/list` + JSON body |
`GET /tasks?contextId=...&pageSize=10&historyLength=3` |
| All working tasks across all contexts | `POST /tasks/list` + JSON body
| `GET /tasks?status=working&pageSize=20` |
| Pagination | `POST /tasks/list` + JSON body | `GET
/tasks?contextId=...&pageSize=10&pageToken=...` |
| Validation error | `POST /tasks/list` + JSON body | `GET
/tasks?pageSize=150&historyLength=-5&status=running` |
Enum values in query parameters now use the short form (e.g.,
`status=working`) per the field type handling rules already defined in
section 11.5.
<!-- START COPILOT CODING AGENT TIPS -->
---
✨ Let Copilot coding agent [set things up for
you](https://github.com/a2aproject/A2A/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot)
— coding agent works faster and does higher quality work when set up for
your repo.
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: darrelmiller <447694+darrelmiller@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Darrel <darrmi@microsoft.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Closes#1478. Related to #306.
The specification provides caching guidance for Extended Agent Cards
(Sections 3.1.11 and 13.3) but has no equivalent guidance for public
Agent Cards. This creates a gap for SDK and framework implementers —
none of the five official SDKs currently implement Agent Card caching,
and framework implementers have noted the lack of protocol-level
guidance (google/adk-python#3297).
This PR adds SHOULD-level HTTP caching guidance, following the precedent
of OpenID Connect Discovery 1.0 (same `.well-known` URI pattern).
**Changes:**
- **`docs/specification.md`**: Add Section 8.6 "Caching" with normative
guidance on `Cache-Control`, `ETag`, and conditional requests. Placed
after Section 8.5 (Sample Agent Card) to avoid renumbering existing
sections and breaking anchor links.
- **`docs/topics/agent-discovery.md`**: Add "Caching Considerations"
section with practical guidance for implementers.
---------
Co-authored-by: Darrel <darrmi@microsoft.com>
Updates the specification to require use of `google.rpc.Status`
formatted JSON objects for error response bodies in HTTP+JSON mapping.
See related issue for reasoning.
Fixes#1596
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Darrel <darrmi@microsoft.com>
Bumps the github-actions group with 1 update:
[astral-sh/setup-uv](https://github.com/astral-sh/setup-uv).
Updates `astral-sh/setup-uv` from 5 to 7
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/astral-sh/setup-uv/releases">astral-sh/setup-uv's
releases</a>.</em></p>
<blockquote>
<h2>v7.2.1 🌈 update known checksums up to 0.9.28</h2>
<h2>Changes</h2>
<h2>🧰 Maintenance</h2>
<ul>
<li>chore: update known checksums for 0.9.28 @<a
href="https://github.com/apps/github-actions">github-actions[bot]</a>
(<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/744">#744</a>)</li>
<li>chore: update known checksums for 0.9.27 @<a
href="https://github.com/apps/github-actions">github-actions[bot]</a>
(<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/742">#742</a>)</li>
<li>chore: update known checksums for 0.9.26 @<a
href="https://github.com/apps/github-actions">github-actions[bot]</a>
(<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/734">#734</a>)</li>
<li>chore: update known checksums for 0.9.25 @<a
href="https://github.com/apps/github-actions">github-actions[bot]</a>
(<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/733">#733</a>)</li>
<li>chore: update known checksums for 0.9.24 @<a
href="https://github.com/apps/github-actions">github-actions[bot]</a>
(<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/730">#730</a>)</li>
</ul>
<h2>📚 Documentation</h2>
<ul>
<li>Clarify impact of using actions/setup-python <a
href="https://github.com/eifinger"><code>@eifinger</code></a> (<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/732">#732</a>)</li>
</ul>
<h2>⬆️ Dependency updates</h2>
<ul>
<li>Bump zizmorcore/zizmor-action from 0.3.0 to 0.4.1 @<a
href="https://github.com/apps/dependabot">dependabot[bot]</a> (<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/741">#741</a>)</li>
</ul>
<h2>v7.0.0 🌈 node24 and a lot of bugfixes</h2>
<h2>Changes</h2>
<p>This release comes with a load of bug fixes and a speed up. Because
of switching from node20 to node24 it is also a breaking change. If you
are running on GitHub hosted runners this will just work, if you are
using self-hosted runners make sure, that your runners are up to date.
If you followed the normal installation instructions your self-hosted
runner will keep itself updated.</p>
<p>This release also removes the deprecated input
<code>server-url</code> which was used to download uv releases from a
different server.
The <a
href="https://github.com/astral-sh/setup-uv?tab=readme-ov-file#manifest-file">manifest-file</a>
input supersedes that functionality by adding a flexible way to define
available versions and where they should be downloaded from.</p>
<h3>Fixes</h3>
<ul>
<li>The action now respects when the environment variable
<code>UV_CACHE_DIR</code> is already set and does not overwrite it. It
now also finds <a
href="https://docs.astral.sh/uv/reference/settings/#cache-dir">cache-dir</a>
settings in config files if you set them.</li>
<li>Some users encountered problems that <a
href="https://github.com/astral-sh/setup-uv?tab=readme-ov-file#disable-cache-pruning">cache
pruning</a> took forever because they had some <code>uv</code> processes
running in the background. Starting with uv version <code>0.8.24</code>
this action uses <code>uv cache prune --ci --force</code> to ignore the
running processes</li>
<li>If you just want to install uv but not have it available in path,
this action now respects <code>UV_NO_MODIFY_PATH</code></li>
<li>Some other actions also set the env var <code>UV_CACHE_DIR</code>.
This action can now deal with that but as this could lead to unwanted
behavior in some edgecases a warning is now displayed.</li>
</ul>
<h3>Improvements</h3>
<p>If you are using minimum version specifiers for the version of uv to
install for example</p>
<pre lang="toml"><code>[tool.uv]
required-version = ">=0.8.17"
</code></pre>
<p>This action now detects that and directly uses the latest version.
Previously it would download all available releases from the uv repo
to determine the highest matching candidate for the version specifier,
which took much more time.</p>
<p>If you are using other specifiers like <code>0.8.x</code> this action
still needs to download all available releases because the specifier
defines an upper bound (not 0.9.0 or later) and "latest" would
possibly not satisfy that.</p>
<h2>🚨 Breaking changes</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="5a095e7a20"><code>5a095e7</code></a>
Bump github/codeql-action from 4.31.9 to 4.32.2 (<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/766">#766</a>)</li>
<li><a
href="b12532f27f"><code>b12532f</code></a>
fix: fall back to VERSION_CODENAME when VERSION_ID is not available (<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/774">#774</a>)</li>
<li><a
href="0098a7571c"><code>0098a75</code></a>
chore: update known checksums for 0.10.6 (<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/771">#771</a>)</li>
<li><a
href="2e7ed0e2bb"><code>2e7ed0e</code></a>
chore: update known checksums for 0.10.5 (<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/770">#770</a>)</li>
<li><a
href="04224aa8ca"><code>04224aa</code></a>
chore: update known checksums for 0.10.4 (<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/768">#768</a>)</li>
<li><a
href="2bc602ff89"><code>2bc602f</code></a>
chore: update known checksums for 0.10.3 (<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/767">#767</a>)</li>
<li><a
href="dd9d748439"><code>dd9d748</code></a>
chore: update known checksums for 0.10.2 (<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/765">#765</a>)</li>
<li><a
href="14eede1834"><code>14eede1</code></a>
chore: update known checksums for 0.10.1 (<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/764">#764</a>)</li>
<li><a
href="c452423b2c"><code>c452423</code></a>
Bump zizmorcore/zizmor-action from 0.4.1 to 0.5.0 (<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/763">#763</a>)</li>
<li><a
href="eac588ad8d"><code>eac588a</code></a>
Bump typesafegithub/github-actions-typing from 2.2.1 to 2.2.2 (<a
href="https://redirect.github.com/astral-sh/setup-uv/issues/753">#753</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/astral-sh/setup-uv/compare/v5...v7">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
## Summary
- Adds [JamJet](https://github.com/jamjet-labs/jamjet) to the partners
list in alphabetical order
- JamJet is an open-source agent-native runtime with native A2A client +
server support built in Rust
Closes#1602
---------
Co-authored-by: Amye Scavarda Perrin <amye@amye.org>
The previous wording was very barebones. We have explored this area
significantly more, and the specification now reflects further guidance
on how to handle retrieving authorizations and credentials during Task
processing.
This specifically addresses the missing guidance on how clients are
expected to respond to a Task in `TASK_STATE_AUTH_REQUIRED`.
Fixes#1582.
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
As mentioned in the linked issue, defaulting to non-blocking behavior is
counterintuitive and is implemented the opposite way in the SDKs.
Renaming it to `return_immediately` makes default behavior simpler while
advanced scenario requires an extra flag.
---
Previos proposals:
1. `polling` has inaccurate meaning in this context as pointed out in
the comments.
2. `non_blocking` is a negative boolean which leads to confusing
conditional expressions (`not non_blocking`).
Fixes#1453
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
client side context id passing can be supported, server can choose to
reject, client's should know how to fallback accordingly
if server accepts, server must respond with the context id
if server cannot accept client side context id it MUST respond with an
error (i.e. it SHOULD not respond with a task with a different context
id?)
servers may not accept a client side context id for a number of reasons:
clashes, validation errors, not supporting context ids
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Fix error caused by #1500:
× Failed to build `a2a-sdk @
file:///home/runner/work/a2a-python/a2a-python`
├─▶ The build backend returned an error
╰─▶ Call to `hatchling.build.build_editable` failed (exit status: 1)
[stderr]
Failure: failed_precondition: plugin
"buf.build/grpc-ecosystem/openapiv2:v2.28.0" failed: no field "config"
found in TaskPushNotificationConfig
**this PR:**
- removes CreateTaskPushNotificationConfigRequest and replace it with
TaskPushNotificationConfig (same fields).
- flattend TaskPushNotificationConfig and PushNotificationConfig
removing the latter
- puts TaskPushNotificationConfig in SendMessageConfig instead of the
removed PushNotificationConfig
**why:** more readable structure, with less messages but with the same
possibilities
Release-As: 1.0.0
---------
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
This PR adds [AgentTrust](https://agenttrust.ai) to the partners list,
alphabetically between AG2AI and AI21 Labs.
**About AgentTrust:**
AgentTrust is trust and identity infrastructure for agentic
collaboration. We provide hosted A2A endpoints with Agent Card
discovery, Ed25519 message signing, human-in-the-loop escalation, and
prompt injection detection.
**What we've built:**
- Hosted A2A endpoints — agents get a public A2A identity at
`/a2a/{slug}` without running a server
- Standard Agent Card served at `/.well-known/agent.json` per agent
- Direct A2A JSON-RPC ingress (`tasks/send`) with allowlist,
InjectionGuard, and HITL rules
- Ed25519 message signing — cryptographic identity verification between
agents
- Negotiation lifecycle extending A2A task states via metadata
extensions (`propose_complete`, `disputed`, `rejected`)
- MCP server with 13 tools —
[npm](https://www.npmjs.com/package/@agenttrust/mcp-server) |
[GitHub](https://github.com/agenttrust/mcp-server)
- Webhook delivery with HMAC-SHA256 signatures
**Links:**
- Website: https://agenttrust.ai
- MCP Server: https://github.com/agenttrust/mcp-server
- npm: https://www.npmjs.com/package/@agenttrust/mcp-server
Built on Google's A2A protocol. We fill the identity and trust gap — A2A
defines how agents talk, AgentTrust helps them prove who they are.
---------
Co-authored-by: AgentTrust <hello@agenttrust.ai>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Amye Scavarda Perrin <amye@amye.org>
Hi Amye and team,
Following up on issue #1443 ("Add Pinchwork as A2A-compatible agent
marketplace") — thank you for the warm welcome and for pointing us to
the partners list!
This PR adds [Pinchwork](https://pinchwork.dev) to the partners list,
alphabetically between Personal AI and Poppulo.
**About Pinchwork:**
Pinchwork is an agent-to-agent task marketplace where AI agents can post
tasks, pick up work, and earn credits — all via a simple API. We have a
live A2A endpoint at `/.well-known/agent-card.json` and a JSON-RPC A2A
endpoint at `/a2a`, supporting `message/send`, `tasks/get`, and
`tasks/cancel`.
We're excited to be part of the A2A ecosystem and look forward to
contributing to interoperability between agents.
Resolves#1443
Co-authored-by: Pinchwork <hello@pinchwork.dev>
Co-authored-by: Amye Scavarda Perrin <amye@amye.org>
https://github.com/a2aproject/A2A/actions/runs/22359664144 fails with
```
go: github.com/bufbuild/buf/cmd/buf@latest: github.com/bufbuild/buf@v1.66.0 requires go >= 1.25.6 (running go 1.24.12; GOTOOLCHAIN=local)
```
Long term docs.yml probably shouldn't use `@latest` to avoid such
breakages in CI without code changes.
Re #1510 (adding `no-issue` as it's not `Fixes`)
## Summary
The follow-up scenario example in \`docs/topics/life-of-a-task.md\` used
\`"message.send"\` (dot notation) for the first request, while the
second request in the same example correctly used \`"SendMessage"\`
(v1.0 PascalCase). This made the file internally inconsistent and showed
a method name that doesn't exist in any version of the protocol.
## Change
\`\`\`diff
- "method": "message.send",
+ "method": "SendMessage",
\`\`\`
**File:** \`docs/topics/life-of-a-task.md\`
## Related
- Closes#1493
- Related to #1367 (method name inconsistencies across documentation)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Gijs Walraven <gijs.walraven@delaware.pro>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
## Summary
Fixes documentation inconsistencies related to Part discriminator field
values, identified in #1365.
## Changes
### `docs/specification.md` — Appendix A.2.1
- **Legacy Part `kind` values**: corrected from PascalCase (`"kind":
"TextPart"`, `"kind": "FilePart"`, `"kind": "DataPart"`) to lowercase
(`"kind": "text"`, `"kind": "file"`, `"kind": "data"`), consistent with
what `whats-new-v1.md` documents as the v0.3.0 format
- **Legacy FilePart structure**: added the missing nested `file` object
wrapper
- **Legacy streaming event `kind` values**: corrected from PascalCase
(`TaskStatusUpdateEvent`, `TaskArtifactUpdateEvent`) to camelCase
(`taskStatusUpdate`, `taskArtifactUpdate`)
- **Current `DataPart` migration target**: removed incorrect
double-wrapping (`{ "data": { "data": {...} } }` → `{ "data": {...},
"mediaType": "application/json" }`)
- **Current streaming event member names**: aligned with
`whats-new-v1.md` (`taskStatusUpdate` / `taskArtifactUpdate`)
### `docs/topics/key-concepts.md`
- Updated Part description to use v1.0 terminology, removing references
to the removed `TextPart`, `FilePart`, and `DataPart` types
### `docs/tutorials/python/8-next-steps.md`
- Replaced reference to removed `DataPart` type with v1.0 Part field
names
### `CONTRIBUTING.md`
- Added **Documentation Guidelines** section with correct v1.0 Part
examples (member-presence pattern) and guidance on the correct v0.3.x
lowercase `kind` discriminator values for migration docs
## Related
- Closes#1365
- External community site fix:
https://github.com/sing1ee/a2a-directory/pull/12🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Gijs Walraven <gijs.walraven@delaware.pro>
This corrects the wording so that blocking=True includes terminal and
interrupted states as triggers for returning to the client.
Fixes: #1264
---------
Signed-off-by: Sam Betts <1769706+Tehsmash@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
ID is already present in the config object.
It is not used in path segment bindings and also uses inconsistent
naming with other push-related rpc payloads.
fixes https://github.com/a2aproject/A2A/issues/1451
Follow-up to #1389
---------
Co-authored-by: Kuba Herczyński <herczyn@google.com>