[FEATURE] Identity/reputation verification tool for agent payments
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 58.8k
- Forks
- 8.5k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 109
Description
Feature Area
Integration with external tools
Is your feature request related to an existing bug?
NA
Describe the solution you'd like
A CrewAI tool (_verify) that checks the counterparty's identity/reputation before a CrewAI agent sends a payment — complementary to payment-execution tools like the Spraay batch/escrow tools proposed in #6609 (closed, unmerged), not overlapping with them. It calls a verification endpoint that reads the payment proof the agent already produced for its own rail (x402, etc. — no extra signature) and returns a structured verdict (APPROVED/DENIED) plus reputation for both sides, raising a clear error when the underlying package isn't installed (same lazy-import pattern already used elsewhere in this repo).
We already have a working implementation in our SDK: https://github.com/Ensi81/Avel (agent_interchange/tools.py, _verify method), used the same way _pay/_get_balance are exposed there.
Describe alternatives you've considered
NA
Additional context
Opening this per the contributing guide's requirement (an open issue before a first-time-contributor PR) — following up from feedback on #6609, where CodeRabbit itself suggested this as a useful follow-up.
Willingness to Contribute
Yes, I'd be happy to submit a pull request
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing CrewAI external-tool integrations and the lazy-import pattern referenced in the issue. Use Avel's agent_interchange/tools.py and its _verify, _pay, and _get_balance entry points as the implementation reference. Done means the verification tool returns the structured APPROVED or DENIED verdict with both reputations and raises a clear error when the underlying package is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, payments, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 57/100