Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/csit/csit.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,8 @@ csit
│   ├── agntcy-slim # Benchmark tests for SLIM
│   │   ├── Taskfile.yml # Tasks for SLIM benchmark tests
│   │   └── tests
│   ├── agntcy-dir # Benchmark tests for ADS
│   │   ├── Taskfile.yml # Tasks for ADS benchmark tests
│   ├── agntcy-dir # Benchmark tests for Agent Directory Service
│   │   ├── Taskfile.yml # Tasks for Agent Directory Service benchmark tests
│   │   └── tests
│   ├── go.mod
│   ├── go.sum
Expand All @@ -31,7 +31,7 @@ csit
│   │   ├── components
│   │   ├── examples
│   │   ├── manifests
│   │   ├── Taskfile.yml # Tasks for ADS integration tests
│   │   ├── Taskfile.yml # Tasks for Agent Directory Service integration tests
│   │   └── tests
│   ├── environment # Test environment helpers
│   │   └── kind
Expand Down Expand Up @@ -71,8 +71,8 @@ The following tasks are defined:

```bash
task: Available tasks for this project:
* benchmarks:directory:test: All ADS benchmark test
* benchmarks:slim:test: All SLIM benchmark test
* benchmarks:directory:test: All Agent Directory Service benchmark tests
* benchmarks:slim:test: All SLIM benchmark tests
* integrations:apps:download:wfsm-bin: Get wfsm binary from GitHub
* integrations:apps:get-marketing-campaign-cfgs: Populate marketing campaign config file
* integrations:apps:init-submodules: Initialize submodules
Expand Down
6 changes: 3 additions & 3 deletions docs/identity/arch_diagrams.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,8 @@ A similar process can be followed in the case of MCP Servers or A2A Agents, but

The following steps summarize the process:

1. An Agent Consumer may search for an Agent with given skills, e.g., using an ADS client, such as a CLI, a UI, or a headless interface in case the consumer is an agent itself.
2. A lookup is performed using the ADS.
1. An Agent Consumer may search for an Agent with given skills, e.g., using an Agent Directory Service client, such as a CLI, a UI, or a headless interface in case the consumer is an agent itself.
2. A lookup is performed using the Agent Directory Service.
3. A list of potential candidates are presented to the Agent Consumer.
4. The Agent Consumer selects the desired Agent.
5. This now triggers the lookup of the selected Agent's definition (e.g., a definition based on an OASF schema), which contains the Agent ID (e.g., an Okta, Duo, AD, DID, or A2A ID).
Expand All @@ -48,7 +48,7 @@ The following steps summarize the process:
- It decrypts the ProofValue and verifies the Agent Badge integrity, since, as shown in the examples [here](./vc_agent_badge.md), the proof type is a `"DataIntegrityProof"`. This may include the computation of a digest, and comparison with a digest obtained after decryption.
- It outputs the verification result and logs it.

10. The Verified Agent Badge is returned to the ADS client.
10. The Verified Agent Badge is returned to the Agent Directory Service client.
11. This is forwarded to the Agent Consumer.

AGNTCY plans to contribute open-source code to automate the process of resolving and verifying Agent Badges and MCP Server Badges, leveraging `ResolverMetadata` objects.
Loading