Skip to content

refactor!: Change Well-Known URI for Agent Card hosting from agent.json to agent-card.json#841

Merged
holtskinner merged 6 commits into
mainfrom
agent-card-uri
Jul 29, 2025
Merged

refactor!: Change Well-Known URI for Agent Card hosting from agent.json to agent-card.json#841
holtskinner merged 6 commits into
mainfrom
agent-card-uri

Conversation

@holtskinner

@holtskinner holtskinner commented Jul 7, 2025

Copy link
Copy Markdown
Member

Based on feedback from IANA in protocol-registries/well-known-uris#66

Release-As: 0.3.0

@holtskinner holtskinner requested a review from a team as a code owner July 7, 2025 15:16

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @holtskinner, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request implements a crucial refactoring of the well-known URI for Agent Card hosting, changing it from agent.json to agent-card.json. This change is a direct response to feedback received from IANA, ensuring better alignment with established standards for well-known URIs and improving the clarity and specificity of the Agent Card's designated location.

Highlights

  • Well-Known URI Refactoring: I've updated the recommended and example well-known URI for hosting Agent Cards from /.well-known/agent.json to /.well-known/agent-card.json across all relevant documentation.
  • Documentation Updates: All instances and references to the agent.json URI have been consistently changed to agent-card.json within the specification, key concepts, agent discovery, and Python tutorial documentation files.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the well-known URI for Agent Card hosting from agent.json to agent-card.json across all documentation files, which aligns with recent IANA feedback. The documentation changes are consistent and correct.

However, the PR appears to be incomplete as it's missing the corresponding code changes in the sample implementations. I've left comments highlighting the need to update the server and client code to reflect this breaking change, ensuring the documentation and implementation remain synchronized.

Comment thread docs/tutorials/python/5-start-server.md
Comment thread docs/tutorials/python/6-interact-with-server.md
@lukehinds

Copy link
Copy Markdown

What's the plan on rolling this out to the clients. I don't think it would be too disruptive as most are setting their own routes up?

@holtskinner

Copy link
Copy Markdown
Member Author

What's the plan on rolling this out to the clients. I don't think it would be too disruptive as most are setting their own routes up?

This is going to be changed in the official SDKs in versions which support protocol version 0.3.0

@holtskinner holtskinner changed the title refactor!: Change Well-Known URI for Agent Card hosting from agent.json to agent-card.json docs!: Change Well-Known URI for Agent Card hosting from agent.json to agent-card.json Jul 29, 2025
@holtskinner holtskinner changed the title docs!: Change Well-Known URI for Agent Card hosting from agent.json to agent-card.json refactor!: Change Well-Known URI for Agent Card hosting from agent.json to agent-card.json Jul 29, 2025
@holtskinner holtskinner merged commit 0858ddb into main Jul 29, 2025
4 checks passed
@holtskinner holtskinner deleted the agent-card-uri branch July 29, 2025 18:45
holtskinner added a commit to a2aproject/a2a-python that referenced this pull request Jul 30, 2025
holtskinner pushed a commit that referenced this pull request Jul 30, 2025
🤖 I have created a release *beep* *boop*
---


## [0.3.0](v0.2.6...v0.3.0)
(2025-07-30)


### ⚠ BREAKING CHANGES

* Add mTLS to SecuritySchemes, add oauth2 metadata url field, allow
Skills to specify Security
([#901](#901))
* Change Well-Known URI for Agent Card hosting from `agent.json` to
`agent-card.json` ([#841](#841))
* Add method for fetching extended card
([#929](#929))

### Features

* Add `signatures` to the `AgentCard`
([#917](#917))
([ef4a305](ef4a305))
* Add method for fetching extended card
([#929](#929))
([2cd7d98](2cd7d98))
* Add mTLS to SecuritySchemes, add oauth2 metadata url field, allow
Skills to specify Security
([#901](#901))
([e162c0c](e162c0c))


### Bug Fixes

* **spec:** Add `SendMessageRequest.request` `json_name` mapping to
`message` ([#904](#904))
([2eef3f6](2eef3f6))
* **spec:** Add Transport enum to specification
([#909](#909))
([e834347](e834347))


### Code Refactoring

* Change Well-Known URI for Agent Card hosting from `agent.json` to
`agent-card.json` ([#841](#841))
([0858ddb](0858ddb))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
@lindsaydsgdnolan-eng

Copy link
Copy Markdown

Please help me:
INFO: 127.0.0.1:40606 - "GET /.well-known/agent-card.json HTTP/1.1" 404 Not Found

@lindsaydsgdnolan-eng

Copy link
Copy Markdown

请帮帮我:INFO: 127.0.0.1:40606 - “GET /.well-known/agent-card.json HTTP/1.1” 404 未找到

already fixed

debug313 pushed a commit to debug313/agent-to-agent that referenced this pull request Apr 12, 2026
🤖 I have created a release *beep* *boop*
---


## [0.3.0](a2aproject/A2A@v0.2.6...v0.3.0)
(2025-07-30)


### ⚠ BREAKING CHANGES

* Add mTLS to SecuritySchemes, add oauth2 metadata url field, allow
Skills to specify Security
([#901](a2aproject/A2A#901))
* Change Well-Known URI for Agent Card hosting from `agent.json` to
`agent-card.json` ([#841](a2aproject/A2A#841))
* Add method for fetching extended card
([#929](a2aproject/A2A#929))

### Features

* Add `signatures` to the `AgentCard`
([#917](a2aproject/A2A#917))
([e799342](a2aproject/A2A@e799342))
* Add method for fetching extended card
([#929](a2aproject/A2A#929))
([ae89f89](a2aproject/A2A@ae89f89))
* Add mTLS to SecuritySchemes, add oauth2 metadata url field, allow
Skills to specify Security
([#901](a2aproject/A2A#901))
([a5c881e](a2aproject/A2A@a5c881e))


### Bug Fixes

* **spec:** Add `SendMessageRequest.request` `json_name` mapping to
`message` ([#904](a2aproject/A2A#904))
([273a1f1](a2aproject/A2A@273a1f1))
* **spec:** Add Transport enum to specification
([#909](a2aproject/A2A#909))
([3076ae6](a2aproject/A2A@3076ae6))


### Code Refactoring

* Change Well-Known URI for Agent Card hosting from `agent.json` to
`agent-card.json` ([#841](a2aproject/A2A#841))
([c20c28b](a2aproject/A2A@c20c28b))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants