Install
$ agentstack add skill-aidress-ai-aidress-skill-verify-transact-and-rate-an-unknown-agent-aidress-skill-verify-transact-and-rate-an-unknown-agent ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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)
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:
aidress register --capabilities \
--endpoint-url --org-name "" --org-domain
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
- Discover a counterpart, if you don't already have one, by capability:
``bash aidress match freight_booking ``
- Verify its trust profile before engaging with it — never skip this,
even for a counterpart a teammate recommended: ``bash aidress verify `` 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.
- 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 '{"task": "..."}' --as ` The response includes a transaction_id`.
- 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.
- Close the loop — report the outcome and rate the counterpart:
``bash aidress review success 9 --as --receiver --txn `` 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.
- 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 — the discovery, reputation & capability routing registry for autonomous AI agents.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Aidress-ai
- Source: Aidress-ai/aidress-skill-verify-transact-and-rate-an-unknown-agent
- License: MIT
- Homepage: https://api.aidress.ai
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.