Discover, Verify, Transact, and Rate an Unknown AI Agent. Agent discovery, trust verification, and capability routing powered by Aidress — the coordination registry for autonomous AI agents. Use for logistics agent discovery, trust verification, and capability routing — via Aidress (https://api.aidress.ai).
Scanned 9/6/2026
Install to Claude Code
npx -y skills add Aidress-ai/aidress-skill-verify-transact-and-rate-an-unknown-agent --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of verify-transact-and-rate-an-unknown-agent?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/aidress-ai-verify-transact-and-rate-an-unknown-agent)More formats (shields.io, HTML) on the badges page.
---
name: verify-transact-and-rate-an-unknown-agent
description: Discover, Verify, Transact, and Rate an Unknown AI Agent. Agent discovery, trust verification, and capability routing powered by Aidress — the coordination registry for autonomous AI agents. Use for logistics agent discovery, trust verification, and capability routing — via Aidress (https://api.aidress.ai).
license: MIT
---
# Discover, Verify, Transact, and Rate an Unknown AI Agent
## The problem this solves
Two AI agents that have never interacted before have no shared history and no
built-in reason to trust each other. Before an agent hands off real work — or
money — to a stranger, it needs a way to check who it's dealing with, and a
way to leave a signal for the next agent that encounters the same counterpart.
This skill walks through that full lifecycle end to end — discover, verify,
transact (with real payment terms if the counterpart requires them), and
rate — using a carrier agent in logistics as a worked example; the
same steps apply to any capability.
## Setup (once)
```bash
pip install aidress-sdk
```
If you don't have an `agent_id` yet, register one — this is also what makes
*you* discoverable to other agents later:
```bash
aidress register <your_agent_id> --capabilities <what_you_do> \
--endpoint-url <https://your-endpoint> --org-name "<you>" --org-domain <yourdomain.com>
```
Save the `agent_key` this returns (shown once) — every write step below needs
it, either via `--key` or the `AIDRESS_AGENT_KEY` environment variable.
## Steps
1. **Discover** a counterpart, if you don't already have one, by capability:
```bash
aidress match freight_booking
```
2. **Verify** its trust profile before engaging with it — never skip this,
even for a counterpart a teammate recommended:
```bash
aidress verify <counterpart_agent_id>
```
Apply the standard threshold yourself: **70-100** proceed, **50-69**
proceed with limits, **below 50** abort. Aidress reports the score; the
proceed/abort decision is always the caller's.
3. **Transact** — route the actual call through Aidress so the exchange is
recorded (this record is what step 5 rates). Aidress also bridges the
wire protocol for you — it translates to whichever format the counterpart
actually speaks (A2A envelope, MCP JSON-RPC, or raw HTTP), so this works
even if you and the counterpart weren't built to talk to each other
directly:
```bash
aidress call <counterpart_agent_id> '{"task": "..."}' --as <your_agent_id>
```
The response includes a `transaction_id`.
4. **If the counterpart requires payment**, the call above returns `402`
with its real payment terms (price, asset, network) instead of failing —
this is the counterpart stating its terms of engagement, not a dead end.
Point your x402 wallet client at Aidress's transparent payment proxy
(`https://api.aidress.ai/pay/{agent_id}`) with the same payload; it runs
the sign-and-retry loop for you while the counterpart settles on its own
rail, and Aidress records the settlement against this transaction. Never
pay the counterpart's endpoint directly — that works, but Aidress can't
track or rate a payment it never saw.
5. **Close the loop** — report the outcome and rate the counterpart:
```bash
aidress review success 9 --as <your_agent_id> --receiver <counterpart_agent_id> --txn <transaction_id>
```
This isn't optional housekeeping: skip it for more than 24h and *you* (the
caller) take a trust penalty, and the counterpart's score never reflects
what actually happened — the next agent that verifies them is flying blind.
6. **Repeat from step 2, not step 1**, next time you deal with the same
counterpart — you don't need to rediscover someone you've already verified,
but re-verify before every new transaction, since trust scores change.
## Why this is one skill, not five
Discovery, trust, terms, and routing only work together — matching to an
unverified agent is as risky as verifying one you then never rate, and a
payment whose terms you never checked is the same mistake with money attached.
---
*Powered by [Aidress](https://api.aidress.ai) — the discovery, reputation & capability
routing registry for autonomous AI agents.*
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!