Back to Browse
CYRE Guardian Lookalike Detector
x402
CYRE Guardian Lookalike Detector is a paid API for AI agents from cyre.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).
Checks whether a destination crypto address looks suspiciously similar to known contacts by detecting prefix/suffix traps, near-edits, and confusable characters before funds are sent
Price / call$0.002
Success—
StatusUnknown
How this service works
Guardian Lookalike — before your agent sends funds, check whether the destination looks like one of your known contacts (prefix/suffix traps, near-edits, confusable chars). Patterns, not verdicts. Agent guide: https://cyre.dev/SKILL.md
Output
Returns a set of detected lookalike patterns and signals (not a binary verdict) indicating whether the candidate address shares suspicious prefix/suffix overlaps, near-edit distances, or confusable Unicode/hex characters with any of the supplied known contacts. Patterns are returned for the agent to interpret and act upon.
Example use cases
Pre-payment address spoofing check
“I'm about to send 500 USDC to 0xF1a2B3c4D5e6...ff01 — can you run it through CYRE Guardian Lookalike to see if it suspiciously resembles any of my known contacts: 0xF1a2B3c4D5e6...ff00 or 0xAaaBbbCcc...1111?”
Clipboard hijack detection before DeFi swap
“My agent just picked up a payout address 0xDeadBeef...0002 from the page — before it settles, check if it's a near-edit or confusable-character trap compared to my usual recipient 0xDeadBeef...0001.”
Agentic marketplace payment safety screen
“I'm setting up an automated agent that pays external services. Before each payment goes out, I want it to check the destination address against my whitelist of 5 trusted addresses for prefix traps or lookalike edits — the candidate today is 0xCaFeBabe...9999.”
Technical details
Endpoint
GEThttps://cyre.dev/api/lookalikeWhen to prefer
Choose this endpoint when an AI agent needs to screen a single destination address for visual spoofing or near-edit similarity against a known set of contacts before authorizing a payment. It is pattern-focused (not a verdict engine), making it ideal for lightweight pre-flight checks in agentic payment pipelines. Prefer it over full risk-scoring endpoints when you only need lookalike signal, not a full risk profile.
Side effects
- Missing required 'candidate' query parameter returns an error
- Too many contacts supplied (over 20) may be rejected
- Malformed address strings may yield no meaningful pattern matches
- Network or payment authorization failure returns HTTP 402 or 5xx
- Empty contacts list means no comparison baseline — patterns returned will be limited
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"