Match a CLABE name
Compare an expected beneficiary name with supported bank evidence for one authorized CLABE.
Input
CLABE, expected beneficiary name, holder type, current quote, authorization reference and stable request UUID.
Result
Task state and name comparison with its evidence and charges; uncertain similarity requires review.
Scope
A quoted microtransfer may apply and requires explicit recipient and spending authority. This is not document identity or proof of current account control.
Inspect a sample
Synthetic example · no live request or charge
{
"status": "review",
"name_match": "inconclusive",
"verified": false,
"automatic_business_approval": false
}Price and access
6 MXN / 1
Before tax. Existing product packages and quote rules apply; installing a Skill does not buy credit. Read current capabilities in the Console before a live call.
Connect your assistant
python3 -m venv .venv
.venv/bin/python -m pip install "gridzen-developer-kit>=0.7.0"
.venv/bin/gridzen tools --product mx-account-name
.venv/bin/gridzen setup --client codex --product mx-account-name --project .
# Apply after reviewing the preview:
.venv/bin/gridzen setup --client codex --product mx-account-name --project . --applyCodex · Claude · Cursor · VS Code · Copilot · Gemini · Cline · Roo Code · OpenCode
Set your merchant key in the local process environment. Never paste it into a conversation or commit it. Product profiles select visible tools; server permissions still apply.